[Bug]: Authentication switching issues on codex
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
Not sure
Steps to reproduce
1- authenticate to another account on codex.
2- in settings it displays that the account has been authenticated successfully
3- continue with chat and see that it is still running on old account since we get error that limits have been used up and the new accounts does not have issues
4- restart t3 and session is updated and new authenticated account works fine.
Expected behavior
Changing the authenticated account should automatically use the new authenticated account for new messages withought having to restart t3 for the new authenticated account to work.
Actual behavior
Unless you restart t3 the switched authenticated account does not take place and work when continuing chat threads that where on the old account.
Impact
Major degradation or frequent failure
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
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 account switch from Settings, then continue an existing chat without restarting t3 and compare it with the restarted session. Trace how the authenticated account is used for new messages and consider the behavior fixed when switching accounts immediately affects continued chats without a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100