Claude Devfleet

This spins up multiple Claude Code agents in parallel, each working in its own isolated git worktree. You give it a complex project prompt, it breaks it into missions with dependencies, and dispatches agents that auto-merge as they finish. Useful when you'd normally tackle a feature in stages but want them happening concurrently instead. The orchestration happens through a separate DevFleet server you run locally on port 18801. It handles up to 3 agents at once by default, queues the rest, and gives you structured reports on what each agent changed. The auto-dispatch chain works well if you trust the plan, otherwise you can gate each mission manually.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill claude-devfleet --agent claude-code

Installs into .claude/skills of the current project.

Files

Claude DevFleet Multi-Agent Orchestration

When to Use

Use this skill when you need to dispatch multiple Claude Code agents to work on coding tasks in parallel. Each agent runs in an isolated git worktree with full tooling.

Setup

The DevFleet server is a separate project, not bundled with ECC. Install and run it from its repository first: https://github.com/LEC-AI/claude-devfleet

Then connect the running instance via MCP:

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 (see SECURITY.md on localhost MCP servers).

How It Works

User → "Build a REST API with auth and tests"
  ↓
plan_project(prompt) → project_id + mission DAG
  ↓
Show plan to user → get approval
  ↓
dispatch_mission(M1) → Agent 1 spawns in worktree
  ↓
M1 completes → auto-merge → auto-dispatch M2 (depends_on M1)
  ↓
M2 completes → auto-merge
  ↓
get_report(M2) → files_changed, what_done, errors, next_steps
  ↓
Report back to user