prodex 0.2.115

OpenAI profile pooling and safe auto-rotate for Codex CLI and Claude Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156

# prodex

[![CI](https://github.com/christiandoxa/prodex/actions/workflows/ci.yml/badge.svg)](https://github.com/christiandoxa/prodex/actions/workflows/ci.yml)

One OpenAI profile pool for Codex CLI and Claude Code.

`prodex` gives you two entry points backed by the same OpenAI account pool:

| Use case | Command |
| --- | --- |
| Run Codex CLI through Prodex | `prodex` or `prodex run` |
| Run Claude Code through Prodex | `prodex claude` |

It keeps each profile isolated, checks quota before launch, and rotates to another ready account before a request or stream is committed.

Use `prodex` when Codex CLI is your front end. Use `prodex claude` when Claude Code is your front end. The account pool, profile isolation, quota checks, and continuation routing stay in Prodex either way.
Managed profiles also share persisted Codex state such as prompt history and session resumes, so cross-profile CLI state stays aligned.

## 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 use `prodex 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:

```bash
npm install -g @christiandoxa/prodex
```

Or install from [crates.io](https://crates.io/crates/prodex):

```bash
cargo install prodex
```

The npm package version is kept in lockstep with the published crate version.

## Update

Check your installed version:

```bash
prodex --version
```

The current local version in this repo is `0.2.115`:

```bash
npm install -g @christiandoxa/prodex@0.2.115
cargo install prodex --force --version 0.2.115
```

If you want to switch from a Cargo-installed binary to npm:

```bash
cargo uninstall prodex
npm install -g @christiandoxa/prodex
```

## Start

Import your current login:

```bash
prodex profile import-current main
```

Or create a profile through the normal Codex login flow:

```bash
prodex login
prodex login --device-auth
```

Check the pool:

```bash
prodex profile list
prodex profile export
prodex quota --all
prodex info
```

Move profiles to another machine or backup the current pool:

```bash
prodex profile export
prodex profile export backup.json
prodex profile import backup.json
```

`prodex profile export` includes each selected profile's `auth.json`. By default it exports every configured profile and asks whether the bundle should be password-protected.

## Use `prodex` for Codex CLI

`prodex` without a subcommand is shorthand for `prodex run`.

```bash
prodex
prodex run --profile second
prodex run 019c9e3d-45a0-7ad0-a6ee-b194ac2d44f9
printf 'context from stdin' | prodex run exec "summarize this"
```

Use this path when you want Codex CLI itself to be the front end. Prodex handles profile selection, quota preflight, continuation affinity, and safe pre-commit rotation across your OpenAI-backed profiles.

## Use `prodex claude` for Claude Code

```bash
prodex claude -- -p "summarize this repo"
prodex claude --profile second -- -p --output-format json "show the latest diff"
```

Use this path when you want Claude Code to be the front end while Prodex still routes requests through the same OpenAI-backed profile pool.

- `prodex claude` runs Claude Code through a local Anthropic-compatible proxy
- Claude Code state is isolated per profile in `CLAUDE_CONFIG_DIR`
- the initial Claude model follows the shared Codex `config.toml` model when available
- Claude's native `opus`, `sonnet`, and `haiku` picker entries are pinned to representative GPT models
- Prodex also seeds Claude's picker with the full Prodex GPT catalog
- Claude `max` effort maps to OpenAI `xhigh` when the selected GPT model supports it
- alias-backed GPT entries reuse Claude's native alias picker values so the picker and confirmation text stay aligned
- additional GPT entries stay on GPT model ids so the selected model banner keeps GPT naming while Claude can still expose effort controls
- use `PRODEX_CLAUDE_BIN` if `claude` is not on `PATH`
- use `PRODEX_CLAUDE_MODEL` to force a specific upstream Responses model
- use `PRODEX_CLAUDE_REASONING_EFFORT` to force the upstream reasoning tier

Example:

```bash
PRODEX_CLAUDE_MODEL=gpt-5.2 PRODEX_CLAUDE_REASONING_EFFORT=xhigh prodex claude -- -p "hello"
```

## Common Commands

```bash
prodex profile list
prodex profile export
prodex profile import backup.json
prodex use --profile main
prodex current
prodex quota --all
prodex quota --all --once
prodex info
prodex doctor
prodex doctor --runtime
```

## More

For a slightly longer walkthrough, see [QUICKSTART.md](./QUICKSTART.md).