Skip to main content
Codex plans aren’t on sale right now and can’t be bought or renewed for the time being. Codex organizations already activated keep working as usual until they expire, independent of your Claude subscriptions; for the scope of support, see Subscription → Codex plans.

What is recodex

Starting with client v1.5.0, the same ReClaude client ships an extra command, recodex (short alias recx), which runs the official Codex CLI with your ReClaude-assigned account; from v1.7.1 it can also open the ChatGPT desktop app (recodex app).
  • recodex sits side by side with reclaude: each has its own login, its own organization bindings, and its own logout, and neither affects the other; Codex organizations and Claude organizations are two separate sets.
  • Both commands share the same background service (daemon).
  • recx is to recodex what rec is to reclaude: recx login is the same as recodex login.

Install

New machine: use the one-line installer from Install the CLI. It gives you four commands at once: reclaude, rec, recodex, and recx. Already installed an older version: once the client is on v1.5.0 or newer, recodex / recx become available automatically (the new version creates them for you). If they don’t show up, run reclaude setup once. Staying on the latest version is recommended: the ChatGPT desktop app needs v1.7.1 or later, and recodex org bind, recodex logout --all and recodex service stop need v1.7.3 or later.
Open a new terminal, then verify with recodex version. No separate Codex CLI install needed: if this machine has no suitable Codex CLI, recodex downloads the official release automatically (no VPN needed). If you already have the official Codex CLI and it’s new enough, recodex uses yours. See Where the Codex CLI comes from below.

Log in

The terminal prints an authorization URL and tries to open your browser. In the browser:
  1. If you aren’t signed in, sign in with your ReClaude email and password first.
  2. Check that the page title reads Authorize recodex sign-in, and review the device details.
  3. Give this device a memorable name — it’ll show up under Codex devices on the Devices page.
  4. If you belong to multiple Codex organizations, pick one from the organization drop-down; after login this computer has its first binding, to that organization — add the other Codex organizations later with recodex org bind.
  5. Click Approve.
If you run plain recodex and this machine has no valid Codex login yet, it starts the same login flow automatically.
  • Independent of your Claude login: recodex login doesn’t change any Claude-side binding or config, and an existing reclaude login keeps working.
  • Don’t run codex login inside Codex: credentials are managed by ReClaude, and recodex rejects that command (codex login status works).

Use

  • Codex uses its own ReClaude-managed configuration; settings and plugins in your own ~/.codex are not carried over. Within one binding, the Codex CLI and the ChatGPT desktop app share configuration and session history.
  • recodex update upgrades the ReClaude client itself (same as reclaude update), not the Codex CLI.

Where the Codex CLI comes from

recodex prefers the official Codex CLI you installed yourself on your PATH. If there isn’t one, or it’s older than the minimum version ReClaude requires (currently 0.160.0), recodex uses the official Codex CLI managed by ReClaude instead (downloaded automatically to ~/.rec/codex/cli/<version>/). If your copy is too old you see “recodex: the local codex … is below the required …; using the managed … this time”, and your copy is left untouched.

ChatGPT desktop app

recodex app launches the ChatGPT desktop app with your current Codex binding, downloading the ReClaude-managed installer automatically on first run; recodex app --org <org_id> picks the organization. Codex inside the desktop app is fully usable; the Chat / Work modes work but with limited features. macOS and Windows only.
  • The chatgpt.com website, the mobile app and the VS Code extension are not supported.
  • recodex app update updates the managed desktop installer; recodex app reset resets the desktop app’s login state and cache (configuration and session history are kept; it asks for confirmation first — add --yes in a non-interactive terminal).

Multi-organization binding and switching

Codex organizations are managed separately from Claude organizations: recodex org only lists and binds Codex organizations, and reclaude org only handles Claude organizations. Usage is the same as on the Claude side (see Command reference → Multi-organization binding): one computer can hold a binding to each of several Codex organizations, and launching without --org uses the Codex-side default binding.
  • You can only bind and switch to Codex organizations you’re a member of.
  • If this machine has several Codex bindings and no default, recodex lists the organizations to choose from and exits; set a default with recodex org use <org_id>.
  • recodex org use only affects the Codex CLI and desktop app you launch afterwards — ones already open are unaffected; it doesn’t change any Claude-side binding.

Common commands

recodex uninstall is exactly the same as reclaude uninstall: it removes the program and the background service and keeps both platforms’ local data by default; only with --purge does it wipe all ReClaude-managed data and history, including each Claude-side organization binding’s Claude Code config, sessions, memory and Claude Desktop data (your own ~/.claude is left alone; wiped data can’t be recovered). To stop using Codex only, recodex logout is enough.

FAQ

“no active subscription, or it has expired; visit reclaude.ai to purchase / renew”, or the approval page says “Codex plans are not available for purchase right now.” You don’t have a Codex plan yet, or the Codex organization this device points to has expired. Codex plans aren’t on sale right now and can’t be bought or renewed for the time being (a Claude plan can’t be used for Codex). If you’re still in another active Codex organization, recodex lists the ones you can switch to — run recodex org use <org_id> as prompted. “recodex: the local codex … is below the required …; using the managed … this time” The Codex CLI you installed yourself is older than the minimum version ReClaude requires, so recodex uses the managed official version for this run, and everything works as usual; to keep using your own copy, upgrade it to the required version or later. Codex logs show a WebSocket failure / 426, then switch to HTTP Starting with v1.5.0, Codex’s WebSocket connections pass straight through ReClaude by default. In the occasional case where the route temporarily doesn’t carry WebSocket, Codex gets a 426 and automatically continues over HTTP streaming — the conversation isn’t affected. When the route falls back, launching recodex first prints codex_transport: fallback (WebSocket falls back to HTTP; Codex CLI works normally) in the terminal; nothing is printed when WebSocket goes straight through. How many devices can I use with Codex? 4 devices per Codex account: all members on the same account share at most 4 active devices in total, and one person can use them all — the same rule as Dedicated Max / Ultra. Codex devices are counted separately from Claude devices; view and revoke them under Codex devices on the Devices page, and see Devices → Device limit for the rules. Can I see Codex usage and message history on the website? Yes. After you Switch organization to a Codex organization at the top of the web dashboard, the home page shows that account’s usage, and Sync usage refreshes it; in message history, records from both platforms are listed together, each labeled with its platform. Codex requests don’t show cost statistics. Can I use the ChatGPT desktop app? Yes — run recodex app, see ChatGPT desktop app above. The chatgpt.com website, the mobile app and the VS Code extension aren’t supported.
Last modified on November 10, 2026