Plan with your best model. Build with the right model.

Work runs one task across your accounts. You describe the work, pick a folder and separate planner and worker accounts. The planner plans in its own Codex window. The worker builds in an isolated Git worktree and receives a bounded brief, not the planner's transcript. You review the result and accept it into your working folder without committing or pushing it. Codex already supports subagents in the app, CLI, and IDE. Work adds account selection, separate windows, worker worktrees, and a review step. The codex agents CLI command browses sessions.

The one you pick. CodexUse shows each account's headroom and status so you can plan on the account with the most room and build on the one you allow for that project, including a custom-model account when its route supports coding tools. CodexUse never picks a planner by price or model name.

Yes, on Apple Silicon macOS. Every OpenAI account and every custom-model account gets its own Codex window. Open starts that window; Show brings a running one to the front. CodexUse never opens a second window for the same account, and it never signs another account out to do it.

CodexUse is for accounts you already hold: your personal login, an employer seat, separate client or contractor accounts. It signs in with the same OAuth flow the Codex CLI uses, keeps each account in its own window and Codex home, and never shares one subscription between people. It does not create accounts, bypass billing, or forge identities. Check your own plan terms before pooling quota for automated workloads.

It answers Codex tasks from your own ChatGPT session instead of from the Codex models. The CodexUse Chrome Companion runs in the regular Chrome profile where you are already signed in and creates a background Temporary Chat for each task. CodexUse never exports or copies Chrome cookies. Turns draw on your Chat allowance, so they do not spend the Codex allowance of any OpenAI account, and no provider bills you. Setup requires Chrome 116 or newer with the companion enabled, one signed-in OpenAI account in CodexUse, an OpenAI Tunnel with a secret API key that has Tunnels Read and Use, a connector named exactly CodexUse created in ChatGPT Developer Mode, and macOS 13 or newer on Apple Silicon. CodexUse refreshes its bundled companion in one stable local folder, opens Chrome Extensions, reveals that folder, and copies its path for the one-time Load unpacked step. ChatGPT reports no remaining Chat allowance for this route, so these accounts stay out of percentage-based auto-roll and Account Pool.

Decide that yourself, against your own agreement. Here is exactly what happens: the CodexUse Chrome Companion reads the ChatGPT page in the background tabs it creates, types each turn, and sends it. This is not an official OpenAI integration, and automating ChatGPT may not be permitted under your agreement with OpenAI. The connection form states this, and starting setup acknowledges it without another checkbox or page. There is no mode that only watches. CodexUse uses the ChatGPT account you already hold, never creates accounts, and never shares one subscription between people. Browser turns run in Temporary Chat, which OpenAI says it may retain for up to 30 days for safety purposes; workspace and account controls still apply.

Yes. A custom-model account can point at any provider that exposes an OpenAI-compatible Responses or Chat Completions endpoint: OpenRouter, DeepSeek, Groq, or a model running on your own Mac. CodexUse runs a local gateway on 127.0.0.1 that presents the Responses API to Codex and translates to the provider's shape. That account spends no OpenAI quota, keeps its credential encrypted in CodexUse's private app database, and shows only its own models in the picker. Dictation and browser control call ChatGPT's backend, so they are unavailable on it.

Sometimes, and not automatically. You are trading a flat subscription for metered billing, so heavy use of a frontier model often costs more than the plan does. It usually wins when a cheaper model is good enough for most of your work, or when you already pay a provider and want the Codex app as the interface. Measure your own volume before deciding.

Free tools swap ~/.codex/auth.json for the Codex CLI. CodexUse gives every account its own Codex window, runs planner and worker jobs across accounts with review before anything merges, keeps a History of every local task, adds custom-model accounts, headroom and refill timers, auto-roll, Telegram, Account Pool, and encrypted Cloud Sync. If you only need CLI account switching, a free tool is a reasonable choice.

Not for OpenAI. CodexUse uses the same OAuth login as the Codex CLI, so you sign in with the account you already have. Two exceptions: a custom-model account needs that provider's own credential, which is encrypted in CodexUse's private app database and never written into config files; and Account Pool mints a separate local key for the app you point at it.

Account Pool turns selected saved Codex accounts into one local API for another OpenAI-compatible app. That app gets one base URL and one key, while CodexUse shares quota across the selected accounts, load-balances new requests, and fails over when one account hits limits or runtime trouble. It runs on your machine and is not a hosted service.

Set a percent-left threshold, rank the eligible accounts if you want a specific order, and CodexUse rolls new work to the next account when the active one drops to that level. A rejoin threshold brings an account back once it refills, and a confirm countdown cancels stale decisions before they fire. Available during the trial and unlocked with Pro.

Current public desktop releases target macOS on Apple Silicon. Intel Mac, Windows, and Linux desktop builds are not shipped. For terminal workflows on another machine, install the optional codexuse CLI with npm.

The same app. Pro is a one-time lifetime license for up to 5 Macs, with free updates and no subscription. It keeps every feature unlocked after the trial. If you buy on the website, enter the license key from your Gumroad receipt in CodexUse. App-initiated checkout watches for payment confirmation; manual key activation remains available. There is a 30-day refund window.