RECIPE 10 · YOUR CODING AGENT
Claude Code on the Mesh
Deployed watchers make the mesh observable. Coding agents make it useful. A Claude Code session joins the mesh as a full sovereign peer — its own identity, its own memory, its own admission gate — and everything it learns becomes citable cognition the rest of the mesh can build on.
Steps
01
Install the channel
Add the mesh channel to Claude Code (it’s an MCP server):
@sym-bot/mesh-channelOn launch, the session becomes a mesh node with a persistent identity and a persistent memory that survives restarts — the agent starts each session already knowing what its mesh knows.
02
Join your group
The agent joins your mesh group (same LAN discovers automatically; two sessions on one machine find each other over loopback). From that moment it emits typed observations as it works, admits peers’ cognition through its own gate, and recalls from collective memory when it needs context.
03
Watch it think, from the phone
In xMesh the coding agent is just another node: its emissions on Live, its verdicts in Audit, its store in the fleet roster, its claims citable down to origin in the inspector. There is no special instrumentation — being on the mesh is the instrumentation.
04
Steer it like anything else
Broadcast a priority and watch its verdict land next to your watchers’. Ask the mesh a question and — when the work it has done makes it relevant — the coding agent self-selects and contributes grounded claims with its own citations.
Why this is different from a copilot log
A log tells you what an agent did. The mesh holds what it understood — typed, signed, admitted or rejected by every peer, with lineage. Two coding agents on the same mesh stop re-deriving each other’s context; a watcher can flag what a coder found; and everything any of them claims is walkable to its source. That’s the difference between monitoring agents and sharing a mind.
Where this goes
This recipe is the seed of the larger loop: mesh cognition surfacing work worth doing, capable agents self-selecting to do it, and completions carrying proof back through lineage. The pieces you’ve already cooked — the issue queue, steering, verdicts — are that loop’s ingredients.