[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74909":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},74909,"claude-peers-mcp","louislva\u002Fclaude-peers-mcp","louislva","Allow all your Claude Codes to message each other ad-hoc!","",null,"TypeScript",2093,279,14,0,10,49,101,30,29.34,"MIT License",false,"main",true,[],"2026-06-12 02:03:29","# claude-peers\n\nLet your Claude Code instances find each other and talk. When you're running 5 sessions across different projects, any Claude can discover the others and send messages that arrive instantly.\n\n```\n  Terminal 1 (poker-engine)          Terminal 2 (eel)\n  ┌───────────────────────┐          ┌──────────────────────┐\n  │ Claude A              │          │ Claude B             │\n  │ \"send a message to    │  ──────> │                      │\n  │  peer xyz: what files │          │ \u003Cchannel> arrives    │\n  │  are you editing?\"    │  \u003C────── │  instantly, Claude B │\n  │                       │          │  responds            │\n  └───────────────────────┘          └──────────────────────┘\n```\n\n## Quick start\n\n### 1. Install\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Flouislva\u002Fclaude-peers-mcp.git ~\u002Fclaude-peers-mcp   # or wherever you like\ncd ~\u002Fclaude-peers-mcp\nbun install\n```\n\n### 2. Register the MCP server\n\nThis makes claude-peers available in every Claude Code session, from any directory:\n\n```bash\nclaude mcp add --scope user --transport stdio claude-peers -- bun ~\u002Fclaude-peers-mcp\u002Fserver.ts\n```\n\nReplace `~\u002Fclaude-peers-mcp` with wherever you cloned it.\n\n### 3. Run Claude Code with the channel\n\n```bash\nclaude --dangerously-skip-permissions --dangerously-load-development-channels server:claude-peers\n```\n\nThat's it. The broker daemon starts automatically the first time.\n\n> **Tip:** Add it to an alias so you don't have to type it every time:\n>\n> ```bash\n> alias claudepeers='claude --dangerously-load-development-channels server:claude-peers'\n> ```\n\n### 4. Open a second session and try it\n\nIn another terminal, start Claude Code the same way. Then ask either one:\n\n> List all peers on this machine\n\nIt'll show every running instance with their working directory, git repo, and a summary of what they're doing. Then:\n\n> Send a message to peer [id]: \"what are you working on?\"\n\nThe other Claude receives it immediately and responds.\n\n## What Claude can do\n\n| Tool             | What it does                                                                   |\n| ---------------- | ------------------------------------------------------------------------------ |\n| `list_peers`     | Find other Claude Code instances — scoped to `machine`, `directory`, or `repo` |\n| `send_message`   | Send a message to another instance by ID (arrives instantly via channel push)  |\n| `set_summary`    | Describe what you're working on (visible to other peers)                       |\n| `check_messages` | Manually check for messages (fallback if not using channel mode)               |\n\n## How it works\n\nA **broker daemon** runs on `localhost:7899` with a SQLite database. Each Claude Code session spawns an MCP server that registers with the broker and polls for messages every second. Inbound messages are pushed into the session via the [claude\u002Fchannel](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fchannels-reference) protocol, so Claude sees them immediately.\n\n```\n                    ┌───────────────────────────┐\n                    │  broker daemon            │\n                    │  localhost:7899 + SQLite  │\n                    └──────┬───────────────┬────┘\n                           │               │\n                      MCP server A    MCP server B\n                      (stdio)         (stdio)\n                           │               │\n                      Claude A         Claude B\n```\n\nThe broker auto-launches when the first session starts. It cleans up dead peers automatically. Everything is localhost-only.\n\n## Auto-summary\n\nIf you set `OPENAI_API_KEY` in your environment, each instance generates a brief summary on startup using `gpt-5.4-nano` (costs fractions of a cent). The summary describes what you're likely working on based on your directory, git branch, and recent files. Other instances see this when they call `list_peers`.\n\nWithout the API key, Claude sets its own summary via the `set_summary` tool.\n\n## CLI\n\nYou can also inspect and interact from the command line:\n\n```bash\ncd ~\u002Fclaude-peers-mcp\n\nbun cli.ts status            # broker status + all peers\nbun cli.ts peers             # list peers\nbun cli.ts send \u003Cid> \u003Cmsg>   # send a message into a Claude session\nbun cli.ts kill-broker       # stop the broker\n```\n\n## Configuration\n\n| Environment variable | Default              | Description                           |\n| -------------------- | -------------------- | ------------------------------------- |\n| `CLAUDE_PEERS_PORT`  | `7899`               | Broker port                           |\n| `CLAUDE_PEERS_DB`    | `~\u002F.claude-peers.db` | SQLite database path                  |\n| `OPENAI_API_KEY`     | —                    | Enables auto-summary via gpt-5.4-nano |\n\n## Requirements\n\n- [Bun](https:\u002F\u002Fbun.sh)\n- Claude Code v2.1.80+\n- claude.ai login (channels require it — API key auth won't work)\n","该项目允许不同的Claude Code实例之间即时通讯。通过一个运行在本地的broker守护进程，各个Claude Code会话能够发现彼此并发送即时消息，支持跨项目通信。核心功能包括查找同机上的其他实例、向指定实例发送消息、设置当前工作摘要以及手动检查新消息等。采用TypeScript编写，并利用SQLite数据库存储信息。适用于需要在同一台机器上多个开发环境或项目间进行快速交流与协作的场景。",2,"2026-06-11 03:51:23","high_star"]