Why
Codex is the most important first-class provider for Usage Radar. If the app cannot find Codex auth, the empty state should help me fix it quickly.
Right now the failure can be technically correct, but it could be friendlier and more specific.
What I want
Make the Codex not-connected or auth-missing state more helpful.
It should explain, in plain language:
- that Usage Radar reads Codex auth from
~/.codex/auth.json or CODEX_HOME/auth.json
- that the user may need to sign in to Codex first
- which path Usage Radar tried, if that is available
- what to do after signing in, such as refresh again
Done when
- missing auth has a clear Codex-specific message
- invalid auth or endpoint failure does not look the same as missing auth
- the popup gives one obvious next action, like refresh or open the relevant folder when possible
- no token contents or sensitive auth file contents are displayed
Notes
This should make first-run setup smoother without adding a full onboarding flow.
Why
Codex is the most important first-class provider for Usage Radar. If the app cannot find Codex auth, the empty state should help me fix it quickly.
Right now the failure can be technically correct, but it could be friendlier and more specific.
What I want
Make the Codex not-connected or auth-missing state more helpful.
It should explain, in plain language:
~/.codex/auth.jsonorCODEX_HOME/auth.jsonDone when
Notes
This should make first-run setup smoother without adding a full onboarding flow.