Windows app stuck in Work after switching from Codex; unable to switch back
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.911.7940.0
What subscription do you have?
Enterprise workspace account
What platform is your computer?
Windows 11 x64
What issue are you seeing?
Codex was working normally earlier in the day. I manually switched from Codex to Work, and after that I became stuck in the Work view.
Work shows that I do not have access. When I try to switch back to Codex, nothing happens and I remain in Work.
The issue persists after restarting the app, restarting Windows, repairing the app, resetting the app, and reinstalling it.
In-app Feedback also previously showed: “Couldn't verify feedback permissions. Please try again.”
codex://settings opens the generic settings page, but codex://new does not return me to Codex.
What steps can reproduce the bug?
Submitted performance trace: no-active-thread-01a0b030-c54a-7960-9445-8fa93f69707b
What is the expected behavior?
After switching to Work, I should still be able to switch back to Codex normally, even if I do not have Work access.
If Work access is unavailable, the app should either prevent entering Work or provide a working way to return to Codex.
Additional information
Codex was working normally immediately before I switched to Work, so the issue started only after entering the Work view.
I am using a managed workspace account.
I have already tried restarting the app, restarting Windows, Repair, Reset, reinstalling the app, codex://new, and codex://settings.
I would prefer to avoid signing out because signing back in requires additional phone verification.
The performance trace has already been uploaded using the in-app trace reporting flow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows 11 flow with a managed workspace account: switch from Codex to Work without Work access, then try returning with the normal switcher and codex://new. Review the submitted performance trace no-active-thread-01a0b030-c54a-7960-9445-8fa93f69707b and compare the behavior with codex://settings. Done means unavailable Work cannot trap the app, and returning to Codex works normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100