CodexControl tracks real quota windows and switches local Codex accounts

I built CodexControl after using multiple Codex accounts and realizing that “switch the auth file” is not enough for a reliable desktop workflow.

The app is local-first and focuses on two jobs:

• showing live quota state for each account

• switching the active local Codex account without mixing desktop-session state

It keeps the 5-hour and 7-day usage windows separate, shows exact reset times, and avoids presenting stale values as current data.

The account-switching side became more complicated than expected. A desktop account can be represented by authentication data, provider/account identifiers, and cached application-session state. Updating only one surface can leave the UI and the active credentials disagreeing.

The macOS version is a native menu-bar app. The Windows version is tray-first. Both are designed to keep credentials local and use the existing Codex state rather than sending account data to another service.

Open source: https://github.com/ademisler/cod...

For people who actively use Codex: would you prefer each quota window shown separately, or one simplified “safe to use” indicator? And should account switching preserve each desktop session exactly or start clean?