What changed

Multi Harness Bridge was published on GitHub on 20 November 2026 after one developer built a workflow to split work across several AI development tools, according to the repository README. The developer needed a request sent in one app to reach a specific project in another and return its reply later. The README notes that all participating harnesses and wake services must run on the same machine under one account sharing the ~/.multi-harness-bridge state directory.1

How it works

The architecture guide explains that the bridge uses SQLite with WAL mode and short immediate transactions to select one eligible message and attach a time-limited random lease. Because the queue scopes every operation to a registered project, a Codex Coordinator can send work to a Devin Inbox, which durably forwards it to the Devin Coordinator and links the correlated reply back. If a consumer fails, the message can be retried after lease expiry, and a stale lease cannot acknowledge a reclaimed item, according to the architecture guide.2

A background dispatcher called multi-harness-wake polls the mailbox every four seconds by default and nudges the exact bound native session without claiming the message, the native wake guide says. To prevent misrouted prompts, a verifier checks the host's current binding before and after sending, and message bodies are never copied into native prompts or process arguments. For Devin Local, the ACP client approves only a scoped pickup_notification tool call matching the exact session and UUID, cancelling unknown calls and shell permissions, according to the guide.3

The native wake guide reports that the dispatcher records each notification attempt in the database before dispatch so confirmed sends are not repeated. Verified pre-submit refusals can be retried at most three times, while busy or draft deferrals retry on a later poll. If a host call times out or returns an ambiguous result, the driver marks the attempt uncertain and halts automatic retries until an operator inspects the session and runs manual reconciliation, the guide says.3

According to the validation document, a clean macOS wheel passed all 71 tests, and a Linux ARM64 build on Python 3.12 passed 69 tests with two macOS-specific checks skipped. However, the Antigravity Desktop accessibility helper is macOS-only and requires local Swift compilation plus user-granted Accessibility permission, the native wake guide notes. The architecture guide adds that the local SQLite design does not cover multi-user authentication, shared-network disks, or cross-machine delivery, and it cannot impose exactly-once delivery on external APIs.234