agent-teams
Multi-Claude Agent Team Collaboration Driven by File System Protocol
Install & Use
Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:
Help me install this AI Skill: agent-teams. It is used for: Multi-Claude Agent Team Collaboration Driven by File System Protocol Full Skill content: https://321skill.com/skills/agent-teams-x/raw/index.md Read that page and install it.
The prompt includes a link to the full Skill content. You can also view the full content.
This Skill addresses the challenges of orchestrating and facilitating communication among multiple Claude processes during collaborative work. In practical development, when multiple AI agents are needed to handle different modules in parallel (such as frontend/backend separation or multi-file code review), developers often lack a lightweight coordination mechanism, while using databases or network layers proves too cumbersome.
The usage is straightforward: simply execute the claude command in your terminal with a team identifier parameter to create independent agent processes. Each agent runs in a separate tmux pane, exchanging messages via JSON files, with file locks (fcntl) ensuring concurrency safety. You can then assign tasks using natural language instructions, such as "Have the frontend agent implement the login page and the backend agent implement the login API." The system automatically creates team configurations, launches members, and monitors the task queue.
It is particularly well-suited for teams or individuals engaged in parallel development and multi-agent collaboration, especially those already familiar with tmux and the Claude CLI. For large-scale refactoring, code reviews, or cross-file implementations that involve handling multiple loosely-coupled subtasks simultaneously, it significantly boosts efficiency and avoids the context window limitations of a single agent.
We recommend using this tool when tasks have inherent parallelism, such as independent multi-module development or competitive analysis. Note that it is primarily designed for loosely-coupled tasks and is not suitable for scenarios requiring tight, sequential reasoning. Additionally, it requires the host environment to have tmux and the Claude CLI installed, with experimental features enabled.
Key Features
Unlike common agent coordination solutions based on MCP or HTTP, it relies entirely on the file system and tmux, eliminating the need for a network layer, database, or daemon process. This makes it more advantageous in offline environments or high-security scenarios, with minimal startup overhead.
Limitations
Requires tmux ≥ 2.0, the Claude CLI, and setting the environment variable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. It is only suitable for loosely-coupled parallel tasks and not for tightly sequential reasoning.
FAQ
How can I view the current status of a specific agent in the team?
Each agent runs in an independent tmux pane. You can directly view its output logs by attaching to tmux or switching panes. Additionally, the task files within the team configuration record progress.
What happens if an agent crashes?
Since each agent is an independent process, a crash does not affect other agents. You can restart the agent via tmux or manually recover the task by checking its corresponding inbox and task files.
Installation guide for AI assistants
If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:
Visit https://321skill.com/skills/agent-teams-x/raw/index.md to read the original Skill definition (Markdown format) for agent-teams, and install it according to the instructions.
Raw Markdown URL for AI: /skills/agent-teams-x/raw/index.md