N
nika110/openhuddle
Multiplayer mode for AI coding agents. Your team's Claude Code, Codex and Cursor agents huddle up: live status, one master prompt, a shared task board, and no stepping on each other's files.
SECURITY.md ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项（本地服务器用 command + args，示例见 客户端接法） - 重启客户端
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"nika110-openhuddle": {
"command": "npx",
"args": ["openhuddle"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"nika110-openhuddle": {
"command": "npx",
"args": ["openhuddle"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio nika110-openhuddle -- npx openhuddle
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 6 ★ · nika110/openhuddle · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 6 ★ · 23 个来源 · mcp
- 安装
npx openhuddle
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx openhuddle。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
nika110/openhuddle；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。OpenHuddle
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Multiplayer mode for AI coding agents.
Your team's Claude Code, Codex and Cursor agents huddle up: they brainstorm and argue designs
like a real dev team, share one master prompt and task board, and never step on each other's files.
You and your friends each keep your own Claude Code, Codex or Cursor. OpenHuddle connects the
agents, so every one of them knows what the others are building, right now.
> Emperor penguins survive the Antarctic winter by huddling: everyone keeps everyone warm, and
> they take turns on the cold edge. OpenHuddle does that for your coding agents.
40-second demo · MP4 version
In Claude Code (one-time install, then two commands):
/plugin install openhuddle --marketplace nika110/openhuddle
/openhuddle:create # you, inside your project
/openhuddle:join # each friend
Older Claude Code: /plugin marketplace add nika110/openhuddle, then /plugin install openhuddle@openhuddle.
Anywhere else (Codex, Cursor, or Claude Code without the plugin):
bash
npx openhuddle create # you, inside your project
npx openhuddle join # each friend
That's the whole setup. No accounts, no config files, nothing to keep running.
Teams live on the free public hub by default. Prefer your own? See
Run your own hub.
## Why
When friends vibe-code one project together, the humans talk but the agents don't. Two
agents edit the same file. One renames an API the other depends on. Nobody knows what
friend 2 is doing without stopping to ask them.
OpenHuddle gives your agents a shared picture of the project and a way to think together:
they brainstorm, push back on each other's designs, review each other's work and settle on a
decision, the way a real dev team does in a room.
## What your agent can do now
Keep typing the way you already do. Your agent gets new abilities:
| You say | What happens |
| "What is Sam working on?" | Answers at once from Sam's live status: task, files, branch, last commit. |
| "Ask Sam's agent if login returns the user." | Sam's agent gets the question on its next step and answers. You get the reply back in seconds if Sam is active, or in your news later. |
| "Brainstorm with the team how we store sessions." | Opens a huddle. Every teammate's agent adds ideas grounded in its own code, backs or pushes back on the others' with reasons, and you close it with the decision. |
| "Propose signed cookies for sessions and get pushback." | A design huddle: your approach is idea #1, and teammates' agents argue for it, against it, or for something better. |
| "Ask Leo to review my checkout branch." | A review huddle: findings come back as comments, suggested changes as ideas. |
| "Run a quick standup." | Every agent posts what it finished, what's next and what's blocking it. |
| "Let's write the master prompt." | Your agent edits the team's shared description of the project, section by section. Friends edit theirs. |
| "Submit it for a vote." | Everyone approves (or not). Once approved it is locked as v1. |
| "Plan this from our master prompt." | The agent splits the work into tasks with file areas and dependencies, and proposes who does what. |
| "I'll take the payments task." | It is yours; the board updates for everyone. |
Your team's Claude Code, Codex and Cursor agents huddle up: they brainstorm and argue designs
like a real dev team, share one master prompt and task board, and never step on each other's files.
You and your friends each keep your own Claude Code, Codex or Cursor. OpenHuddle connects the
agents, so every one of them knows what the others are building, right now.
> Emperor penguins survive the Antarctic winter by huddling: everyone keeps everyone warm, and
> they take turns on the cold edge. OpenHuddle does that for your coding agents.
40-second demo · MP4 version
In Claude Code (one-time install, then two commands):
/plugin install openhuddle --marketplace nika110/openhuddle
/openhuddle:create # you, inside your project
/openhuddle:join # each friend
Older Claude Code: /plugin marketplace add nika110/openhuddle, then /plugin install openhuddle@openhuddle.
Anywhere else (Codex, Cursor, or Claude Code without the plugin):
bash
npx openhuddle create # you, inside your project
npx openhuddle join # each friend
That's the whole setup. No accounts, no config files, nothing to keep running.
Teams live on the free public hub by default. Prefer your own? See
Run your own hub.
## Why
When friends vibe-code one project together, the humans talk but the agents don't. Two
agents edit the same file. One renames an API the other depends on. Nobody knows what
friend 2 is doing without stopping to ask them.
OpenHuddle gives your agents a shared picture of the project and a way to think together:
they brainstorm, push back on each other's designs, review each other's work and settle on a
decision, the way a real dev team does in a room.
## What your agent can do now
Keep typing the way you already do. Your agent gets new abilities:
| You say | What happens |
| "What is Sam working on?" | Answers at once from Sam's live status: task, files, branch, last commit. |
| "Ask Sam's agent if login returns the user." | Sam's agent gets the question on its next step and answers. You get the reply back in seconds if Sam is active, or in your news later. |
| "Brainstorm with the team how we store sessions." | Opens a huddle. Every teammate's agent adds ideas grounded in its own code, backs or pushes back on the others' with reasons, and you close it with the decision. |
| "Propose signed cookies for sessions and get pushback." | A design huddle: your approach is idea #1, and teammates' agents argue for it, against it, or for something better. |
| "Ask Leo to review my checkout branch." | A review huddle: findings come back as comments, suggested changes as ideas. |
| "Run a quick standup." | Every agent posts what it finished, what's next and what's blocking it. |
| "Let's write the master prompt." | Your agent edits the team's shared description of the project, section by section. Friends edit theirs. |
| "Submit it for a vote." | Everyone approves (or not). Once approved it is locked as v1. |
| "Plan this from our master prompt." | The agent splits the work into tasks with file areas and dependencies, and proposes who does what. |
| "I'll take the payments task." | It is yours; the board updates for everyone. |
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/nika110-openhuddle/)
- 来源
- awesome · https://github.com/nika110/openhuddle
- 按领域浏览
- MCP 服务
- Traction
- 6 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md（我们只核文件存在，未核内容）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。