What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.527.31326 (3390)
What subscription do you have?
Not relevant to the window/session restore behavior.
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
Closing, restarting, or updating Codex Desktop does not restore the windows I previously had open.
This is related to, but broader than, #26578. That issue describes the Windows app losing the maximized window state after an update relaunch. In this case, the problem is not just that the restored window bounds/state are wrong; the previously open Codex windows do not appear to be restored at all.
This makes updating Codex much more disruptive than it needs to be. Before closing/restarting/updating, I need to manually write down which Codex windows I have open, what they relate to, and which macOS desktop space each window is on. After the update, I then need to manually recreate that working set.
Because of that, I avoid restarting/updating Codex immediately, even when updates are available, because the cost of reconstructing my workspace is high.
What steps can reproduce the bug?
- Open multiple Codex Desktop windows.
- Place those windows across one or more macOS desktop spaces.
- Close, restart, or update Codex Desktop.
- Reopen Codex Desktop after the restart/update completes.
- Observe whether the previously open windows are restored to those correct desktop spaces.
Observed result:
- Codex does not restore the previous set of open windows.
- Window-to-desktop-space placement is not restored.
- I need to manually track and recreate my previous workspace.
- This makes updates/restarts feel risky/disruptive, because the app does not preserve my working context.
What is the expected behavior?
Codex Desktop should restore the previous window/session state after a normal restart or update.
At minimum, it should restore:
This should probably be configurable, since not everyone will want automatic session/window restoration. A setting such as “Restore windows from previous session” would allow users to choose whether Codex reopens the prior workspace after restart/update, similar to how many desktop apps and browsers handle session restore. For users who enable it, the update/relaunch flow should preserve the working set so applying updates does not require manually documenting and reconstructing the workspace.
Additional information
I mentioned this here as well:
The practical impact is that I cannot quickly apply new Codex Desktop updates without first doing manual bookkeeping of my current windows/spaces, then manually recreating that setup afterwards.
See Also
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.527.31326 (3390)
What subscription do you have?
Not relevant to the window/session restore behavior.
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
Closing, restarting, or updating Codex Desktop does not restore the windows I previously had open.
This is related to, but broader than, #26578. That issue describes the Windows app losing the maximized window state after an update relaunch. In this case, the problem is not just that the restored window bounds/state are wrong; the previously open Codex windows do not appear to be restored at all.
This makes updating Codex much more disruptive than it needs to be. Before closing/restarting/updating, I need to manually write down which Codex windows I have open, what they relate to, and which macOS desktop space each window is on. After the update, I then need to manually recreate that working set.
Because of that, I avoid restarting/updating Codex immediately, even when updates are available, because the cost of reconstructing my workspace is high.
What steps can reproduce the bug?
Observed result:
What is the expected behavior?
Codex Desktop should restore the previous window/session state after a normal restart or update.
At minimum, it should restore:
This should probably be configurable, since not everyone will want automatic session/window restoration. A setting such as “Restore windows from previous session” would allow users to choose whether Codex reopens the prior workspace after restart/update, similar to how many desktop apps and browsers handle session restore. For users who enable it, the update/relaunch flow should preserve the working set so applying updates does not require manually documenting and reconstructing the workspace.
Additional information
I mentioned this here as well:
The practical impact is that I cannot quickly apply new Codex Desktop updates without first doing manual bookkeeping of my current windows/spaces, then manually recreating that setup afterwards.
See Also