The approval that finds you
A blocked agent surfaces as buttons in Telegram. Tap once, and the pane keeps moving.
Torad Fleet · an OpenClaw plugin
in preview
Torad Fleet / the control room
Every coding agent you run, on one screen.
Torad Fleet is an OpenClaw plugin that finds every Claude Code, Codex, and Gemini session on your machine, ranks them by urgency, and takes your answer from your phone.
Free to run · your machine is the server · every action audited
left · the fleet, one session pulled forwardright · the same session in Telegram? · the approval, one tap
Free. Local. Yours.
The whole control room is free. Paid extras unlock with a key your machine verifies offline. Nothing meters you, nothing phones home to us.
$0the control room is free
4harnesses on one screen
scan-cleaninstalls with no dangerous flag
100%of actions audited
FreeThe whole control room ships free. Nothing in it is a trial.
Scan-clean installThe scanned bundle cannot run processes. Execution lives in one separate, readable helper.
Pay per featurePaid features unlock with an offline-verified license. There is no metered backend.
No rented cloudState is local SQLite. The web room binds to loopback. No Torad backend in the path.
What it is
Not another daemon. A plugin inside OpenClaw.
Fleet discovers your agent sessions over tmux, reads each transcript as it is written, and types back into the pane when you answer. Nothing new to babysit.
It compounds. One agent gets phone approvals. Three get ranked by urgency. A dozen stay legible.
A · the fleet in useB · the flow: a pane, b transcript, c plugin, d helper
The web control room
At your desk. Every session is a live tile, and the one that needs you is already pulled to the front.
Telegram
Away from it. Every session is a topic: turns stream in, replies land in the pane, and a blocked prompt becomes buttons you tap.
The web room binds to loopback. Telegram is the away-from-desk surface, by design.
Agent-to-agent
Your sessions can talk to each other.
Fleet ships an MCP server with two verbs: read what a sibling session said, send it the next move. You stop being the messenger between your own agents.
› seeStatus { sessionName: "repo-web" }
‹ "Migration finished. Typecheck is clean. Blocked on the API contract."
› sendMessage { sessionName: "repo-web", message: "Contract merged on main. Pull and wire the client." }
‹ ok · relayed into the pane
two verbs, exactly · seeStatus reads, sendMessage acts
A B · two agent sessionsQ · the host queue, on disk
Deliberately few verbs.
seeStatus returns a session's latest assistant message from its own transcript. sendMessage relays a prompt into its pane. Read, then act. Nothing else.
Durable by construction.
A relayed message rides the same on-disk queue as every other operation, committed before it is typed. A restart does not lose it.
Scoped like any tool.
It is an MCP server you add per agent. Give it to the session doing the orchestrating, not to everything with a keyboard.
Demo
Watch it run.
Six shipped features, one labeled preview.
Captured run · recording
Recording in production.
The fleet that ranks itself
Tiles carry provider, health, a live mini-terminal, and velocity. The session that needs you becomes the hero.
Works across four harnesses
Claude Code, Codex, Hermes, and Gemini share one wall. The matrix below states exactly how deep each one goes.
No rented cloud
The room runs on your machine with your own bot token. Telegram is the one network boundary, detailed below.
Execution, split out
The scanned bundle cannot spawn a process. One readable helper owns tmux, and they meet in a single audited table.
Built for the bad day
Mirroring keeps streaming when the helper is down. The doctor finds orphaned sessions and cleans them.
The preview chapter
- The operator wall. Every pane, live on one screen.
- The streamed terminal. A live stream with a delivery verdict: submitted, stuck, or unknown.
- The voice conductor. Drive the fleet by speaking to it.
- The cost Black Box. Per-session spend and diff, read from each transcript.
- The autonomous operator. Designed and gated, not wired in: today an agent only proposes, behind Apply or Dismiss.
Why Fleet
Everything else installs beside your setup. This installs into it.
Fleet is an OpenClaw plugin. Three things follow from that one fact.
Grow the tool you already run.
Fleet activates when your gateway starts. For an OpenClaw user it is not a second thing to adopt.
- Install is three steps, and one script does the first two. One command,
openclaw workspaces health, verifies the result. - A dry run previews discovery without creating a topic or sending a message: a safe first look.
It installs scan-clean. No dangerous flag.
OpenClaw hard-blocks any plugin whose source can spawn a process. Fleet splits brain from hands: the scanned bundle is exec-free, and a zero-dependency helper owns tmux. The two meet in one shared table on disk.
- The split is CI-enforced on every build, which is what lets it install from ClawHub with no dangerous-install flag.
- The helper is one readable file. It acts only on operations the plugin wrote, listens on loopback behind an Origin gate, and runs as you, with the same authority as your own keyboard.
Pay per feature, not per backend.
The whole product is free: fleet, operator, search, doctor, audit, batch, and both surfaces. Paid features are additive, and the free path degrades gracefully instead of breaking.
- One ships today: Sentinel, fleet-health alerts when a session starts waiting or dies. Unlicensed, it simply no-ops.
- A feature key verifies offline, by signature, not by network. One key will cover every Torad plugin. Today there is one plugin.
Supported agents
Four harnesses, first-class on the wall.
Fleet controls tmux sessions and on-disk transcripts, not model APIs. Support varies by agent.
| Capability | Claude Code | Codex | Hermes | Gemini |
|---|---|---|---|---|
| Detect and bind | yes | yes | yes | yes |
| Drive into the pane | yes | yes | yes | yes |
| Live transcript mirror | yes | yes | yes | pane-tail |
| Tappable answer buttons | yes | yes | yes | pane-tail |
| Exact token / cost | exact | best-effort | best-effort | no |
| Spawn a new agent | yes | yes | yes | no |
On your billing: Fleet attaches to sessions you already started. No second API key, no token surcharge from us; each session bills on its own auth, as if you typed the prompt yourself.
Features
Five views, whole-fleet vitals, and one audited seam.
Fleet
Every session as a tile: provider, health, a live mini-terminal, velocity.
Operator
The most urgent session, pulled to a hero slot with controls at hand.
Search
Find any session across the fleet without cycling panes.
Doctor
Health states, orphans, and the same diagnosis the CLI prints.
Audit
Append-only and read-only: who, verb, target, outcome.
Whole-fleet vitals
Running, waiting, dead, and bound counts, plus a 0-to-100 health dial. There is no hard session cap.
One ordered batch
Multi-select acts run as one ordered, audited batch with per-session outcomes. Database verbs are transactional; tmux side-effects are not, so it reports "4 of 5 done".
Tags and favourites
Tags group the fleet. Favourites and layout persist server-side, across devices.
The one audited seam
Every web button, Telegram tap, or agent tool passes one seam that logs who, verb, target, and outcome. A respawned session is a new binding, so a stale command cannot fire into it. Spawning is allowlisted and name-validated, with no shell.
Sentinel
a paid feature
a paid feature
Push alerts the moment a session starts waiting or dies. The free path simply no-ops.
Trade-offs
Where Fleet fits, and where it does not.
The limits, in one place.
Not a fit if
Narrower than ductor, which reaches more chat networks, cron, and webhooks. Less private than raw ssh plus tmux, which is end-to-end yours.
Fleet earns its place when "attach and read" stops scaling: approvals queue up, sessions die quietly, and you stop noticing which pane asked first.
The one network boundary
With Telegram on, assistant-turn text is stored by Telegram, and bot chats are not end-to-end encrypted. It is your bot, your account, your group, your allowlist, and the only added egress is the Telegram Bot API. There is no Torad backend in the path.
Turn Telegram off and the web room adds no egress at all.
Two defaults worth flipping
Out of the box, defaults favor speed: inbound messages paste without confirmation, and agent write tools are on.
Set requireApproval to hold every inbound message behind an approve button, and set agentTools.allowWrites to false to make agent access read-only. Flip both anywhere you would not hand over your terminal.
Get access
Now in preview.
The control room works today. We onboard a few operators at a time, so every install gets real attention.
Watch it first
The recording lands here: phone approvals, urgency ranking, and one agent handing work to another.
See it runJoin the preview
Tell us what you run. Members get the room, plus early access to paid features as they land.
FAQ
Questions, answered.
I run one or two agents, not a fleet. Is it worth installing?
Yes. The first win is not fleet scale, it is the blocked approval that becomes a phone button. Ranking, batches, and the relay start paying once you run three or more.
I already cycle tmux windows by hand. What do I actually gain?
Reach and a record. Attention finds you instead of the reverse: tappable approvals, push when a session waits or dies, exact per-session cost, and an append-only ledger of who did what. It does not replace ssh.
Five open-source bots already do Telegram-topic-per-session. Why this one?
Three differences: it installs into the OpenClaw you already run, passes the install scanner clean with no dangerous flag, and charges per feature with an offline key rather than per backend.
Isn't a remote-control bot over my dev fleet a security risk?
Treat it as terminal authority, because it is. The scanned bundle cannot spawn processes, only allowlisted Telegram ids may drive, every mutation passes the audited seam, and two config flips put an approval gate in front of every inbound message.
What does it cost, and does it phone home?
The instrument is free. Paid features are additive and unlock with a key your machine verifies offline, so there is no metered backend to phone. Preview terms arrive with membership.
Is it generally available?
Not yet. Fleet is in limited preview. Request access above.
See every agent. Steer any one. Let them steer each other.
Torad Fleet · an OpenClaw plugin · part of Torad Labs