Repository navigation
v0.1.4
Codex seats can be staged, a seat can choose how it starts, and a resumed seat whose fleet session ended now rejoins.
What changed
- A resumed seat whose fleet session ended joins again (#22, PR #24). The old first prompt told a restaged seat it had already joined, which left it holding only
joinwith no instruction to use it. A resumed seat now heartbeats ifpresence_heartbeatis offered (and moves its session if its work location differs); if onlyjoinis offered, it joins with its declared role, repository, work location and capacity. No prompt tells a seat toleave. - Each seat can start on its own or wait for its operator (#25, PR #27). A per-seat
startoverrides the machine's setting. seat-stagestages a seat whose harness iscodex(#26, PR #28). The seats file acceptsharness = "codex",seat-stage checkchecks a Codex seat against Codex, andstagelaunchescodex "<prompt>"and resumes withcodex resume <id> "<prompt>".- Codex docs corrected after measurement (PR #29): the README's Codex row and
docs/restart.md("Codex seats").
Codex: what was measured and what was not
Run live on macOS (arm64) with codex-cli 0.163.0: staging a Codex seat, the first prompt at launch, and codex resume.
- A Codex seat is not woken by the fleet; it waits for its operator to prompt it.
- Its bridge must carry
--auto-joinwith the seat's role, repository and work location in its MCP args, or the session keeps onlyjoin.seat-stagedoes not write those args. - Not measured: reading Codex's usage, a remote-control equivalent, and Windows.
Upgrading
composer global update robot-council/fleet-kit, or see Updating. Nothing in an existing seats file needs to change.