Openhuddle

Name: Openhuddle
Author: nika110

제작자: nika110버전 0.4.1i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.nika110/openhuddle

설치

개요

제작자가 쓴 설명(영어 원문)

Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 문서, 시트 및 사무 업무

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add openhuddle -- npx -y openhuddle mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "openhuddle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 nika110 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

문서, 시트 및 사무 업무 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 2174개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 2174개 중 63%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 2174개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Openhuddle, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.4.1)은 18일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Agent-Native Calendar

제작자: BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

클라우드에서 실행★ 7,620MIT2개월 전 업데이트

설치

Excel MCP Server

제작자: haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

내 컴퓨터에서 실행★ 4,276MIT6일 전 업데이트

설치

MCP Server for Excel

제작자: sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

내 컴퓨터에서 실행★ 847MIT3일 전 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

OpenHuddle

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):

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.
"From now on, let the agent assign tasks."	Team settings change by talking. No files to edit.

And without you asking:

News arrives on its own (Claude Code). Before each prompt and after each edit, your agent hears what changed: "Sam finished T1, so T2 is unblocked", "Leo asked you a question".
Teammates get answers (Claude Code). Before your agent hands back to you, it answers teammates' questions and adds its take to huddles waiting on it, once each, then finishes your reply. Turn it off for yourself with "set auto_respond off".
No trampling (Claude Code). Editing a file claims it for 30 minutes. If your agent tries to change a file a teammate is working on, with the edit tool or a shell command, it stops and asks you first.
Commits are shared (every tool). A git hook tells the team about every commit.

How a project goes

 master prompt  →  vote  →  plan  →  build  →  merge

(everyone) (lock v1) (lead) (each on (git, as a branch) usual)

Master prompt. Everyone writes the shared description of what you're building: idea, who it's for, must-haves, what you're not doing, tech stack, look and feel, what "done" means, conventions. Every edit is signed and versioned.
Vote. Submitting starts a vote. With the default rule everyone approves, then it locks. Changing it later starts an amendment and a new vote.
Plan. The lead (whoever makes the plan, any member can) turns it into tasks. Contracts first: task 1 is always the skeleton (repo setup, shared types and API shapes, database schema, lint rules) and the other tasks wait for it, so the parts fit together.
Build. Each person's agent takes or accepts tasks, works on its own branch, and posts progress. Finishing a task unblocks the ones waiting on it and tells their owners.
Merge with git, the way you already do. OpenHuddle never stores your code.

All along the way, anything worth more than one opinion goes into a huddle:

Kind	What it's for
`brainstorm`	An open question. Everyone adds ideas and backs or pushes back on the others'.
`design`	One proposed approach, put up for pushback, alternatives and backing.
`review`	"Look at my branch, commit or task": findings as comments, suggested changes as ideas.
`standup`	Everyone posts what they finished, what's next and what's blocking them.

A huddle shows who it's still waiting on. Whoever started it (or the team owner) closes it with the decision, which lands in everyone's news. If the decision means new work, the agent adds tasks. You can join in from the dashboard too.

Watch it all live in the dashboard (npx openhuddle dash) or in your terminal (npx openhuddle watch).

How it works

            ┌─────────── OpenHuddle hub ───────────┐

│ team · master prompt · task board │ │ huddles · file claims · questions │ │ live feed │ └────▲─────────────▲─────────────▲─────┘ │ │ │ ┌──────┴─────┐ ┌─────┴──────┐ ┌────┴───────┐ │ Ana │ │ Sam │ │ Leo │ │ Claude Code│ │ Codex │ │ Cursor │ └────────────┘ └────────────┘ └────────────┘ code still goes through git

The hub holds the shared picture. It is one small server; use the public one or run your own.
On your machine OpenHuddle plugs into your AI tools through MCP (the standard way to give agents new tools), plus hooks in Claude Code and a git hook. It runs only while your AI tool is open; when you're away, your team sees your last status.

What works where

	Claude Code	Codex	Cursor
Install	plugin or `npx`	`npx`	`npx`
Team tools (sync, ask, huddles, tasks, master prompt, plan)	✅	✅	✅
News arrives on its own before each prompt and after each edit	✅	ask "what's new?"	ask "what's new?"
Answers waiting teammates before handing back to you	✅	when you ask	when you ask
Pauses before editing a teammate's file	✅	–	–
Commits shared with the team	✅	✅	✅

create and join detect which tools you have and connect each one.

Settings

Every setting has a default. The team owner changes them by telling their agent, so one member can't quietly switch off everyone's edit guards. Anyone can take the lead.

Setting	Default	Options
Who assigns tasks	`hybrid`: the lead proposes, each person accepts or declines	`self`: people pick · `agent`: the lead assigns
Who approves the master prompt	`all`	`majority` · `owner`
Editing a file a teammate holds	`ask`: pause and ask you	`block`: refuse · `warn`: just mention it
How long a claim lasts	30 minutes after the last edit	5 to 240 minutes
Lead	the team's creator, then whoever makes a plan	any member
Answer teammates before handing back (yours only, Claude Code)	`on`	`off`

Requirements

Node.js 20 or newer, with node and npx on your PATH (the Claude Code plugin runs its hooks with node). Running your own hub needs Node 22.13 or newer.
A git repository for the project. Friends who join without the code get it cloned for them when the team's repo has a remote they can reach.
Claude Code, Codex or Cursor. Mix them freely within a team.

Commands

In Claude Code with the plugin:

/openhuddle:create [--name "Team"] [--as you]    start a team in this project

/openhuddle:join join one /openhuddle:status what the team is doing right now /openhuddle:huddle [kind] start a brainstorm, design, review or standup

From any terminal:

npx openhuddle create [--name "Team"] [--as you]   start a team in this repo

npx openhuddle join [--as you] join one (clones the repo if you need it) npx openhuddle status who is doing what, the board, the master prompt npx openhuddle watch live feed in the terminal npx openhuddle dash open the live dashboard npx openhuddle invite [--rotate] show (or reset) the invite link npx openhuddle remove remove a teammate (owner) npx openhuddle delete-team --yes delete the team and all its data now (owner) npx openhuddle doctor [--fix] check and repair the setup npx openhuddle leave leave and remove openhuddle from this project npx openhuddle hub [--port 8787] run your own hub

Updating

Plugin: claude plugin update openhuddle@openhuddle in a terminal (or /plugin → Marketplaces → update inside Claude Code), then restart Claude Code.
npx setups: run npx openhuddle@latest doctor --fix in the project. It refreshes the copy in ~/.openhuddle/app that the hooks and tools use. When your team's hub runs a newer version, your agent tells you so.

Uninstall

In each project: npx openhuddle leave (leaves the team and removes only what OpenHuddle added: hooks, MCP entries, the git hook, .openhuddle/).
Plugin: /plugin uninstall openhuddle.
Then delete ~/.openhuddle if you like.

Troubleshooting

Symptom	Fix

| Your age

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

Openhuddle

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

문서, 시트 및 사무 업무 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

제작자의 README

Why

What your agent can do now

How a project goes

How it works

What works where

Settings

Requirements

Commands

Updating

Uninstall

Troubleshooting