Mike Schwarz
ef7dceab42
The Fleet page shows subscription move reports: for each daemon, the managing agent's dated reports from GET /api/provider/moves, with from and to, the reason and policy version, each seat's account evidence and tool turn with their times, what's missing, peers and follow-up links. A daemon without the route reads as unavailable, not as no reports; the recent window and unreadable rows are named. Configured and observed seat accounts stay separate, so a move is never shown as current use. The reader keeps sign-in, last exhaustion and reset expectations. The starter agent's manage-subscriptions practice applies only when enabled and names the exact Codex home and host. Slice 18's Fleet side; not part of the curated default install.
Fleet Studio launch rig
A starter operations agent for an OpenRig machine, with the fleet know-how it carries:
- recovering a stranded seat (a usage limit, a lost login, a restart)
- reading subscription usage honestly
- keeping agents' context healthy
- managing subscriptions when the person enables that job
The know-how is four context packs in context/fleet-ops/. At startup the agent adds any that are
missing to the machine's context library, so every agent on the machine can find them with
rig context list and read them with rig context get fleet-ops/<name>. You can also add them
yourself, without the agent:
rig context add rigs/fleet-studio/context/fleet-ops/recover-a-stranded-seat
rig context add rigs/fleet-studio/context/fleet-ops/read-usage-honestly
rig context add rigs/fleet-studio/context/fleet-ops/keep-context-healthy
rig context add rigs/fleet-studio/context/fleet-ops/manage-subscriptions
Start it
From a checkout of this repository:
rig up rigs/fleet-studio/rig.yaml
The rig also runs the Fleet page in its own container (Compose project openrig-fleet-studio, port
9450): open http://127.0.0.1:9450/surfaces/fleet.html. It answers which accounts have room, which
machines report here, what the rigs are doing, and the managing agent’s dated subscription move reports, from what OpenRig's own daemons report. It is read
only, needs no other app, and never asks for a sign-in or reads a token. The Observatory (rigs/observatory/) is an optional,
separate launch rig; Fleet Studio does not need it. Both rigs use the same starter operations agent
(rigs/agents/starter-ops/), each with its own startup context.
What it touches
Its own rig and its own files. It reads the rest of the environment with OpenRig's commands and changes nothing outside its rig unless the person separately enables the subscription-management job; see the agent's role. Installing the bundle alone does not enable it.