On Linux, a Codex agent can be restarted in its own pane on the same conversation, for example after its account's limit resets.
Restart a Codex seat in place, on Linux. rig seat restart <seat> --keep-conversation --reason "<why>" restarts one Codex seat in its own pane on the same conversation, so it starts again on whatever account its Codex home now holds. It doesn't switch accounts itself. Before it stops anything, it checks that the seat is a Codex seat OpenRig launched, in a single pane, with a conversation it can prove, and that relaunching wouldn't change the running settings; any doubt refuses with nothing stopped. --plan runs every check and stops nothing. --verify --expect-account <account> reports moved only when a tool turn has completed in the same conversation since the restart and Codex's status names that account.
Linux only: on macOS, a request that gets as far as reading the running process refuses before stopping the seat. It has restarted one real Codex seat (Codex 0.153.4), doesn't verify which account the seat resumes on, and wasn't tried with Codex builds that share one app server.
rig seat restart <seat> --keep-conversation --plan- Release
- OpenRig 0.6.11 release notes