Exact error
Match the message before using the fix
Error: account/read failed during TUI bootstrapaccount/read failed: email and plan type are required for chatgpt authentication (code -32600)account/read failed: duplicate workspace in routing discovery (code -32603)Quick answer
Start here
Read and save the complete nested message after `account/read failed`. If there is no workspace-routing error, `codex logout` followed by `codex login` fixed one reported authentication case. If the nested error says `duplicate workspace in routing discovery`, logout, login, and reinstall did not fix the current report, so stop cycling credentials and report the exact code and workspace context.
Diagnosis
Why it happens
- `account/read failed during TUI bootstrap` is an outer startup error; different account/read failures can appear behind it.
- One report recovered after refreshing authentication, while another reported missing email and plan data for ChatGPT authentication.
- The `duplicate workspace in routing discovery` report occurred after successful login and persisted after reinstalling, so that branch is not proven to be a local credential failure.
Safest first
Fixes, in order
Classify the nested account/read error
Applies when: Every occurrence of the outer TUI bootstrap error
The nested text and JSON-RPC code determine whether a login refresh is a reasonable test.
- Copy the full error line, including text after the second `account/read failed` and any numeric code.
- Run `codex --version` and `codex login status`.
- Record the operating system and whether the account is personal, team, or organization-managed.
- Do not paste tokens, cookies, email addresses, or organization identifiers into a public issue.
codex --version
codex login statusExpected: You can distinguish a generic/auth-data branch from the duplicate-workspace routing branch.
Refresh authentication once
Applies when: The nested message is absent or refers to ChatGPT authentication data, not duplicate workspace routing
A logout/login cycle fixed one upstream report, but it is a reported workaround rather than a universal repair.
- Run `codex logout`.
- Run `codex login` and complete the official browser flow.
- Confirm `codex login status` reports the intended authentication method.
- Start `codex` once and stop repeating the cycle if the same nested error returns.
codex logout
codex login
codex login statusExpected: Codex starts normally, or the unchanged nested error shows that authentication refresh is not sufficient.
Escalate the duplicate-workspace branch without destructive cleanup
Applies when: The nested error is `duplicate workspace in routing discovery (code -32603)`
The current report confirms successful authentication and no benefit from reinstalling or logging in again.
- Update to the current official Codex build and reproduce once.
- Capture the exact version, nested error, account type, and whether more than one workspace is visible to the account.
- Submit those redacted facts to the matching upstream issue or official feedback channel.
- Leave authentication files and organization membership unchanged while the routing issue is investigated.
Expected: You preserve account state and provide the upstream team with the information that separates routing from authentication.
Verification
Prove the fix worked
- Run `codex login status` and confirm the expected authentication method.
- Start Codex and verify the TUI reaches an interactive prompt.
- If it still fails, confirm the saved nested message and error code are unchanged before escalating.
Escalation
If it still fails
- Do not delete the whole `.codex` directory or manually edit cached credentials for this startup message.
- Do not describe a successful `codex login status` as proof that account/workspace discovery succeeded.
- For managed accounts, ask the workspace administrator to confirm membership separately; do not publish organization details.
Scope
Environment and version notes
- The logout/login recovery report used Codex CLI 0.120.0 on Linux.
- The missing email/plan report used CLI 0.135.0 on Windows 10.
- The duplicate-workspace report used 0.155.0-alpha.9.2 on Windows and remained open on September 23, 2026.
Evidence
Sources
Source labels describe the evidence available on the checked date. A closed issue is not automatically a shipped fix.