Fleet docs v0.2.0-rc.448

How to reach the chief

The chief is one live conversation, named chief, of kind chief. It runs in the chief-of-staff repo on the one node that has that repo, and it is pinned there. It loads your Claude home (your memory, skills and settings, from fleet home) and has full permission, as a worker does.

Talk to it

  • On the page or the phone: open /chat. The Chief channel is at the top of the list; the conversation in it is the chief. Type a message. Its answer streams in as it is written.
  • From a terminal: fleet send chief "<text>". Read the answer on the page.
  • From the Claude app or ChatGPT: the control MCP's send and turn tools, as for any agent.

A message sent while it works is queued and reaches it in the same turn.

What it does

  • Small jobs it does itself, end to end. For bigger ones it starts workers with fleet spawn; they show under its "workers" button.
  • It posts rulings, heads-ups and blockers on its channel's board (fleet board post).
  • It tells you on Telegram when something needs you, with the helper its brief names.
  • It never finishes. Ask it to stop with fleet stop chief; a new message brings it back.

It keeps its memory

  • A quiet chief exits after 1 hour. The next message starts it again in about a second, and it resumes from its stored conversation.
  • A restart of its node keeps the running process; the next node process adopts it.

The proving run

Remote Control is retired once the fleet chief has handled 50 of your requests with no message lost. The chief's header on the page shows the count, for example 12 of 50 requests, 0 lost. GET /v1/conversations/chief/proving gives the same count.

  • A request is a message from a person to the chief. Messages from agents, from the board and from fleet itself are not counted.
  • Lost: a request that no turn took: the chief ended before it read it, or it waited more than 30 minutes.
  • Duplicated: the same text from the same person again within 60 seconds (a client that sent twice). It is shown, and it holds the run open like a lost one.

When the 50th request arrives with none lost or duplicated, fleet leaves the chief one note. The chief then tells you and proposes disabling the claude-rc@ units: systemctl disable --now, keeping the unit files, which are erased later. Fleet disables nothing itself. You decide.

Start it

One chief, made once:

fleet spawn chief --kind chief --node <node with the repo> --workdir <the repo> --brief <brief file>

A chief that a person spawns joins the Chief channel (made on first use). Its node must take kind chief (kinds: in the node's config).