When an agent's conversation is really gone, a restore now stops and asks instead of reporting a failure. A community contribution.
In a restore of a rig whose seats are in pods, a seat is rolled back as unresumable only when its runtime reports the conversation missing. When Claude, Codex or Pi reports that, the restore rolls the seat back to awaiting-decision and starts nothing, instead of reporting a failed launch and leaving the new pane behind. A rig where every seat ends this way reads partially_restored instead of failed; the exit code is 1 either way. A Claude that exits to its shell for another reason keeps 0.6.10's result: the restore reports the seat failed and keeps its pane, so you can read what happened. Restores of rigs without pods keep their earlier handling.
- Contributed by
- @duncanleung
- Release
- OpenRig 0.6.11 release notes