Skip to content

SYNAPSE CHANNEL

The local-first coordination bus for fleets of AI agents.

Flagship example: coordinate parallel AI coding agents through declared file scopes — the hub refuses a second overlapping live claim, while covered provider hooks and the staged Git gate enforce only their documented mutation boundaries.

A local-first coordination bus for a fleet of AI agents working in parallel — within one codebase or across a whole ecosystem of them. A single WebSocket hub is the authoritative source of truth for presence, file-scoped work claims, chat, task status, a shared plan, agent capabilities, and resource offers, so agents spread over many projects can see conflicting or duplicate declared work before acting.

The bus is transport-light (websockets, plus a typing backport on Python 3.10), hub-centric by design, and its base coordination runs locally. Optional model workers use the documented provider profiles, local Ollama or a deterministic rule backend. External services have separate account, network and cost requirements.

New here? Read Why SYNAPSE CHANNEL — a five-minute read on what it is, what you build on it, how it differs from the tools next to it, and why coordination is the bottleneck once you run more than one agent.

Current 0.x releases are pre-1.0 development releases. 1.0.0 is planned as the first stable commercial release of SYNAPSE CHANNEL, with stable operational contracts, support surfaces, and commercial licensing terms documented for that line. SYNAPSE CHANNEL is seeking startup funding, strategic partners, and aligned ecosystem co-owners; see Commercial licensing for the evaluation and contact path.

Current 0.x releases do not promise backward compatibility across minor releases. Pin an exact package version when an integration needs a fixed target, and review API and wire stability plus the 0.x to 1.0 migration guide before upgrading.

A synapse session: declare a plan with a dependency, complete a task, and watch the dependent unblock

Why a coordination bus

When several agents work across your repositories at once they need a shared, authoritative view of who is doing what. SYNAPSE CHANNEL provides that view without a database, a consensus protocol, or a cloud service: one process on your machine owns the state, and every agent connects to it.

What it gives you

  • Work claims with file-scope overlap detection, expiring leases, and epochs.
  • Journal-backed recovery within retained, admitted SQLite-WAL history, integrity/key configuration and lease expiry. Keyed operations have their documented replay/retention boundaries; neither guarantees external effects.
  • A typed task lifecycle, deadlock detection, and a shared blackboard of declared tasks with dependencies and an append-only progress stream.
  • Atomic handoff, an LLM-free stall supervisor, and resumable checkpoints.
  • Proportionate connect authentication and task-class routing to tiered backends.
  • Direct messaging — broadcast, a named group (A,B), or one agent — with a per-agent inbox an idle agent catches up from the durable feed.
  • A command line for the whole flow (synapse hub/worker/team/send/listen/ relay/board/supervisor/manifest/task) and runnable examples.

Client paths: supported first

The hub speaks one wire protocol, but not every client surface carries the same support weight. Choose in this order:

  • Supported core — the paths fleets should build on today: the hub itself and its coordination CLI commands. The full CLI spans several surface classifications; only the named boundaries are covered by the API and wire stability contract.
  • Shipped adapter — the MCP server face for MCP hosts such as Claude Code, Codex, Cursor, and Claude Desktop: registered tools/resources and host-specific profiles are listed in the guide. Qualification applies to the exact host, version, artifact and executed profile; the stability contract freezes named adapter boundaries rather than every host's behavior.
  • Validated, partial interop — the A2A bridge: the official SDK completes discovery and the send/get/list/cancel lifecycle against it, and the official TCK HTTP+JSON MUST run records 55 passed with 5 documented gaps — recorded evidence, not certification. The Go and JS clients embed within their stated boundaries.
  • Experimental — the cockpit PWA and the installable VS Code extension preview: useful, moving fast, and not part of the stability contract. Expect surface changes between minor releases.

Coming: Studio

The read-only dashboard is growing into an operator Studio — a control plane that answers, at a glance, what is happening, what is at risk, and what is safe to do next. The instrument-panel design system, /studio reference page, live /studio/command shell, security-posture panel, and event-log LiveFeed have shipped. Local-first and read-only by default.

Next steps

SYNAPSE CHANNEL is AGPL-3.0-or-later with a commercial licence available. See the project's NOTICE.md.