cross-agent-teams-mcp 0.6.0 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/README.zh-CN.md +10 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,6 +4,16 @@
|
|
|
4
4
|
|
|
5
5
|
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.
|
|
6
6
|
|
|
7
|
+
## Why not just use Claude Code's agent teams?
|
|
8
|
+
|
|
9
|
+
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:
|
|
10
|
+
|
|
11
|
+
**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.
|
|
12
|
+
|
|
13
|
+
**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.
|
|
14
|
+
|
|
15
|
+
**Cross-device / cross-user collaboration.** The daemon recently grew support for building teams across physical machines (see [section 4](#4-cross-host--cross-device-collaboration)). 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.
|
|
16
|
+
|
|
7
17
|
## Quick start
|
|
8
18
|
|
|
9
19
|
### Claude Code
|
package/README.zh-CN.md
CHANGED
|
@@ -4,6 +4,16 @@
|
|
|
4
4
|
|
|
5
5
|
一个本地 MCP daemon, 让同一台机器上的多个 AI 编码 agent (Claude Code, Codex, opencode) 互相通信. agent 注册到 daemon, 互发 1-to-1 消息, 在 team 或 role 内广播, 互相唤醒 — 全部通过一个本地 daemon 完成, 不依赖任何外部服务.
|
|
6
6
|
|
|
7
|
+
## 为什么不直接用 Claude Code 自带的 agent teams?
|
|
8
|
+
|
|
9
|
+
Claude Code 自己也有 agent teams 功能, cross-agent-teams 表面上和它有重叠, 但解决的是不同的问题. 三个具体的理由:
|
|
10
|
+
|
|
11
|
+
**跨 agent 支持.** Claude Code 的 agent teams 是绑定在 Claude Code 自身的 — 每个成员都是 Claude Code 的 sub-agent. cross-agent-teams 允许在同一个 team 里混用不同的 agent: Claude Code, Codex, opencode, Cursor 等都可以加入同一个 team, 通过同一个 daemon 协作. 按场景选最合适的 agent, 而不是被某一个 harness 锁死.
|
|
12
|
+
|
|
13
|
+
**更强的持久性与可控性.** 本项目的设计是每个 agent 进程都由你手动启动和停止. 这比"按需隐式拉起"麻烦, 但也更可控, 更持久 — agent 自己保留长期上下文, 记忆, 会话状态, 不会被编排器隐式重建. 一个专家 agent 可以挂着跑几小时甚至几天, 你一直跟同一个 session 对话.
|
|
14
|
+
|
|
15
|
+
**跨设备 / 跨用户协作.** daemon 最近新增了跨物理机组 team 的能力 (见 [第 4 节](#4-跨主机--跨设备协作)). 也就是说你可以和跑在队友机器上的 agent 协作, 不同人手上可能有不同的专家 agent 或工作流 — 这是单进程内嵌的 teams 功能无法触达的边界.
|
|
16
|
+
|
|
7
17
|
## 快速开始
|
|
8
18
|
|
|
9
19
|
### Claude Code
|