A harness-agnostic, MCP-free way to direct a fleet of AI agents across your projects — Claude Code, Cursor, and Codex, all on one fleet. The fleet layer over cyberlegion: it carries only fleet-specific logic — ships, missions, and the Council view, derived from SDD state — and depends up on cyberlegion for every mechanism verb (register, mail, spawn, prune).
You're the Council — the human. You give directions and make decisions; the fleet is autonomous and carries them out. A ship is a workspace: a folder, a repository, or a worktree; your fleet is all the ships you've enlisted, across one project or many.
No install required — run with npx:
npx cyberfleet <command>Or pin to an exact version for reproducible hooks:
npx cyberfleet@0.0.6 <command>npx cyberfleet missions # the Council view: ships × mission × gate × leash
npx cyberfleet jump <peer> # focus a ship's session, or print its worktree path
npx cyberfleet pause <peer> # flip a ship's status marker
npx cyberfleet gate approve <cr> <gate> # stubbed — Council ratification can't be relayed via CLI| Option | Description |
|---|---|
--root <path> / --space <path> |
cyberlegion hub root (overrides the global hub / $CYBERLEGION_ROOT) |
--format <format> |
Output format: toon (default) or json |
See packages/cyberfleet/readme.md for the full command
reference.
The npm package, packages/cyberfleet, is also the agent plugin root. It ships — the fleet & crew
personas (Pod, Operator, Crimp, Mechanic) and the headless-operator subagent
for unattended dispatch.
/plugin marketplace add cyberuni/cyberfleet
/plugin install cyberfleet
Full docs: https://cyberuni.github.io/cyberfleet
See CONTRIBUTING.md and AGENTS.md.