Coding & Development
OpenCode Peers
3h agoCross‑session messaging for OpenCode — let independent OpenCode instances on the same machine discover each other and exchange plain‑text messages. Modeled after Claude Code’s cross‑session messaging, it enables parallel terminals (different repos, work‑trees, or tasks) to share conclusions without copy‑pasting context.
Peer discovery and messagingInbound gating controlsIndependent session endpointsDurable per‑session queuesImmediate message injectionPlain‑text only communicationAutomatic peer‑triggered turnsInline results and notificationsExplicit TUI controlsLocal‑only operation
Key Capabilities
01
Peer discovery and messaging
Agents can list peers and send plain‑text messages via /list‑agents, /peers‑name, /peers‑inbox, and /peers‑outbox commands.
02
Inbound gating controls
User‑side commands to accept, auto‑accept, hold, or refuse inbound messages, with auto‑accept for same‑directory peers.
03
Independent session endpoints
Each OpenCode session (including child sessions) has a unique addressable endpoint, disambiguating duplicate names.
04
Durable per‑session queues
Message queues and sender outboxes survive process restarts, guaranteeing delivery outcomes.
05
Immediate message injection
Accepted messages are injected instantly with a single async prompt call, even while the target session is busy.
06
Plain‑text only communication
Messages consist solely of text—no file transfers or shared conversation history.
07
Automatic peer‑triggered turns
Peer‑triggered turns run unattended by default; permission requests raised during these turns are auto‑approved.
08
Inline results and notifications
Command results and notifications appear inline in the session, avoiding toast pop‑ups.
09
Explicit TUI controls
Palette actions use host dialogs for selection/confirmation; slash wrappers remain for automation compatibility.
10
Local‑only operation
All messaging stays on the local machine; no external network services are used.
Use Cases
Synchronize API contract updatesFrontend and backend OpenCode sessions exchange changes to API contracts, keeping both sides aligned in real‑time.Frontend and backend developers working on the same codebase
Coordinate database migrationsOne session notifies another when a migration is completed, allowing safe rebase or further work without manual copy‑pasting.DevOps engineers and backend developers handling schema changes
Share conclusions across work‑treesParallel terminals running in different work‑trees can hand off findings or task results, streamlining multi‑repo workflows.Developers managing multiple repositories or work‑trees
Automate hand‑off between CI tasksCI sessions can send status messages to other sessions to trigger subsequent steps without external tooling.CI/CD pipeline engineers
Maintain local knowledge baseTeams can keep a local, durable log of messages that survives restarts, useful for audit trails or debugging.Software teams requiring offline traceability
Update History
Updated 3h ago▲ 0% mentionsProduct HuntWeb