Claude DevFleet Multi-Agent Orchestration
Dispatch parallel Claude Code agents in isolated git worktrees with Muse: plan a project into a mission DAG, auto-dispatch on dependency completion, monitor progress, read structured reports.
- What
- Dispatch parallel Claude Code agents in isolated git worktrees with Muse: plan a project into a mission DAG, auto-dispatch on dependency completion, monitor progress, read structured reports.
- Cost
- Free
- Needs
- Use "Claude DevFleet Multi-Agent Orchestration" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a full multi-agent orchestration workflow on top of the Claude DevFleet server. The flow is Plan, Dispatch, Monitor, Report. plan_project turns a plain-language description into a project with a mission DAG, chained by depends_on with auto_dispatch set; you show the plan, get approval, then dispatch the root mission while the rest auto-start as dependencies complete. Each agent runs in an isolated git worktree with full tooling and auto-merges on completion. Tools cover the whole lifecycle: create_project, create_mission, dispatch_mission, cancel_mission, wait_for_mission (blocks up to the timeout, prefer polling get_mission_status every 30-60 seconds for long runs), get_report (files changed, what was done, errors, next steps), get_dashboard (running agents, stats, activity), list_projects, list_missions. Concurrency runs up to 3 agents by default via DEVFLEET_MAX_AGENTS, with the mission watcher queueing the rest. Guidelines are firm: always confirm the plan with the user before dispatching unless they said go ahead, read a failed mission's report before retrying, never create circular dependencies, and merge conflicts stay on the agent's worktree branch for manual resolution. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the DevFleet server is a separate project (github.com/LEC-AI/claude-devfleet) you install and run yourself, then connect over MCP to localhost:18801; verify the process on that port is the DevFleet binary you installed before connecting. Every agent is a full session, so token costs multiply; poll instead of blocking waits on long missions. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Claude DevFleet Multi-Agent Orchestration" with your Muse. Prerequisites: install and run the DevFleet server separately from https://github.com/LEC-AI/claude-devfleet, then connect it over MCP: claude mcp add devfleet --transport http http://localhost:18801/mcp. Verify the process listening on port 18801 is the DevFleet binary you installed (localhost MCP servers are a trust decision). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/claude-devfleet/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Plan a project for [feature/refactor]: [description]" or "Dispatch the missions for project [id] after I approve the plan." 3. Let Muse plan the mission DAG, confirm it, dispatch, and poll get_mission_status. Read each mission's get_report before the next step. Tip: set DEVFLEET_MAX_AGENTS to match your budget; each agent is a full session and token costs multiply. Safety: a skill is plain-text instructions; it runs nothing by itself. Always confirm the plan before dispatching, and merge conflicts stay on the agent's worktree branch for manual resolution.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.