Accounts Pool

Accounts Pool (Pro) turns selected saved Codex accounts into one local, OpenAI-compatible API. It runs on your machine as a loopback endpoint — not a hosted proxy — so another app can reach all of those accounts through a single base URL and key.

Set up the pool

1. Open Connect → Account Pool, or run codexuse account-pool status.
2. Select the profiles you want it to use.
3. Choose how new requests are routed.
4. Generate a local API key for the runtime that will serve the client.

The current base URL appears in Settings, and the CLI can inspect the same setup. Keep the exact base URL and runtime key together when you connect a client.

Connect a local client

Accounts Pool serves any tool that already speaks OpenAI-compatible Responses or Chat Completions API shapes — scripts, editor extensions, local agent runners, and desktop apps that want one base URL, one key, and more total headroom than a single account provides.

curl http://127.0.0.1:PORT/v1/models \
  -H "Authorization: Bearer cux_pool_..."

curl http://127.0.0.1:PORT/v1/responses \
  -H "Authorization: Bearer cux_pool_..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.5",
    "input": "Summarize what changed in this repository."
  }'

curl http://127.0.0.1:PORT/v1/chat/completions \
  -H "Authorization: Bearer cux_pool_..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.5",
    "messages": [{"role": "user", "content": "Summarize what changed in this repository."}]
  }'

Manage it from the CLI Pro

You can manage the same Accounts Pool settings from the terminal without opening the desktop app.

codexuse account-pool status
codexuse account-pool profiles list
codexuse account-pool keys create
codexuse account-pool keys create --runtime=desktop
codexuse account-pool sessions list

Choose the model names your client will see

You choose which model IDs the pool exposes. If you want simpler setup on the other side, CodexUse can also publish aliases that keep a preferred reasoning level behind one easier public name.

How routing works

A new pooled session can start on any eligible selected profile, which spreads fresh work across your accounts instead of draining one first. Once a session starts, CodexUse keeps it on that account unless a rollover is needed.

• Least used: prefer the eligible profile with the most headroom right now.
• Round robin: spread new sessions evenly across the selected pool.
• Session continuity: once a pooled session exists, later turns stay with it unless a rollover is needed.

What happens when one account runs out

If a selected account hits quota, a rate limit, an auth problem, or a runtime failure, Accounts Pool moves that logical session to another eligible profile and continues there. That is the point of pooling: more shared headroom, smoother load distribution, and fewer hard stops for the client.

What this will not fix

Accounts Pool helps when you truly have multiple eligible accounts to route across. If two saved profiles are really the same underlying OpenAI account, they still share the same headroom. The pool can organize that setup, but it cannot invent extra quota.

Good fits