Windows desktop app invalidates valid personal-account token after thread start/resume
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
App: 26.820.9563.0
Bundled Codex: 0.150.0-alpha.8
Login and account lookup succeed.
Both existing and newly created threads start/resume successfully.
Immediately afterward GET /backend-api/accounts/{account_id}/settings returns 401:
"Must use workspace account for this operation"
The app then changes auth state to auth_token_missing and displays the login screen.
Reinstall, app reset, fresh login, and global-state reset do not resolve it.
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
Reproduce the Windows flow using the listed app and bundled Codex versions, then trace the GET /backend-api/accounts/{account_id}/settings response and the transition to auth_token_missing after thread start or resume. Done means a valid personal-account token remains usable and the app does not return to the login screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100