Why
Some users may have more than one Codex/OpenAI account or separate Codex homes. CodexBar supports account selection, and a smaller version of that could make Usage Radar more useful without forcing users to swap files or environment variables manually.
This should be handled carefully because account management can easily turn into a large settings surface.
What I want
Explore a compact account model for Codex.
Possible shape:
- detect the current system Codex account from the normal Codex auth path
- optionally allow additional named Codex homes/accounts
- let the user choose which account Usage Radar displays
- keep each account's usage/cache state clearly separated
- make it obvious which account the popup is showing
Done when
- there is a small proposed config shape for multiple Codex accounts
- switching accounts does not mix cached usage snapshots between accounts
- the UI shows the selected account label in a compact way
- missing or expired auth is shown per account
- raw tokens are never copied into app cache or logs
Notes
This is not meant to become full account administration. The goal is only to make Usage Radar usable for people who already work with multiple Codex accounts or Codex homes.
Why
Some users may have more than one Codex/OpenAI account or separate Codex homes. CodexBar supports account selection, and a smaller version of that could make Usage Radar more useful without forcing users to swap files or environment variables manually.
This should be handled carefully because account management can easily turn into a large settings surface.
What I want
Explore a compact account model for Codex.
Possible shape:
Done when
Notes
This is not meant to become full account administration. The goal is only to make Usage Radar usable for people who already work with multiple Codex accounts or Codex homes.