codex - 💡(How to fix) Fix Codex Desktop: Profile and Usage become unavailable until local UI state is cleared

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

Codex App 26.527.31326 (CFBundleVersion 3390) Bundled/linked CLI reports codex-cli 0.135.0-alpha.1

What subscription do you have?

Not included here.

What platform is your computer?

macOS 15.7.5, Apple Silicon / arm64

What issue are you seeing?

The Codex Desktop Settings pages for Profile and Usage can enter a persistent unavailable/error state even though the account, auth, network, and backend data are healthy.

Observed UI symptoms:

• Profile page shows Profile stats unavailable.
• Usage/Profile data disappears from the Codex Desktop UI.
• Restarting the app does not reliably fix it.
• Clearing Codex Desktop local UI state makes Profile/Usage visible again, but the issue can recur after the UI state is regenerated.

This looks isolated to Codex Desktop renderer/local UI state or its fetch bridge, not to account data or backend availability.

What steps can reproduce the bug?

I do not yet have a deterministic minimal trigger, but this sequence reproduced the failure/recovery cycle on the same machine:

1. Open Codex Desktop for macOS.
2. Go to Settings -> Profile / Usage.
3. Observe that Profile/Usage becomes unavailable; Profile shows Profile stats unavailable.
4. Verify locally that Codex itself is otherwise healthy:
   • codex doctor reports auth, state databases, websocket connectivity, and reachability as OK.
   • System proxy is disabled and no proxy environment variables are present.
5. Query the same backend profile endpoint with the local ChatGPT auth token from ~/.codex/auth.json using Codex-Desktop-like headers:
   • GET https://chatgpt.com/backend-api/wham/profiles/me
   • Response is 200 and includes profile, stats, daily_usage_buckets, weekly_usage_buckets, and lifetime_tokens.
6. Quit Codex Desktop completely.
7. Move local Codex Desktop UI state out of the way, for example:

backup="$HOME/Desktop/codex-ui-state-backup-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$backup"

for p in \
  "$HOME/Library/Application Support/Codex/Default/Local Storage" \
  "$HOME/Library/Application Support/Codex/Default/Session Storage" \
  "$HOME/Library/Application Support/Codex/Default/Network Persistent State" \
  "$HOME/Library/Application Support/Codex/Default/Preferences" \
  "$HOME/Library/Application Support/Codex/Local State"; do
  [ -e "$p" ] && mv "$p" "$backup/"
done

1. Reopen Codex Desktop.
2. Profile/Usage data appears again.
3. After using/reopening the app, the problem can recur once the local UI state is regenerated.

What is the expected behavior?

Settings -> Profile and Usage should display the user's profile and usage stats whenever the authenticated backend endpoint returns valid profile/stats data.

If a frontend query fails, the UI should expose a useful error/retry path instead of getting stuck in a persistent unavailable state that requires deleting local renderer state.

What is the actual behavior?

The UI shows Profile/Usage as unavailable even though:

• the same account is authenticated,
• backend profile stats are returned successfully by /backend-api/wham/profiles/me,
• codex doctor reports healthy auth/network/state,
• clearing Codex Desktop renderer state restores the page.

Diagnostic evidence

Version checks:

codex-cli 0.135.0-alpha.1
Codex.app CFBundleShortVersionString: 26.527.31326
Codex.app CFBundleVersion: 3390
macOS: 15.7.5
arch: arm64

codex doctor summary while the UI was unavailable:

16 ok · 1 idle · 1 notes · 0 warn · 1 fail

The only failure was terminal-related because the diagnostic was run from a non-interactive Codex tool environment:

TERM=dumb - colors and cursor control are disabled

Backend profile endpoint check while the UI was unavailable:

{
  "status": 200,
  "ok": true,
  "hasProfile": true,
  "hasStats": true,
  "dailyLen": 99,
  "weeklyLen": 20,
  "hasLifetimeTokens": true
}

Local state observation after recurrence:

• ~/Library/Application Support/Codex/Default/Local Storage/leveldb contained regenerated Statsig/usage/profile-related cached state.
• Clearing Default/Local Storage, Default/Session Storage, Default/Network Persistent State, Default/Preferences, and Local State restored Profile/Usage visibility.

Additional information

This appears to be a Codex Desktop UI/local-state problem rather than a user account, subscription, network, or backend data problem.

The workaround is to quit Codex Desktop and clear the UI state paths listed above. That workaround is disruptive and the issue can recur after the state is regenerated.

No auth tokens, account IDs, or personal identifiers are included in this report.