Korean한국어

여러 AI 코딩 에이전트 (Claude Code, Codex, opencode)가 서로 대화하는 로컬 MCP 데몬. 에이전트 등록, 1-to-1 메시지, 팀 또는 역할에 방송, 그리고 서로를 깨 - 모든 단일 데몬, 외부 서비스.

왜 Claude Code의 에이전트 팀을 사용 하지?

Claude Code는 이미 자체 에이전트 팀 기능을 발송합니다. 표면에 그것을 가진 교차 시약 팀이, 그러나 다른 문제를 해결합니다. 이 프로젝트를 위해 도달하는 3개의 구체적인 이유:

Cross-agent 지원. Claude Code의 대리인 팀은 Claude Code 자체에 묶습니다 — 각 회원은 Claude Code sub-agent입니다. Cross-agent-teams는 동일한 팀에서 다른 대리인을 섞을 수 있습니다: Claude 부호 대리인, Codex 대리인, opencode 대리인, Cursor 대리인, 등, 1개의 daemon를 통해서 모든 coordinating. 1개의 하네스에 잠긴 대신 각 역할에 적합한 에이전트를 사용합니다.

**항근 및 통제성. ** 이 디자인에서 각 에이전트 프로세스가 시작되고 수동으로 중지됩니다.

cross-agent-teams-mcp

中文说明

A local MCP daemon that lets multiple AI coding agents (Claude Code, Codex, opencode) running on the same machine talk to each other. Agents register, send 1-to-1 messages, broadcast to a team or role, and wake each other up — all over a single daemon, no external services.

Why not just use Claude Code’s agent teams?

Claude Code already ships its own agent teams feature. cross-agent-teams overlaps with it on the surface, but solves a different problem. Three concrete reasons to reach for this project:

Cross-agent support. Claude Code’s agent teams are tied to Claude Code itself — every member is a Claude Code sub-agent. cross-agent-teams lets you mix different agents in the same team: a Claude Code agent, a Codex agent, an opencode agent, a Cursor agent, etc., all coordinating through one daemon. Use the agent that’s best suited for each role instead of being locked to one harness.

Better persistence and controllability. In this design, each agent process is started and stopped manually. That’s more cumbersome than implicit spawn-on-demand, but it’s also much more controllable and persistent — agents keep their own long-running context, memory, and conversation state instead of being recreated from scratch every time the orchestrator decides it needs them. You can leave a specialist agent running for hours or days and keep talking to the same session.

Cross-device / cross-user collaboration. The daemon recently grew support for building teams across physical machines (see section 4). That means you can coordinate with agents running on a teammate’s laptop, where different people may own different specialized agents or workflows — something a single-process in-harness teams feature can’t reach.

Quick start

Recommended: let a code agent set it up

The whole device setup (zshrc launchers, daemon token, codex/opencode config) is written as an agent-readable runbook: README.agent.md. Paste this to any code agent that can fetch URLs and run shell commands:

Read https://raw.githubusercontent.com/jtianling/cross-agent-teams-mcp/HEAD/README.agent.md
and follow it to set up xats on this device.

The agent will confirm a device label and the ~/.zshrc changes with you, auto-generate the daemon token on first start-xats, and wire up the free-xats-codex / xats-codex / free-xats-opencode / xats-opencode launchers plus start-xats / stop-xats. Prefer doing it by hand? Continue below.

Claude Code

# 1. Start the daemon (run once, keep it alive)
npx -y cross-agent-teams-mcp@latest daemon --port 9100 &

# 2. In your project, install the MCP config
npx mcpsmgr add jtianling/cross-agent-teams-mcp -a claude-code

# 3. Start Claude Code with the channel loader (manual permission prompt expected)
claude --dangerously-load-development-channels server:cross-agent-teams-channel