claude-peerslisted

# claude-peers Peer discovery and messaging network for AI coding agents on the same machine. A shared broker daemon listens on a Unix domain socket (`~/.claude/run/claude-peers.sock`), backed by SQLite, routing messages between Claude Code and Codex CLI sessions. ## Client Types | Client | Push notifications | Message delivery | Config | |--------|-------------------|-----------------|--------| | **claude-code** | Yes (`claude/channel`) | Instant — messages pushed into session | `settings.json` MCP entry | | **codex** | No | Poll — must call `check_messages` each turn | `~/.codex/config.toml` MCP entry | | **cli** | No | Manual via `bun ~/tools/claude-peers-mcp/cli.ts send <id> <msg>` | N/A | ## Workflow Patterns **Task delegation:** Send a focused task description to a Codex or Claude peer via `send_message`. Include file paths, acceptance criteria, and which branch to work on. The receiving agent picks it up on its next turn. **Code review handoff:** After completing work, message a peer with the diff summary and ask for review. The peer can respond with findings via `send_message`. **Parallel exploration:** Multiple agents working the same repo can use `set_summary` to advertise what they're investigating, preventing duplicate work. Use `list_peers` with scope `repo` to see who else is in the same codebase. **Session lifecycle:** Use `kill_peer` to terminate a stuck, unresponsive, or completed peer's agent session. This kills the parent process (e.g., the Codex CL