Account pooling. Running several sign-ins behind one gateway can conflict with the terms of the provider, so check what each provider allows before you pool accounts.
Credentials. OAuth sign-ins store tokens in the console's encrypted database, so keep the .env master key backed up and never share it.
Who it is forA person with Codex or Claude OAuth sign-ins who needs to know how much capacity each credential has left.
The problemQuota is spread across several sign-ins and windows, and checking each provider separately is slow.
The outcomeA per-credential view of quota readings and estimated window capacity, with refresh times set in OMC Settings.
What you need first
- Docker Engine with the Compose plugin and CLIProxyAPI v8.0.0 or later, or a native executable with CPA installed separately
- A Linux or macOS shell with curl and openssl for the Docker path
- A place to keep the .env file, since OMCPA_MASTER_KEY encrypts the database and cannot be recovered without it
Steps
- Install Oh My CPA from the Compose guide and sign in at
http://127.0.0.1:8080/omc/. - Open OAuth management and sign in for Codex or Claude from the console.
- Read the window capacity estimate and the previous cycle shown as a labelled reference for each credential.
- Adjust how often quota readings refresh in OMC Settings if the default six hours does not suit you.
Prompt for your agent
In the Oh My CPA console at http://127.0.0.1:8080/omc/, list each Codex and Claude OAuth credential with its estimated window capacity. Report the credentials that have less than half their window left. Verify each figure against the quota reading shown for that credential before you finish.
Caveat. The README calls window capacity an estimate, so treat it as guidance rather than an exact provider limit.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page