TonyHeadband

Fleet Manager — Development skill for Claude Code

Development community

Desktop command room for a fleet of Claude Code agents: start agents on your repos, see which are working, waiting on you or done, and answer, review or stop them from one window.

How to install Fleet Manager

This entry records only its repository, not the path inside it, so there is no exact command to give. Open TonyHeadband/fleet-manager and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Fleet Manager does

Desktop command room for a fleet of Claude Code agents: start agents on your repos, see which are working, waiting on you or done, and answer, review or stop them from one window. Orchestrators break a goal into steps run by specialist agents. Linux, Rust, egui.

Alternatives in Development

Mempalace Search — Search your memories across the MemPalace using semantic search with wing/room filtering 58.6k ★
Tmux Claude Session Manager — Run many Claude Code sessions across your projects, each in its own tmux session — then list them, see which a 380 ★
Device Control Agent — You are an autonomous macOS agent with full control of this device via two CLI tools: - steer — GUI automation 250 ★

README

fleet-manager

A desktop command room for a fleet of coding agents. Start several Claude Code agents on your repos, see at a glance which ones are working, which are waiting on you and which have finished, and answer, pause, review, stop or archive them from one window.

A task can be one agent you fly by hand, or an orchestrator that breaks the goal into steps and launches specialist agents for you to approve and watch. Where it is going (autopilot inside a policy you set, enforced specialist limits) is in [ROADMAP.md](ROADMAP.md).

**Status: v0.1, personal tool.** Linux only (x86_64 app; daemon on x86_64 and aarch64), Claude Code only, loopback only with no authentication. Expect breaking changes.

What it does

Tasks. A task is one agent session working toward a goal, in its own folder under the tasks root. Each repo it touches gets a git worktree on the task's branch, fleet/, so agents never step on each other or on your checkouts. Repos can be paths, git URLs or names fleet-manager remembers, and an agent can ask for another repo mid-session (you grant or refuse it from the card).
Orchestrated tasks. Pick a Type when you create a task: an orchestrator agrees the goal with you, proposes a breakdown you approve in the side panel, launches specialist agents, merges their branches and opens one PR after the repo's tests pass. The board shows the task as one group with a rolled-up status. See Orchestrated tasks.
A board driven by Claude Code hooks, not by scraping the terminal. Columns: Queued, Working, Needs you, Talking, Review. A card in Needs you says why: a permission prompt, a question, an error, or startup.
Act from the card. Answer, pause, resume, stop. The side panel shows the agent's live terminal (read-only) and the diff of every repo in the task.
Stop now, archive later. Stop ends the agent and keeps everything on disk: worktrees, branches, the task folder and its rec