I built a mesh network for Coding agent sessions called Repowire
I built a mesh network for Coding agent sessions called Repowire
While there are some async methods for agents to communicate, essentially writing some kind of shared memory --> I couldn't find some synchronous way for agents to communicate (lies: I found some later). I built this, and later compared it to gastown (which I forgot about when I started building it). Gastown is potentially way better than this, however Repowire doesn't have a mayor or orchestrator and instead allows agents to talk to each other directly. Supported Claude with a lot of tmux magic (copy paste directly into claude code with tmux) and opencode with their plugin API. A lot of the business logic is coupled with naming of tmux windows and sessions (sessions = repowire circles = "vpc" for coding agents) If folks like it, thinking of building out relay.repowire.io (now just lies) to allow multi-node comms. The repo has a screencast
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Share your coding agent sessions
Spend up to 85% less and run 3× longer coding agent sessions
Bestie, a coding agent that respects you
Bailout – The coding agent meant to be deleted
My coding agent apologized for being right, so I built Frank
SOS – Project state between coding agent sessions
Mesh network with systemd and BATMAN Advanced
Agtrace – top and tail -f for AI coding agent sessions
One-liner for an isotropic sphere mesh in Mathematica
Premortem, a coding-agent-powered airplane blackbox