← ClaudeAtlas

claude-devfleetlisted

Use when orchestrating parallel Claude Code agents via the Claude DevFleet MCP server - planning projects into mission DAGs, dispatching agents in isolated git worktrees, monitoring progress, and reading structured reports. Covers exact tool signatures, the auto_dispatch draft-status gotcha, and concurrency limits.
Mixard/fable-pack · ★ 1 · AI & Automation · score 74
Install: claude install-skill Mixard/fable-pack
# Claude DevFleet Multi-Agent Orchestration DevFleet (github.com/LEC-AI/claude-devfleet) dispatches multiple Claude Code agents in parallel, each in an isolated git worktree with auto-merge on completion. It is a separate server: install and run it from its repository first, then connect: ```bash claude mcp add devfleet --transport http http://localhost:18801/mcp ``` Before first use, verify the process listening on port 18801 is the DevFleet binary you installed (localhost MCP servers can be spoofed by other local processes). ## Tools | Tool | Purpose | |------|---------| | `plan_project(prompt)` | AI breaks a description into a project with chained missions; returns `project_id` + mission DAG | | `create_project(name, path?, description?)` | Create a project manually, returns `project_id` | | `create_mission(project_id, title, prompt, depends_on?, auto_dispatch?)` | Add a mission. `depends_on` is a list of mission ID strings, e.g. `["abc-123"]` | | `dispatch_mission(mission_id, model?, max_turns?)` | Start an agent on a mission | | `cancel_mission(mission_id)` | Stop a running agent | | `wait_for_mission(mission_id, timeout_seconds?)` | Block until completion (default timeout 600 s) | | `get_mission_status(mission_id)` | Non-blocking progress check | | `get_report(mission_id)` | Structured report: files changed, what was done, errors, next steps | | `get_dashboard()` | Running agents, slot usage, stats, recent activity | | `list_projects()` | Browse all projects | | `l