Your fleet's owner key is not armed on this browser. The fleet stays visible without it: the key only arms actions that change something (Start, Steer, Update and so on).
Paste a DAG of sandboxed dispatches across your captains (JSON). A live graph view shows each node's honest grade and cost.
Fleet searchmemory, skills and observations across your captains
Each captain's memory stays its own. A result from another captain carries a ⚓ tag naming it; quote it as "As per <captain>, ...".
⚠ Peer unreachable: showing local-only results.
Homework—
Captain stats—
Billed tokens——
Cache reads——
Transcripts——
Corpus——
Where the tokens go—
Sessions vs agents—
Memory pipeline—
This captain has not reported a full scan yet.
Fleet Board // Tactical
NODES 0
No captains yet. A captain is a machine running Captain Memo, linked to this hub; each one you add appears here as a cell you can watch and command.
Add a captain // Linux · macOS · Windows
A captain is a machine running Captain Memo, linked to this hub. One line installs it, links it here, and keeps it updated. Pick the machine's OS:
—
01Run it on the new machineAny terminal there, as the user who will run the captain. It installs Bun if needed, and the captain keeps itself updated from then on.
02It shows up under Pending Within a minute the captain knocks on this hub and waits in the Pending zone below.
03Admit & sign to seal it inThe first time, you will set up your owner key (a password and a recovery code, both yours alone). Every later admit is one click.
This line is yours alone: it carries your repository credential and your fleet token. Treat it like a password.Prefer each step by hand? Guide ↗
Active Tasks // Fleet
LIVEVIA HUB 0ON HOST 0—
CaptainSessionCLIModeKindTokensAgeState
No tasks running.
Deployment Log // Stream
LIVE
No recent activity.
Owner key (hub-pinned)—
Seats
Seats—
Plan—
Federation token—
Last seen—
Hub—
Revision—
Controls
Owner key
Checking this browser's owner key against your fleet's…
Rotate federation token
Mints a new token and revokes the old one. Existing captains must be re-keyed: on each, run captain-memo federation connect with a bundle built from the new token (the Getting started guide shows how), then captain-memo restart.
⚠ Save this token now. It will not be shown again. Re-key your captains with it.
copied
Republish keys to fleet
Re-broadcast every connected captain's keys (owner-signed) so peers can reach each other. Fixes a captain that returns no fleet results. Requires the owner key armed.
Key mesh
Native sessions between captains
Each captain of yours takes its own signed list of the others that may start native sessions on it. Switching Native sessions on stays a per-captain choice, in its Safety settings.
Federation status
—
Gateways
Pending admit0
Active
No gateways have connected yet.
Apps
Add app
Pair a new device captain. Requires an armed owner key and an admitted gateway.