@chankov/agent-fleet weekly downloads statistics

Agent Fleet

<p align="center"> <img src="https://raw.githubusercontent.com/chankov/agent-fleet/main/docs/assets/branding/agent-fleet-logo-white-v1.png" alt="Agent Fleet — Many agents. One direction." width="800"> </p>

Operate a coding-agent fleet — not just one chat session.

Agent Fleet is a multi-agent orchestration system for AI coding agents, built pi-first: a thin dispatcher routes work to specialist agents under a Verification Contract, whole teams spawn as tiled workspaces you can snapshot and resume, agents message each other over a shared coms plane, a Hermes Desktop panel shows you the whole fleet at a glance — and a library of 29 production-grade lifecycle skills and 15 personas keeps every agent disciplined.

Three things make it unusual:

1. You run it on the subscriptions you already pay for — Codex/ChatGPT, GitHub Copilot, Claude, Ollama — mixed inside one fleet, alongside models running locally on your own GPU. How ↓
2. The dispatcher never drowns. Research output, subagent dumps and specialist chatter stay out of the orchestrator's context window — on disk, behind file paths. How ↓
3. You can actually see it. Tiled panes in herdr, a live session panel in Hermes Desktop, and questions relayed to your phone when an agent needs a human. How ↓

One coding agent: pi. Everything installs for pi and nothing else. Claude Code appears throughout this README as a coms peer — a real Claude pane bridged into the fleet to answer other agents' questions and run cross-model review. That is its whole role; it is not an install target. The bridge ↓

---

The fleet at a glance

flowchart TD
    You(["<b>You</b><br/>terminal · desktop · phone"])

    subgraph Control["Control surfaces"]
        Herdr["<b>herdr</b><br/>tiled peer workspaces<br/>snapshot · resume"]
        Desktop["<b>Hermes Desktop plugin</b><br/>live session panel<br/>who is blocked · what it is doing"]
        Phone["<b>Hermes relay</b><br/>hub questions → Telegram<br/>answer from anywhere"]
    end

    Hub["<b>agent-hub</b> — thin dispatcher<br/>owns the Verification Contract on disk"]

    subgraph Team["Specialist team (.pi/agents/teams.yaml)"]
        Specialists["planner · plan-reviewer · builder<br/>test-engineer · code-reviewer · documenter"]
    end

    Research["<b>research helpers</b> — read-only<br/>findings go to disk, never to the dispatcher"]
    Coms["<b>coms</b> — peer data plane<br/>pi ⇄ pi ⇄ Claude Code panes"]

    You --> Control
    Control --> Hub
    Hub --> Specialists
    Specialists --> Research
    Hub <--> Coms
    Specialists <--> Coms
    Coms --> Desktop

Layer	Job
agent-hub	One pi runtime — direct operator work or thin-context orchestration under a Verification Contract
herdr	Fleet control plane — tiled peer workspaces, presence, snapshot/resume
coms	Peer data plane — bidirectional messaging between agents (including Claude Code panes)
Hermes Desktop plugin	Live fleet panel in the Hermes desktop app — every session, its state, what it is doing, and who is waiting on you
Hermes relay	Remote human control — relay hub questions to your phone and answer them there
Codex conductor (experimental)	Android-initiated, approval-gated delegation to live coms peers through a user-systemd service
Skills + personas	Lifecycle discipline — how to spec, plan, build, verify, review, and ship

---

Quick Start

Install into a repository

From the target repository. The first install goes through npx — just fleet does not exist yet, because the managed justfile region is one of the things setup writes:

cd ~/projects/my-app
npx @chankov/agent-fleet@latest setup

In a real TTY that opens the installer: pick Default, Full, or Full + all features, edit the exact feature snapshot, read the reconciliation plan, then explicitly answer yes once. The third choice stores preset: "full" plus today's platform-compatible feature values; later releases never auto-enable newly added features. For automation, name the selection and consent:

npx @chankov/agent-fleet@latest setup --preset default --features none --yes

Default is the stable Fleet Core selection; it creates neither .claude/ nor voice configuration. Full keeps its existing stable platform-applicable catalogue semantics and may install the recorded Claude Code coms bridge. File installation is not a readiness claim: the final report distinguishes missing/unverified runtime dependencies and points to just fleet deps and just fleet doctor. The lifecycle requires no coding agent or model.…