--- name: claude-team-bf166e4c9732 description: Orchestrate multiple Claude Code workers via iTerm2 using the claude-team MCP server. Spawn workers with git worktrees, assign beads issues, monitor progress, and coordinate parallel development work. homepage: https://github.com/Martian-Engineering/claude-team metadata: {"clawdbot":{"emoji":"👥","os":["darwin"],"requires":{"bins":["mcporter"]}}} --- # Claude Team Claude-team is an MCP server that lets you spawn and manage teams of Claude Code sessions via iTerm2. Each worker gets their own terminal pane, optional git worktree, and can be assigned beads issues. ## Why Use Claude Team? - **Parallelism**: Fan out work to multiple agents working simultaneously - **Context isolation**: Each worker has fresh context, keeps coordinator context clean - **Visibility**: Real Claude Code sessions you can watch, interrupt, or take over - **Git worktrees**: Each worker can have an isolated branch for their work ## ⚠️ Important Rule **NEVER make code changes directly.** Always spawn workers for code changes. This keeps your context clean and provides proper git workflow with worktrees. ## Prerequisites - macOS with iTerm2 (Python API enabled: Preferences → General → Magic → Enable Python API) - claude-team MCP server configured in `~/.claude.json` ## Using via mcporter All tools are called through `mcporter call claude-team.`: ```bash mcporter call claude-team.list_workers mcporter call claude-team.spawn_workers workers='[{"project_path":"/path/to/repo","bead":"cp-123"}]' ``` ## Core Tools ### spawn_workers Create new Claude Code worker sessions. ```bash mcporter call claude-team.spawn_workers \ workers='[{ "project_path": "/path/to/repo", "bead": "cp-123", "annotation": "Fix auth bug", "use_worktree": true, "skip_permissions": true }]' \ layout="auto" ``` **Worker config fields:** - `project_path`: Required. Path to repo or "auto" (uses CLAUDE_TEAM_PROJECT_DIR) - `bead`: Optional beads issue ID — worker will follow beads workflow - `annotation`: Task description (shown on badge, used in branch name) - `prompt`: Additional instructions (if no bead, this is their assignment) - `use_worktree`: Create isolated git worktree (default: true) - `skip_permissions`: Start with --dangerously-skip-permissions (default: false) - `name`: Optional worker name override (auto-picks from themed sets otherwise) **Layout options:** - `"auto"`: Reuse existing claude-team windows, split into available space - `"new"`: Always create fresh window (1-4 workers in grid layout) ### list_workers See all managed workers: ```bash mcporter call claude-team.list_workers mcporter call claude-team.list_workers status_filter="ready" ``` Status values: `spawning`, `ready`, `busy`, `closed` ### message_workers Send messages to one or more workers: ```bash mcporter call claude-team.message_workers \ session_ids='["Groucho"]' \ message="Please also add unit tests" \ wait_mode="none" ``` **wait_mode options:** - `"none"`: Fire and forget (default) - `"any"`: Return when any worker is idle - `"all"`: Return when all workers are idle ### check_idle_workers / wait_idle_workers Check or wait for workers to finish: ```bash # Quick poll mcporter call claude-team.check_idle_workers session_ids='["Groucho","Harpo"]' # Blocking wait mcporter call claude-team.wait_idle_workers \ session_ids='["Groucho","Harpo"]' \ mode="all" \ timeout=600 ``` ### read_worker_logs Get conversation history: ```bash mcporter call claude-team.read_worker_logs \ session_id="Groucho" \ pages=2 ``` ### examine_worker Get detailed status including conversation stats: ```bash mcporter call claude-team.examine_worker session_id="Groucho" ``` ### close_workers Terminate workers when done: ```bash mcporter call claude-team.close_workers session_ids='["Groucho","Harpo"]' ``` ⚠️ **Worktree cleanup**: Workers with worktrees commit to ephemeral branches. After closing: 1. Review commits on the worker's branch 2. Merge or cherry-pick to a persistent branch 3. Delete the branch: `git branch -D ` ### bd_help Quick reference for beads commands: ```bash mcporter call claude-team.bd_help ``` ## Worker Identification Workers can be referenced by any of: - **Internal ID**: Short hex string (e.g., `3962c5c4`) - **Terminal ID**: `iterm:UUID` format - **Worker name**: Human-friendly name (e.g., `Groucho`, `Aragorn`) ## Workflow: Assigning a Beads Issue ```bash # 1. Spawn worker with a bead assignment mcporter call claude-team.spawn_workers \ workers='[{ "project_path": "/Users/phaedrus/Projects/myrepo", "bead": "proj-abc", "annotation": "Implement config schemas", "use_worktree": true, "skip_permissions": true }]' # 2. Worker automatically: # - Creates worktree with branch named after bead # - Runs `bd show proj-abc` to understand the task # - Marks issue in_progress # - Implements the work # - Closes the issue # - Commits with issue reference # 3. Monitor progress mcporter call claude-team.check_idle_workers session_ids='["Groucho"]' mcporter call claude-team.read_worker_logs session_id="Groucho" # 4. When done, close and merge mcporter call claude-team.close_workers session_ids='["Groucho"]' # Then: git merge or cherry-pick from worker's branch ``` ## Workflow: Parallel Fan-Out ```bash # Spawn multiple workers for parallel tasks mcporter call claude-team.spawn_workers \ workers='[ {"project_path": "auto", "bead": "cp-123", "annotation": "Auth module"}, {"project_path": "auto", "bead": "cp-124", "annotation": "API routes"}, {"project_path": "auto", "bead": "cp-125", "annotation": "Unit tests"} ]' \ layout="new" # Wait for all to complete mcporter call claude-team.wait_idle_workers \ session_ids='["Groucho","Harpo","Chico"]' \ mode="all" # Review and close mcporter call claude-team.close_workers \ session_ids='["Groucho","Harpo","Chico"]' ``` ## Best Practices 1. **Use beads**: Assign `bead` IDs so workers follow proper issue workflow 2. **Use worktrees**: Keeps work isolated, enables parallel commits 3. **Skip permissions**: Workers need `skip_permissions: true` to write files 4. **Monitor, don't micromanage**: Let workers complete, then review 5. **Merge carefully**: Review worker branches before merging to main 6. **Close workers**: Always close when done to clean up worktrees ## HTTP Mode (Streamable HTTP Transport) For persistent server operation, claude-team can run as an HTTP server. This keeps the MCP server running continuously with persistent state, avoiding cold starts. ### Starting the HTTP Server Run the claude-team HTTP server directly: ```bash # From the claude-team directory uv run python -m claude_team_mcp --http --port 8766 # Or specify the directory explicitly uv run --directory /path/to/claude-team python -m claude_team_mcp --http --port 8766 ``` For automatic startup on login, use launchd (see the "launchd Auto-Start" section below). ### mcporter.json Configuration Once the HTTP server is running, configure mcporter to connect to it. Create `~/.mcporter/mcporter.json`: ```json { "mcpServers": { "claude-team": { "transport": "streamable-http", "url": "http://127.0.0.1:8766/mcp", "lifecycle": "keep-alive" } } } ``` ### Benefits of HTTP Mode - **Persistent state**: Worker registry survives across CLI invocations - **Faster responses**: No Python environment startup on each call - **External access**: Can be accessed by cron jobs, scripts, or other tools - **Session recovery**: Server tracks sessions even if coordinator disconnects ### Connecting from Claude Code Update your `.mcp.json` to use HTTP transport: ```json { "mcpServers": { "claude-team": { "transport": "streamable-http", "url": "http://127.0.0.1:8766/mcp" } } } ``` ## launchd Auto-Start To automatically start the claude-team server on login, use the bundled setup script. ### Quick Setup Run the setup script from the skill's assets directory: ```bash # From the skill directory ./assets/setup.sh # Or specify a custom claude-team location CLAUDE_TEAM_DIR=/path/to/claude-team ./assets/setup.sh ``` ### What the Setup Does The setup script: 1. Detects your `uv` installation path 2. Creates the log directory at `~/.claude-team/logs/` 3. Generates a launchd plist from `assets/com.claude-team.plist.template` 4. Installs it to `~/Library/LaunchAgents/com.claude-team.plist` 5. Loads the service to start immediately The plist template uses `uv run` to start the HTTP server on port 8766, configured for iTerm2 Python API access (Aqua session type). ### Managing the Service ```bash # Stop the service launchctl unload ~/Library/LaunchAgents/com.claude-team.plist # Restart (re-run setup) ./assets/setup.sh # Check if running launchctl list | grep claude-team # View logs tail -f ~/.claude-team/logs/stdout.log tail -f ~/.claude-team/logs/stderr.log ``` ### Troubleshooting launchd ```bash # Check for load errors launchctl print gui/$UID/com.claude-team # Force restart launchctl kickstart -k gui/$UID/com.claude-team # Remove and reload (if plist changed) launchctl bootout gui/$UID/com.claude-team launchctl bootstrap gui/$UID ~/Library/LaunchAgents/com.claude-team.plist ``` ## Cron Integration For background monitoring and notifications, claude-team supports cron-based worker tracking. ### Worker Tracking File Claude-team writes worker state to `~/.claude-team/memory/worker-tracking.json`: ```json { "workers": { "Groucho": { "session_id": "3962c5c4", "bead": "cp-123", "annotation": "Fix auth bug", "status": "busy", "project_path": "/Users/phaedrus/Projects/myrepo", "started_at": "2025-01-05T10:30:00Z", "last_activity": "2025-01-05T11:45:00Z" }, "Harpo": { "session_id": "a1b2c3d4", "bead": "cp-124", "annotation": "Add API routes", "status": "idle", "project_path": "/Users/phaedrus/Projects/myrepo", "started_at": "2025-01-05T10:30:00Z", "last_activity": "2025-01-05T11:50:00Z", "completed_at": "2025-01-05T11:50:00Z" } }, "last_updated": "2025-01-05T11:50:00Z" } ``` ### Cron Job for Monitoring Completions Create a monitoring script at `~/.claude-team/scripts/check-workers.sh`: ```bash #!/bin/bash # Check for completed workers and send notifications TRACKING_FILE="$HOME/.claude-team/memory/worker-tracking.json" NOTIFIED_FILE="$HOME/.claude-team/memory/notified-workers.json" TELEGRAM_BOT_TOKEN="${TELEGRAM_BOT_TOKEN}" TELEGRAM_CHAT_ID="${TELEGRAM_CHAT_ID}" # Exit if tracking file doesn't exist [ -f "$TRACKING_FILE" ] || exit 0 # Initialize notified file if needed [ -f "$NOTIFIED_FILE" ] || echo '{"notified":[]}' > "$NOTIFIED_FILE" # Find idle workers that haven't been notified IDLE_WORKERS=$(jq -r ' .workers | to_entries[] | select(.value.status == "idle") | .key ' "$TRACKING_FILE") for worker in $IDLE_WORKERS; do # Check if already notified ALREADY_NOTIFIED=$(jq -r --arg w "$worker" '.notified | index($w) != null' "$NOTIFIED_FILE") if [ "$ALREADY_NOTIFIED" = "false" ]; then # Get worker details BEAD=$(jq -r --arg w "$worker" '.workers[$w].bead // "no-bead"' "$TRACKING_FILE") ANNOTATION=$(jq -r --arg w "$worker" '.workers[$w].annotation // "no annotation"' "$TRACKING_FILE") # Send Telegram notification MESSAGE="🤖 Worker *${worker}* completed 📋 Bead: \`${BEAD}\` 📝 ${ANNOTATION}" curl -s -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \ -d chat_id="$TELEGRAM_CHAT_ID" \ -d text="$MESSAGE" \ -d parse_mode="Markdown" > /dev/null # Mark as notified jq --arg w "$worker" '.notified += [$w]' "$NOTIFIED_FILE" > "${NOTIFIED_FILE}.tmp" mv "${NOTIFIED_FILE}.tmp" "$NOTIFIED_FILE" fi done ``` Make it executable: ```bash chmod +x ~/.claude-team/scripts/check-workers.sh ``` ### Crontab Entry Add to crontab (`crontab -e`): ```cron # Check claude-team workers every 2 minutes */2 * * * * TELEGRAM_BOT_TOKEN="your-bot-token" TELEGRAM_CHAT_ID="your-chat-id" ~/.claude-team/scripts/check-workers.sh ``` ### Environment Setup Set Telegram credentials in your shell profile (`~/.zshrc`): ```bash export TELEGRAM_BOT_TOKEN="123456789:ABCdefGHIjklMNOpqrsTUVwxyz" export TELEGRAM_CHAT_ID="-1001234567890" ``` ### Alternative: Using clawdbot for Notifications If you have clawdbot configured, you can send notifications through it instead: ```bash # In check-workers.sh, replace the curl command with: clawdbot send --to "$TELEGRAM_CHAT_ID" --message "$MESSAGE" --provider telegram ``` ### Clearing Notification State When starting a fresh batch of workers, clear the notified list: ```bash echo '{"notified":[]}' > ~/.claude-team/memory/notified-workers.json ``` --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/claude-team/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/claude-team/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Product Manager Specialties: Backend, DevOps Tools: Iterm2, Mcporter Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: a380ed923f130495a6c88f2765cd7df381ab8d74ce4e89a0a26f0087d16dfea1