prodex
prodex manages multiple isolated Codex profiles and lets Codex CLI or Claude Code run on top of the same OpenAI account pool.
It is built for a simple setup:
- each account gets its own profile
- quota is checked before launch
- fresh work can move to another ready profile
- existing continuations stay on the profile that already owns them
Requirements
- An OpenAI account, plus at least one logged-in Prodex profile
- Codex CLI if you want to use
prodex - Claude Code (
claude) if you want to useprodex claude
If you install @christiandoxa/prodex from npm, the Codex runtime dependency is installed for you. Claude Code is still a separate CLI and should already be available on your PATH when you use prodex claude.
Install
Install from npm:
Or install from crates.io:
The npm package version is kept in lockstep with the published crate version.
Update
Check your installed version:
The current local version in this repo is 0.2.125:
If you want to switch from a Cargo-installed binary to npm:
Quick Setup
If your shared Codex home already contains a login:
Or create a profile through the normal login flow:
If you want to name the profile first:
Check the pool:
Run Codex CLI or Claude Code through Prodex:
prodex without a subcommand is shorthand for prodex run.
Important Commands
Profile And Login
Run With Codex CLI
|
Run With Claude Code
Export And Import Profiles
prodex profile export includes each exported profile's auth.json. By default it exports every configured profile and asks whether the bundle should be password-protected.
Quota, Status, And Debugging
If a runtime session looks stalled, inspect the latest runtime log:
Notes
- Managed profiles share persisted Codex state through Prodex-owned shared storage.
prodex quota --allrefreshes live by default. Use--oncefor a one-shot snapshot.
More
For a longer walkthrough, see QUICKSTART.md.