Claude Code across your whole fleet.
A self-hosted control plane for running Claude Code on every machine you own. Connect a Claude account once, launch agents on any folder, and watch them work live, from the web or your favorite channel.
OAuth-only, never an API key. Self-hosted and fully Dockerized.
Refactor the auth handler and add tests for the token refresh path.
streaming live to the Fleet Hub…
How it works
Your whole fleet, in one place
A central Fleet Hub federates every machine, so a folder on a laptop in the next room and a server in another datacenter both feel like one product. Here is the loop, end to end.
Connect your Claude accounts
Log in with Claude OAuth, no API keys, ever, and manage multiple Claude accounts in one place. Credentials live in an encrypted vault on the Hub and are injected just-in-time on whichever machine an agent runs, so you never copy tokens between hosts.
Claude accounts
Manage every account in one place.
claude-user1
Claude Max · connected via OAuth
claude-user2
Claude Pro · connected via OAuth
claude-user3
Claude Pro · connected via OAuth
See and command every machine
Join a machine with a one-line script and its Runner dials home over a secure tunnel, surviving reboots. The Machines view gives you a live grid: online status, active agents, CPU and memory sparklines, disk, plus one-click Terminal, VS Code, and power controls.
Machines
4 onlineLive view of every machine in your fleet.
machine-2 · machine-3 and the rest of your fleet
Edit, run, and watch it work
Open any folder in the built-in editor, browse the file tree, edit with a full code editor, and drop into a host terminal, all scoped to the right machine and project. Launch an agent and every turn, tool call, and diff streams live, then replays on refresh.
› pytest tests/test_auth.py -q
✓ 14 passed in 1.92s
Manage many projects and trackers
Group folders into as many projects as you need, each backed by a GitHub repo, then pull work straight from your trackers, Jira and GitHub issues, side by side. Hand a ticket to an agent and it picks up the project, branch, and machine automatically.
- JiraPROJ-142Add token refresh testsIn Progress
- JiraPROJ-138Rotate Claude account leasesTo Do
- #91Bump auth dependenciesOpen
Features
Everything you need to run Claude Code at fleet scale
Always up, everything Dockerized, reproducible, and self-hosted on your own infrastructure.
One fleet, many machines
Operate agents across one or many machines from a single dashboard. Machines federate through the Hub and reconnect automatically after a reboot.
Live streaming and replay
Every turn, thinking block, tool call, and diff streams as it happens, and the full timeline replays on refresh so nothing is lost.
Many accounts, one vault
Manage multiple Claude accounts in one place, OAuth-only and no API keys. A central encrypted vault is the fleet-wide credential authority.
Drive it from anywhere
Kick off and follow agents from the Web UI or straight from Telegram, Slack, and email channels.
Authorized and audited
Every list and action is gated server-side, scoped per organization, and written to a tamper-evident audit log.
Projects, repos, and tickets
Group folders into projects backed by GitHub repos, and pull work straight from Jira and GitHub issues, then hand a ticket to an agent.
Architecture
A Hub in the middle, Runners on every machine
You talk to the Fleet Hub. It proxies over a secure tunnel to a Runner on each machine, where Claude Code actually executes.
You
- Web UI
- Telegram · Slack · Email
Fleet Hub
- Auth & orgs
- Tunnel · proxy
- Credential vault
Runners
- One per machine
- Folders & projects
- Claude Code engine
Runners auto-reconnect and survive reboots, so the fleet stays always up and always connected, no matter where your machines live.
Put your whole fleet to work.
Sign in to the Fleet Hub and launch your first agent in minutes.