Prodex

prodex

prodex is a multi-account, multi-provider Codex wrapper with quota-aware profile routing.

Manage multiple Codex accounts, rotate eligible profiles as quota runs out, and use supported providers through the same front end.

Contents

- Why prodex
- Requirements
- Supported providers
- Installation
- Optional tools
- Quick start
- Daily command: prodex s
- OpenAI profile diagnostic
- Commands
- Modes
- Sub-agents
- Harness modes
- Profiles
- Local model support
- Utilities and diagnostics
- Advanced behavior
- Documentation
- Support

Why prodex

Use prodex if you want to:

- use multiple Codex accounts from one CLI
- rotate to another eligible account when quota runs out
- launch Codex/Super against non-OpenAI providers without changing front ends
- keep profile auth.json account credentials separated
- keep sessions attached to the profile that created them
- run Codex and Super mode through the supported wrapper

If you only use one Codex account and do not need quota rotation, you probably do not need prodex.

Requirements

For OpenAI/Codex quota-aware routing, you need at least one logged-in Prodex profile. Local --url launches and some provider API-key launches can run without a persisted profile.

Tool requirements

Supported providers

Prodex supports two provider paths:

- Profile-backed routing: persisted profiles that Prodex can select, rotate, and inspect where provider APIs allow it.
- Runtime provider launch: prodex s gemini, prodex s deepseek, or prodex s --provider ... starts Codex with a temporary provider bridge for that session.

Supported provider matrix

prodex gateway exposes the provider bridge as a standalone OpenAI-compatible service for non-Codex clients:

Gateway quickstart

Gateway capabilities (advanced)

The gateway serves…