ClawTeam Multi-Agent Coordination by hkuds/clawteam
npx skills add https://github.com/hkuds/clawteam --skill 'ClawTeam Multi-Agent Coordination'ClawTeam 是一个与框架无关的 CLI 工具,用于协调多个 AI 智能体组成团队工作。它提供团队/任务管理、智能体间消息传递、git 工作树隔离、支持感知提供商的运行时配置、git 上下文注入、快照以及基于终端的监控仪表板。
所有操作均通过 clawteam CLI 执行。数据默认存储在 ~/.clawteam/ 目录中。
pip install clawteam
需要 Python 3.10+。如需 P2P 传输支持:pip install clawteam[p2p]。
tmux(默认的生成后端)claude、codex、gemini、、 或 广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
kiminanobotopenclawclawteam profile wizard),需安装默认依赖项团队 — 由一名领导者和零个或多个工作者组成的命名智能体组。
收件箱 — 每个智能体基于文件的消息队列。receive 是消耗性的;peek 则不是。
任务 — 共享的任务看板,包含 pending(待处理)、in_progress(进行中)、completed(已完成)和 blocked(已阻塞)状态。任务支持依赖链和优先级。
配置 — 可复用的客户端/提供商/运行时配置,供 spawn 和 launch 使用。
预设 — 共享的提供商模板,用于生成一个或多个配置。
上下文 — 支持 Git/工作树的上下文工具,用于重叠检查、近期变更和提示词注入。
看板 — 团队仪表板,包含看板任务、收件箱计数和消息历史视图,以及 gource 活动可视化。
export CLAWTEAM_AGENT_ID="leader-001"
export CLAWTEAM_AGENT_NAME="leader"
export CLAWTEAM_AGENT_TYPE="leader"
clawteam team spawn-team my-team -d "项目团队" -n leader
clawteam task create my-team "设计系统" -o leader
clawteam task create my-team "实现功能" -o worker1
clawteam task create my-team "编写测试" -o worker2
clawteam board show my-team
# 检查内置的提供商模板
clawteam preset list
clawteam preset show moonshot-cn
# 从预设生成可复用的配置
clawteam preset generate-profile moonshot-cn claude --name claude-kimi
# 或者使用交互式 TUI
clawteam profile wizard
# 在新机器/新家目录首次使用 Claude Code 时,可能需要运行一次修复
clawteam profile doctor claude
# 在团队中使用配置前进行冒烟测试
MOONSHOT_API_KEY=... clawteam profile test claude-kimi
# 默认路径:tmux 后端,claude 命令,git 工作树隔离,skip-permissions 开启
clawteam spawn --team my-team --agent-name worker1 --task "实现认证模块"
clawteam spawn --team my-team --agent-name worker2 --task "编写单元测试"
# 显式指定后端和命令
clawteam spawn tmux claude --team my-team --agent-name worker3 --task "构建 API 端点"
clawteam spawn subprocess claude --team my-team --agent-name worker4 --task "运行代码检查"
# 推荐用于非默认提供商/模型
clawteam spawn tmux --profile claude-kimi --team my-team --agent-name worker5 --task "构建 API 端点"
clawteam spawn subprocess --profile gemini-vertex --team my-team --agent-name worker6 --task "运行代码检查"
clawteam board attach my-team
clawteam inbox send my-team worker1 "开始实现认证模块"
clawteam board live my-team --interval 3
| 设置项 | 默认值 | 覆盖方法 |
|---|---|---|
| 后端 | tmux | clawteam spawn subprocess ... |
| 命令 | claude | clawteam spawn tmux my-cmd ... |
| 工作空间 | auto(git 工作树) | --no-workspace 或配置 workspace=never |
| 权限 | skip | --no-skip-permissions 或配置 skip_permissions=false |
| 运行时配置 | 无 | --profile <名称> |
当您需要使用非默认的提供商、模型、端点或认证映射时,请使用 --profile。
# 创建带依赖关系的任务
clawteam task create my-team "部署" --blocked-by <实现任务ID>,<测试任务ID>
# 创建带优先级的任务
clawteam task create my-team "修复生产环境问题" --priority high
# 更新状态
clawteam task update my-team <任务ID> --status in_progress
clawteam task update my-team <任务ID> --status completed
# 筛选任务
clawteam task list my-team --status blocked
clawteam task list my-team --owner worker1
clawteam task list my-team --priority high
clawteam task wait my-team
clawteam task wait my-team --timeout 300 --poll-interval 10
clawteam task wait my-team --agent coordinator
clawteam --json task wait my-team --timeout 600
工作者在完成初始 --task 后不应停止。预期的循环是:
# 1. 检查分配给您的任务
clawteam task list my-team --owner worker1
# 2. 完成任何待处理的工作,然后检查新指令
clawteam inbox receive my-team --agent worker1
# 3. 如果空闲,通知领导者并持续监控后续指令
clawteam lifecycle idle my-team
重复此循环,直到领导者明确关闭工作者。
clawteam context log my-team
clawteam context conflicts my-team
clawteam context inject my-team --agent worker1
在重新分配工作、继续其他工作者的任务或合并重叠的变更之前使用这些命令。
clawteam team snapshot my-team --tag before-refactor
clawteam team snapshots my-team
clawteam team restore my-team --snapshot before-refactor
clawteam board gource my-team --log-only
clawteam board gource my-team --live
在无头环境中推荐使用 --log-only。
常见的已验证 CLI 包括:
claudecodexgeminikiminanobotopenclawOpenClaw 工作者的生成会自动进行规范化。原始的 openclaw 命令会根据需要提升为智能体入口点,并配置 --local、--session-id 和 --message 参数。
通过 profile + preset 配置非默认提供商,而不是将环境变量硬编码到提示词中。
| 组 | 用途 | 关键命令 |
|---|---|---|
preset | 共享的提供商模板 | list, show, generate-profile, bootstrap |
profile | 可复用的客户端/提供商配置 | list, show, set, test, wizard, doctor |
team | 团队生命周期 | spawn-team, discover, status, request-join, approve-join, cleanup, snapshot, restore |
inbox | 消息传递 | send, broadcast, receive, peek, watch |
task | 任务管理 | create, get, update, list, wait |
board | 监控与可视化 | show, overview, live, attach, serve, gource |
context | Git/工作树上下文 | diff, files, conflicts, log, inject |
plan | 计划审批 | submit, approve, reject |
lifecycle | 智能体生命周期 | request-shutdown, approve-shutdown, idle |
spawn | 进程生成 | spawn [后端] [命令] |
identity | 身份管理 | show, set |
所有命令都支持 --json 参数以获取机器可读的输出。将该标志放在子命令之前:
clawteam --json team discover
clawteam --json board show my-team
clawteam --json task list my-team --status pending
inbox receive 会消耗消息。使用 inbox peek 进行非消耗性读取。--blocked-by 时,任务状态会自动设置为 blocked。blockedBy 中列出该任务的任务的阻塞状态。priority;对紧急的阻塞解除任务和生产环境修复使用 high。clawteam spawn 默认使用 tmux、git 工作树隔离和 skip-permissions。clawteam launch 也遵循 skip_permissions,因此模板工作者不再因审批提示而停滞。clawteam spawn 生成时,身份环境变量会自动设置。board attach <团队> 在平铺的 tmux 布局中监视所有智能体。board show 的 JSON 输出和浏览器看板现在包含带有成员感知别名的消息历史记录,这对于收件箱分类和交接非常有用。--profile,而不是手动导出提供商环境变量。profile 是最终的运行时对象;preset 是用于生成配置的可复用模板。clawteam profile doctor claude。context inject 和 context conflicts 是安全交接跨工作树任务的推荐方式。references/cli-reference.md — 完整的 CLI 参考,包含命令、选项和数据模型references/workflows.md — 多智能体工作流:设置、生成协调、加入协议、计划审批、优雅关闭、监控模式每周安装量
–
代码仓库
GitHub 星标数
3.5K
首次出现
–
安全审计
ClawTeam is a framework-agnostic CLI tool for coordinating multiple AI agents as a team. It provides team/task management, inter-agent messaging, git worktree isolation, provider-aware runtime profiles, git context injection, snapshots, and terminal-based monitoring dashboards.
All operations are performed via the clawteam CLI. Data is stored in ~/.clawteam/ by default.
pip install clawteam
Requires Python 3.10+. For P2P transport support: pip install clawteam[p2p].
tmux installed (default spawn backend)claude, codex, gemini, kimi, nanobot, or openclawclawteam profile wizard)Teams — Named groups of agents with one leader and zero or more workers.
Inbox — File-based message queue per agent. receive is destructive; peek is not.
Tasks — Shared task board with pending, in_progress, completed, and blocked. Tasks support dependency chains and priorities.
Profiles — Reusable client/provider/runtime configs used by spawn and launch.
Presets — Shared provider templates used to generate one or more profiles.
Context — Git/worktree-aware context tools for overlap checks, recent changes, and prompt injection.
Board — Team dashboard with kanban tasks, inbox counts, and message history views, plus gource activity visualization.
export CLAWTEAM_AGENT_ID="leader-001"
export CLAWTEAM_AGENT_NAME="leader"
export CLAWTEAM_AGENT_TYPE="leader"
clawteam team spawn-team my-team -d "Project team" -n leader
clawteam task create my-team "Design system" -o leader
clawteam task create my-team "Implement feature" -o worker1
clawteam task create my-team "Write tests" -o worker2
clawteam board show my-team
# Inspect built-in provider templates
clawteam preset list
clawteam preset show moonshot-cn
# Generate a reusable profile from a preset
clawteam preset generate-profile moonshot-cn claude --name claude-kimi
# Or use the interactive TUI
clawteam profile wizard
# Claude Code on a fresh machine/home may need onboarding repair once
clawteam profile doctor claude
# Smoke-test the profile before using it in a team
MOONSHOT_API_KEY=... clawteam profile test claude-kimi
# Default path: tmux backend, claude command, git worktree isolation, skip-permissions on
clawteam spawn --team my-team --agent-name worker1 --task "Implement the auth module"
clawteam spawn --team my-team --agent-name worker2 --task "Write unit tests"
# Explicit backend and command
clawteam spawn tmux claude --team my-team --agent-name worker3 --task "Build API endpoints"
clawteam spawn subprocess claude --team my-team --agent-name worker4 --task "Run linting"
# Recommended for non-default providers/models
clawteam spawn tmux --profile claude-kimi --team my-team --agent-name worker5 --task "Build API endpoints"
clawteam spawn subprocess --profile gemini-vertex --team my-team --agent-name worker6 --task "Run linting"
clawteam board attach my-team
clawteam inbox send my-team worker1 "Start implementing the auth module"
clawteam board live my-team --interval 3
| Setting | Default | Override |
|---|---|---|
| Backend | tmux | clawteam spawn subprocess ... |
| Command | claude | clawteam spawn tmux my-cmd ... |
| Workspace | auto (git worktree) | --no-workspace or config workspace=never |
Use --profile whenever you need a non-default provider, model, endpoint, or auth mapping.
# Create with dependencies
clawteam task create my-team "Deploy" --blocked-by <impl-task-id>,<test-task-id>
# Create with priority
clawteam task create my-team "Hotfix prod issue" --priority high
# Update status
clawteam task update my-team <task-id> --status in_progress
clawteam task update my-team <task-id> --status completed
# Filter tasks
clawteam task list my-team --status blocked
clawteam task list my-team --owner worker1
clawteam task list my-team --priority high
clawteam task wait my-team
clawteam task wait my-team --timeout 300 --poll-interval 10
clawteam task wait my-team --agent coordinator
clawteam --json task wait my-team --timeout 600
Workers should not stop after completing the initial --task. The expected loop is:
# 1. Check tasks assigned to you
clawteam task list my-team --owner worker1
# 2. Finish any pending work, then check for new instructions
clawteam inbox receive my-team --agent worker1
# 3. If idle, notify the leader and keep monitoring for follow-ups
clawteam lifecycle idle my-team
Repeat the loop until the leader explicitly shuts the worker down.
clawteam context log my-team
clawteam context conflicts my-team
clawteam context inject my-team --agent worker1
Use these before reassigning work, continuing another worker's task, or merging overlapping changes.
clawteam team snapshot my-team --tag before-refactor
clawteam team snapshots my-team
clawteam team restore my-team --snapshot before-refactor
clawteam board gource my-team --log-only
clawteam board gource my-team --live
Prefer --log-only in headless environments.
Common validated CLIs include:
claudecodexgeminikiminanobotopenclawOpenClaw worker spawns are normalized automatically. Bare openclaw commands are promoted to the agent entrypoint and wired with --local, --session-id, and --message as needed.
Configure non-default providers through profile + preset instead of hardcoding env vars into prompts.
| Group | Purpose | Key Commands |
|---|---|---|
preset | Shared provider templates | list, show, generate-profile, bootstrap |
profile | Reusable client/provider configs | list, show, , , , |
All commands support --json for machine-readable output. Put the flag before the subcommand:
clawteam --json team discover
clawteam --json board show my-team
clawteam --json task list my-team --status pending
inbox receive consumes messages. Use inbox peek for non-destructive reads.blocked is auto-set when --blocked-by is specified at creation.blockedBy.priority; use high for urgent unblockers and production fixes.clawteam spawn defaults to tmux, git worktree isolation, and skip-permissions.clawteam launch also respects , so template workers no longer stall on approval prompts.references/cli-reference.md — Complete CLI reference with commands, options, and data modelsreferences/workflows.md — Multi-agent workflows: setup, spawn coordination, join protocol, plan approval, graceful shutdown, monitoring patternsWeekly Installs
–
Repository
GitHub Stars
3.5K
First Seen
–
Security Audits
AI Elements:基于shadcn/ui的AI原生应用组件库,快速构建对话界面
60,400 周安装
| Permissions | skip | --no-skip-permissions or config skip_permissions=false |
| Runtime profile | none | --profile <name> |
settestwizarddoctorteam | Team lifecycle | spawn-team, discover, status, request-join, approve-join, cleanup, snapshot, restore |
inbox | Messaging | send, broadcast, receive, peek, watch |
task | Task management | create, get, update, list, wait |
board | Monitoring and visualization | show, overview, live, attach, serve, gource |
context | Git/worktree context | diff, files, conflicts, log, inject |
plan | Plan approval | submit, approve, reject |
lifecycle | Agent lifecycle | request-shutdown, approve-shutdown, idle |
spawn | Process spawning | spawn [backend] [command] |
identity | Identity management | show, set |
skip_permissionsclawteam spawn.board attach <team> to watch all agents in a tiled tmux layout.board show JSON and the browser board now include message history with member-aware aliases, which is useful for inbox triage and handoffs.--profile for non-default providers/models instead of manually exporting provider env vars.profile is the final runtime object; preset is a reusable template for generating profiles.clawteam profile doctor claude once before spawning.context inject and context conflicts are the recommended way to hand off cross-worktree tasks safely.