Reliable remote update and relaunch for iPad-to-Windows Codex workflow

Summary

Codex should reliably relaunch after an app update when the update is initiated from a remote Windows session. This matters for users who primarily operate Codex from an iPad connected to a Windows desktop.

Current behavior

I initiated a Codex app update from the console. The update completed, but Codex did not relaunch automatically even though the UI indicated it would relaunch after finishing. I had to manually restart the app.

Observed version change:

• Previous Windows package: OpenAI.Codex_26.611.8604.0
• Updated Windows package: OpenAI.Codex_26.616.9593.0
• Package status after manual restart: Ok

Desired behavior

1. Allow the update to be started from a remote Windows session, including when the user is connected from an iPad.
2. Reliably close, update, and relaunch Codex on Windows.
3. Restore the same workspace/thread after relaunch when possible.
4. If relaunch fails, show a persistent recovery action such as Relaunch Codex.
5. Clearly report whether the update succeeded, failed, or requires manual restart.
6. Avoid leaving the user in a state where the update has completed but Codex is closed or disconnected with no obvious recovery path.

Why this matters

For local desktop users, manually relaunching may be a minor interruption. For remote users, especially iPad-to-Windows workflows, a failed relaunch is more disruptive because the user may need to reconnect through a remote desktop workflow just to recover the active Codex session.

A more robust update flow would be effectively transactional:

• save active session state
• download and apply update
• verify installed version
• relaunch Codex
• reopen prior workspace/thread
• report success or provide a clear recovery action