Expand description
The bridge (conclave bridge): a dual peer between Claude Code and central servers.
One process that is simultaneously a stdio MCP server to Claude Code and a WS
client to one or more central servers (DESIGN.md §13). It translates inbound central
events into injected <channel> / <whisper> notifications and outbound MCP tool calls
into central messages, owning the session identity, its connections, and the local
permission policy (DESIGN.md §9): per inbound message it resolves the
(server, channel) level, drops on mute, otherwise injects through a pluggable
notification sink; and it rejects outbound emit calls whose target channel is below
converse.
Split by responsibility: policy resolves the local autonomy level and gates emit;
sink frames a delivered message and pushes it to the session; mcp is the JSON-RPC
stdio peer toward Claude Code; client holds the outbound WS connections to central with
reconnect + re-subscribe. BridgeCore is the transport-free dispatcher those feed.
Structs§
- Bridge
Setup - Everything the running bridge needs: this machine’s key, the local config, the session handle, and (optionally) a subset of configured servers to connect to.
Functions§
- run
- Runs the bridge: the MCP stdio peer, one reconnecting WS link per server, and the dispatcher.