Skip to content
Summer sale. 50% off Pro, $19.50 for life. Desktop app: Apple Silicon Mac only.SUMMER50
CodexUse

Accounts Pool: shared quota and load balancing for saved Codex accounts

Accounts PoolUpdated August 2026 · 6 min read

Accounts Pool turns selected saved Codex accounts into one local API, so another app gets shared quota, load balancing, and failover instead of drawing on one account at a time. It is available during the trial, and Pro keeps it after that.

Short version: connect an app once, give it one local API and one pool key, and CodexUse spreads work across your selected accounts instead of letting that app depend on a single one.

Why this matters

Without Accounts Pool, an app only had whatever headroom one account gave it. If that account neared quota or hit a runtime issue, the workflow stalled fast.

Accounts Pool fixes that. The app gets one local API and one pool key, while CodexUse pools the selected accounts behind it so fresh work load-balances and blocked sessions roll over.

What shipped

  • One local OpenAI-compatible API for the saved accounts you select
  • Pool keys for the apps you connect to it
  • Shared quota across selected saved accounts
  • Load balancing for fresh requests across the pool
  • Published model names for downstream apps
  • Failover when an eligible account runs out or fails
  • CLI commands to manage the pool and desktop runtime keys

Where it fits

Use caseWhy Accounts Pool helps
Local agent runnerGive it more total headroom by pooling selected accounts behind one local API.
Sidecar editor extensionKeep the editor integration simple with one key, while CodexUse load-balances new work in the background.
Longer response workflowsWhen one account hits quota or a runtime issue, the pool can roll to another eligible account instead of dying immediately.

What it does not pretend to solve

  • It is not a public hosted proxy. The point is a local endpoint on your own machine.
  • It does not create extra quota from duplicate accounts. If two saved profiles are really the same underlying OpenAI account, they still share the same headroom.
  • It does not hide bad requests. Unsupported or malformed requests still fail instead of being silently retried somewhere else.

What you actually get

Save your Codex accounts in CodexUse once. Any OpenAI-compatible app on your machine then gets one API, one key, more shared quota, load balancing across selected accounts, and automatic rollover when one account gets blocked.

So Accounts Pool fits anywhere you already run an OpenAI-compatible app or script and want CodexUse as the pooled account layer behind it.

Getting started

  1. Open Connect → Account Pool in CodexUse.
  2. Enable the pool and choose the profiles you want available.
  3. Publish the model names you want the other app to see.
  4. Generate a local pool key.
  5. Point the other app at the base URL shown by CodexUse.

CLI path

If you want the same setup from a terminal, the CLI covers the operational side too:

codexuse account-pool status
codexuse account-pool status --runtime=desktop
codexuse account-pool keys create --runtime=desktop

The settings, keys, and pooled sessions belong to the desktop runtime. Use the base URL shown by the running desktop app.

Related

Accounts Pool docs Client setup guide Rate limits and 429s

Is Accounts Pool included in the trial?

Yes. Accounts Pool is available during the 7-day trial, and Pro keeps it unlocked after the trial.

Does it use my normal Codex login?

Yes. CodexUse still uses the same Codex CLI OAuth profiles you already saved locally.

Do downstream clients need my OpenAI credentials?

No. They use a local pool key generated by CodexUse, not your Codex account credentials.