Peer-to-peer chat between Claude Code sessions via files. Tools and /huddle_* slash commands for sessions in the same repo to coordinate.
List all agents registered in this repo's huddle space. Use when the user types /huddle_agents.
Join an existing huddle. You'll see the full message history on your next read. Use when the user types /huddle_join <name>.
Leave a huddle. You'll no longer receive its messages; the huddle itself stays. Use when the user types /huddle_leave <name>.
List all huddles in this space with membership and unread counts. Use when the user types /huddle_list.
Read unread messages from a huddle (marks them as read). Use when the user types /huddle_read <name>.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Peer-to-peer chat between Claude Code sessions via files. Two (or more) claude
instances running in the same repo can coordinate over named rooms ("huddles")
that you control — the user decides which sessions join which huddles.
You're running Claude in two terminals in the same repo, each on its own task. Occasionally the work overlaps — both sessions reach for the same file, refactor the same module from different angles, or hit the same bug and start chasing it in parallel. Today you notice the overlap manually, paste context between windows, and hope nothing was clobbered.
huddle gives those sessions a way to talk directly: spin up a named room when
you notice the convergence, drop both sessions in, and let them swap notes
("I'm rewriting auth.py — leave it alone for 10 minutes", "found the bug at
router.go:142, taking it from here"). Coordination on demand, no orchestrator
required.
git clone <repo-url> ~/src/<wherever>/huddle-mcp
claude plugin marketplace add ~/src/<wherever>/huddle-mcp
claude plugin install huddle
Restart any running claude session to pick up the plugin's MCP server and
slash commands.
claude plugin uninstall huddle
claude plugin marketplace remove huddle-mcp
In every claude session in the repo, the plugin auto-assigns an identity
(agent-a, agent-b, …) on first tool call. From there, you direct each session:
/huddle_start <name> — create a huddle (you're the sole member)/huddle_join <name> — join an existing huddle in another session/huddle_send <name> <message> — post a message/huddle_read <name> — read unread messages/huddle_wait [seconds] — block until a new message arrives/huddle_list — list all huddles with membership/unread/huddle_leave <name> — leave a huddle/huddle_whoami — show your assigned identity/huddle_agents — list all sessions registered in this repoThere is no auto-enrollment and no invite — you tell each session what to
start or join.
The plugin ships a huddle CLI that reads message files directly — no Claude
session involved.
huddle list # list huddles in this repo
huddle show <name> # print the full conversation
huddle show <name> -f # follow: print new messages as they arrive
If huddle isn't on your PATH, run it inside the repo with
uv run huddle ..., or install globally with uv tool install ~/src/<wherever>/huddle-mcp.
Per-repo huddle state lives at ~/.claude/huddle/<repo-basename>/:
~/.claude/huddle/<repo>/
agents.json
huddles/
<huddle-name>/
meta.json
messages/
<ts>-from-<sender>-<id>.json
read-state/
<agent>.json
All JSON, inspectable by hand. Override the root with HUDDLE_ROOT=/some/path.
Override identity with HUDDLE_NAME=alice.
uv sync
uv run pytest
uv run ruff check .
The plugin loads the MCP server via uv --directory ${CLAUDE_PLUGIN_ROOT} run huddle-mcp (see .mcp.json).
In marketplace.json, "source": "./" works; "source": "." does not.
npx claudepluginhub drewburlingame/huddle-mcp --plugin huddleHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Plugin that includes the Figma MCP server and Skills for common workflows
Production-grade vibe coding suite. Structured workflows from discovery to deployment: start, build, ship, fix, refactor.
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
Memory compression system for Claude Code - persist context across sessions