Skip to content

⛡️ Multi-agent fleet management CLI built for OpenClaw, Claude Code, and any AI agent stack to orchestrate, monitor, judge reliability, and route intelligently across any runtime with delta tracking 🦞

License

Notifications You must be signed in to change notification settings

oguzhnatly/fleet

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

29 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Fleet

Multi-agent fleet management for OpenClaw

One CLI to monitor, manage, and orchestrate your entire AI agent fleet.

πŸ“– Read the story behind this β†’

CI ClawHub License Bash 4+

Quick Start β€’ Commands β€’ Patterns β€’ Configuration β€’ Docs


You're running multiple OpenClaw gateways: a coordinator that thinks, employees that code, review, deploy, and research. Fleet is the operational layer that was missing. One CLI that gives your coordinator full visibility, control, and judgment over the entire fleet.

See what changed. Dispatch tasks. Learn which agents actually deliver, and route work to whoever you can trust. Works with any runtime.

Built for AI agents to manage AI agents. Works on any system 🦞

Fleet Demo

Why Fleet?

πŸ” Visibility Β· Know which agents are up, which CI is red, what changed overnight. One command, full picture.

πŸ“Š Delta tracking Β· SITREP remembers the last run. Only shows what changed. No noise.

πŸ”§ Zero config Β· fleet init detects running gateways, discovers your workspace, links itself to PATH. One command to go from clone to operational.

🧩 Modular · Each command is a separate file. Adding a new command means dropping a .sh file in lib/commands/. No monolith, no framework.

⚑ Agent native · Designed to be used by agents, not just humans. The SKILL.md teaches any OpenClaw agent to manage a fleet autonomously, install dependencies, and adapt to any environment. If bash isn't available, your agent figures out another way.

πŸ“¦ Pattern library Β· Solo empire, dev team, research lab. Pre built configs for common setups.

Contents

Quick Start

# Install via ClawHub
clawhub install fleet

# Or via skills.sh (works with Claude Code, Codex, Cursor, Windsurf, and more)
npx skills add oguzhnatly/fleet

# Or clone directly
git clone https://github.com/oguzhnatly/fleet.git
fleet/bin/fleet init    # links PATH, detects gateways, creates config

# Check your fleet
fleet agents
fleet health
fleet sitrep

Commands

Monitoring

Command Description
fleet health Health check all gateways and endpoints
fleet agents Show agent fleet with live status and latency
fleet sitrep [hours] Full SITREP with delta tracking
fleet audit Check for misconfigurations and risks

Development

Command Description
fleet ci [filter] GitHub CI status across all repos
fleet skills List installed ClawHub skills

Operations

Command Description
fleet backup Backup gateway configs, cron jobs, auth profiles
fleet restore Restore from latest backup
fleet init Interactive setup with gateway detection
See more command output examples

fleet agents

Agent Fleet
───────────
  β¬’ coordinator      coordinator      claude-opus-4               :48391 online 13ms

  β¬’ coder            implementation   codex                       :48520 online 8ms
  β¬’ reviewer         code-review      codex                       :48540 online 9ms
  ⬑ deployer         deployment       codex                       :48560 unreachable
  β¬’ qa               quality-assurance codex                      :48580 online 7ms

fleet audit

Fleet Audit
───────────

Configuration
  βœ… Config file exists at ~/.fleet/config.json
  βœ… Config permissions: 600
  βœ… All agent tokens configured
  βœ… No placeholder tokens found

Agents
  βœ… All 5 agents online
  βœ… Main gateway healthy (:48391)

CI
  βœ… gh CLI available
  βœ… All CI green

Resources
  βœ… Memory usage: 43%
  βœ… Disk usage: 7%

Backups
  βœ… Last backup: 2 day(s) ago

  All clear Β· 11 checks passed, 0 warnings

fleet ci

CI Status
─────────

  frontend (myorg/frontend)
    βœ… Update homepage (main) passed 2h ago
    βœ… Fix footer (main) passed 4h ago

  backend (myorg/backend)
    ❌ Add endpoint (main) failed 1h ago
    βœ… Fix auth (main) passed 3h ago

fleet health

Fleet Health Check
──────────────────
  βœ… coordinator (:48391) 12ms

Endpoints
  βœ… website (200) 234ms
  βœ… api (200) 89ms
  ❌ docs UNREACHABLE

Services
  βœ… openclaw-gateway

Patterns

Fleet supports any agent organization pattern. Three common ones:

Solo Empire

One brain, many hands. The indie hacker setup.

         Coordinator (Opus)
        /     |      \
    Coder  Reviewer  Deployer
   (Codex)  (Codex)   (Codex)

Development Team

Team leads managing specialized developers.

              Orchestrator (Opus)
            /        |         \
      FE Lead     BE Lead     QA Lead
     (Sonnet)    (Sonnet)    (Sonnet)
       / \          |           |
    Dev1  Dev2    Dev1       Tester
   (Codex)(Codex)(Codex)    (Codex)

Research Lab

Specialized agents for knowledge work.

            Director (Opus)
          /     |      \       \
    Scraper  Analyst  Writer  Fact Check
   (Codex)  (Sonnet) (Sonnet)  (Codex)

See docs/patterns.md for detailed guides and examples/ for configs.

Configuration

Fleet reads ~/.fleet/config.json. Create one with fleet init or manually:

{
  "workspace": "~/workspace",
  "gateway": {
    "port": 48391,
    "name": "coordinator"
  },
  "agents": [
    { "name": "coder", "port": 48520, "role": "implementation", "model": "codex" },
    { "name": "reviewer", "port": 48540, "role": "code review", "model": "codex" }
  ],
  "endpoints": [
    { "name": "website", "url": "https://myapp.com" },
    { "name": "api", "url": "https://api.myapp.com/health" }
  ],
  "repos": [
    { "name": "frontend", "repo": "myorg/frontend" },
    { "name": "backend", "repo": "myorg/backend" }
  ]
}

Everything is configurable. No hardcoded ports, models, or names. Your fleet, your way.

See docs/configuration.md for the full schema.

Environment Variables

Variable Description Default
FLEET_CONFIG Config file path ~/.fleet/config.json
FLEET_WORKSPACE Workspace override Config value
FLEET_STATE_DIR State persistence ~/.fleet/state
NO_COLOR Disable colors (unset)

Architecture

fleet/
β”œβ”€β”€ bin/fleet              # Entry point
β”œβ”€β”€ lib/
β”‚   β”œβ”€β”€ core/              # Config, output, state management
β”‚   β”‚   β”œβ”€β”€ config.sh      # JSON config loader
β”‚   β”‚   β”œβ”€β”€ output.sh      # Colors, formatting, HTTP helpers
β”‚   β”‚   └── state.sh       # Delta state persistence
β”‚   └── commands/           # One file per command
β”‚       β”œβ”€β”€ agents.sh       # Agent fleet status
β”‚       β”œβ”€β”€ audit.sh        # Misconfiguration checker
β”‚       β”œβ”€β”€ backup.sh       # Config backup/restore
β”‚       β”œβ”€β”€ ci.sh           # GitHub CI integration
β”‚       β”œβ”€β”€ health.sh       # Endpoint health checks
β”‚       β”œβ”€β”€ init.sh         # Interactive setup
β”‚       β”œβ”€β”€ sitrep.sh       # Structured status reports
β”‚       └── skills.sh       # ClawHub skill listing
β”œβ”€β”€ templates/configs/      # Config templates
β”œβ”€β”€ examples/               # Architecture pattern examples
β”‚   β”œβ”€β”€ solo-empire/
β”‚   β”œβ”€β”€ dev-team/
β”‚   └── research-lab/
β”œβ”€β”€ docs/                   # Documentation
β”œβ”€β”€ tests/                  # Integration tests
β”œβ”€β”€ SKILL.md                # ClawHub agent instructions
└── .github/workflows/      # CI pipeline

Modular by design. Each command is a separate file. Add your own by dropping a .sh file in lib/commands/.

For AI Agents

Fleet ships with a SKILL.md that any AI coding agent can read. Install it and your coordinator automatically knows how to manage the fleet:

clawhub install fleet          # OpenClaw agents
npx skills add oguzhnatly/fleet  # Claude Code, Codex, Cursor, Windsurf, etc.

The agent reads the skill file, learns the commands, and runs health checks autonomously during heartbeat cycles.

Requirements

Dependency Version Notes
bash 4+ macOS ships 3.2, run brew install bash
python3 3.10+ No pip packages needed
curl any Pre installed on most systems
OpenClaw any Gateway support required
gh CLI any Optional, for CI commands

Roadmap

Fleet is being built in stages. Each version makes it more active, more intelligent, and more universal.

v1 Β· Shipped βœ…

Visibility layer. Monitoring, delta SITREP, CI status, backup, audit. Fleet can see the entire operation.

v2 Β· Active (task dispatch and session steering)

Fleet stops being observational and becomes directive.

  • fleet task <agent> "<prompt>" β€” dispatch a task to any agent from the CLI
  • fleet steer <agent> "<message>" β€” send a mid-session correction to a running agent
  • fleet watch <agent> β€” live log tail from a specific agent session
  • fleet parallel "<task>" β€” describe a high-level task, fleet breaks it into subtasks, assigns to the right agents, runs in parallel
  • fleet log β€” append-only structured log of everything dispatched and received
  • fleet kill <agent> β€” graceful session end

v3 Β· Planned (reliability scoring and agent trust)

Fleet learns which agents actually deliver, not just which ones are alive.

  • fleet trust β€” trust matrix for all agents: delivery rate, rejection rate, consistency, trend
  • fleet score <agent> β€” detailed PDR breakdown with failure patterns and trajectory
  • Reliability-weighted task routing for fleet parallel (dispatch to best agent for task type, not just whoever is idle)
  • Trend scoring: an agent at 30% reject rate trending down ranks higher than one at 10% trending flat

PDR (Provenance-Driven Reputation): delivered / dispatched * time_modifier. Built on observable behavior from the fleet log, not self-reported health.

v4 Β· Planned (cross-runtime adapter layer)

Fleet works with any agent on any runtime, not just OpenClaw.

  • Standardized adapter interface: OpenClaw, Claude Code, Codex, generic HTTP, Docker
  • fleet adapters β€” list registered adapters and their status
  • fleet runtime add <name> <type> β€” register a new runtime without editing config manually
  • Backward compatible: existing configs default to OpenClaw adapter

v5 Β· Planned (server mode and HTTP API)

Fleet becomes an embeddable data source, not just a CLI.

  • fleet serve β€” start fleet as a local HTTP server
  • REST API: /agents, /sitrep, /trust, /log, /task, /steer
  • External tools, dashboards, and CI systems can consume fleet data
  • Foundation for a future cloud sync tier

Contributing

Issues and PRs welcome. See CONTRIBUTING.md for guidelines.

Built by a solo operation, for solo operations.

Support

If Fleet is useful to you, consider supporting its development:

Sponsor on GitHub

License

MIT Β· Oguzhan Atalay

About

⛡️ Multi-agent fleet management CLI built for OpenClaw, Claude Code, and any AI agent stack to orchestrate, monitor, judge reliability, and route intelligently across any runtime with delta tracking 🦞

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Contributors

Languages