OpenRig
← All of OpenRig 0.6.11

ChangedOpenRig 0.6.11

Bringing a team back now stops and asks when an agent's earlier conversation might still be resumable, instead of starting it over. A community contribution.

Restore no longer starts a seat fresh when an earlier occupant left a resume token. If a seat wasn't running when the snapshot was taken, but an earlier session recorded a resume token, rig up --existing and rig launch stop that seat at awaiting-decision and start nothing, because the token doesn't prove that conversation can still resume. rig launch of such a seat now exits 1 where it used to start it fresh. The message names the command that starts it fresh on purpose. For a seat stopped when the snapshot was taken, restore does not resume an earlier recorded conversation; the offered --fresh command starts a new conversation, not that recorded one.

The status API for a rig, `GET /api/rigs/:id/status`, can call a running rig `blocked` because of one such seat: it folds the restore forecast into the rig's status, though no seat is halted. `rig status` and the TUI's rig list don't show it for a running rig, and the web UI's "Resolve & restore" still works.

Pull request
#1141
Contributed by
@haralez