Codex Desktop: Computer Use is lost after restart and archived threads trigger restore error

What version of the Codex App are you using (From “About Codex” dialog)?

26.601.21317 (build 3511)

What subscription do you have?

Not specified

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

I am seeing two Codex Desktop issues that started recently. They may be separate, but both look like local state / startup persistence problems.

1. Computer Use install state does not persist

• Computer Use can be installed manually from the Codex plugin UI.
• It appears available immediately after installation.
• After restarting Codex Desktop or rebooting the computer, Codex behaves as if Computer Use needs to be installed again.
• I manually reinstalled Computer Use again before filing this issue.

1. Archiving a thread triggers a restore failure toast

• After archiving a thread, Codex shows a red toast similar to:

Restore conversation failed: session [redacted] is archived. Run codex unarchive [redacted] to unarchive it first.

• The thread appears to be archived successfully, but Codex still tries to restore/open it afterward.

I am intentionally redacting session IDs and omitting local paths, user names, account details, private project names, and configuration contents.

What steps can reproduce the bug?

For Computer Use:

1. Open Codex Desktop.
2. Install Computer Use from the plugin UI.
3. Verify that Computer Use is available / usable immediately after installation.
4. Quit and restart Codex Desktop, or reboot the computer.
5. Open Codex Desktop again.
6. Observe that Computer Use appears missing or requires installation again.

For the archive toast:

1. Open any thread in Codex Desktop.
2. Archive the thread from the UI.
3. Observe a red toast saying Codex failed to restore the same session because it is archived.

No code snippet is involved; this is a desktop app state / UI persistence issue. I am not including session IDs, token usage, context window usage, or screenshots because they may contain private identifiers.

What is the expected behavior?

• Installed and authorized Computer Use should remain available across Codex Desktop restarts and system reboots unless the user explicitly removes it.
• Archiving a thread should not immediately attempt to restore/open that archived thread.
• If an archived thread is still referenced by stale UI/session state, Codex should clear that reference or navigate to a non-archived thread instead of showing an error toast.

Additional information

Privacy note: I have not attached screenshots or raw local logs because they may contain account UI, session IDs, local paths, or other private identifiers. I can provide redacted logs or run a maintainer-suggested diagnostic command if there is a safe way to collect it.

Sanitized environment details:

• Codex Desktop: 26.601.21317 (build 3511)
• macOS: 26.5.1 (build 25F80)
• Platform output: Darwin 25.5.0 arm64 arm
• Mac model family: MacBook Pro
• Model identifier: Mac17,2
• Chip: Apple M5
• CPU cores: 10 (4 performance-class / 6 efficiency-class, as reported by macOS)
• Memory: 32 GB
• Computer Use currently works in this session after manual reinstall; the app state reports CUA App Version 799.

Sanitized observation log:

• After a previous restart, Codex Desktop showed Computer Use as needing installation again even though it had been installed before.
• After manually reinstalling Computer Use, it became usable again in the current session.
• Archiving a thread appears to complete successfully, but Codex immediately shows a restore failure toast for that archived thread.
• I tried clearing stale archived-thread restore state locally; that did not resolve the Computer Use persistence issue after restart.

No account names, emails, session IDs, local filesystem paths, private project names, or screenshots are included in this report.