Introducing opencode-plugin-peers: local cross-session messaging for OpenCode

[jkrandom-sudo]

What it does

opencode-plugin-peers lets independent OpenCode sessions on the same machine discover each other and exchange plain-text messages. It is useful when you run multiple terminals, repositories, or worktrees in parallel and want sessions to hand off conclusions without copying and pasting context.

Highlights

• Discover peers with list_agents or /peers
• Send messages with send_message, including while the target session is busy
• Address root and child sessions independently
• Keep durable queues, delivery outcomes, and sender outboxes across restarts
• Control inbound messages with accept, auto, hold, or refuse
• Use local-only transport: Unix-domain sockets on macOS/Linux and loopback TCP on Windows
• Exchange plain text only—no files or shared conversation history

Install

opencode plugin -g opencode-plugin-peers

Requires OpenCode 1.18.0 or later. Current npm release: 0.2.1.

• GitHub: https://github.com/jkrandom-sudo/opencode-plugin-peers
• npm: https://www.npmjs.com/package/opencode-plugin-peers

Security note

Peer messages are untrusted input. Same-machine processes running as your user share the local trust boundary. For sensitive projects, consider peerPermissions: "ask" and inboundPolicy: "hold" or "refuse" instead of automatic handling. See the README for the full security model.

Feedback wanted

I would especially value feedback on:

• multi-repository and worktree workflows
• busy-session delivery and restart recovery
• inbound policy and permission UX
• Windows behavior

If you try it, please share your OpenCode version, operating system, and workflow when reporting an issue.