prodex 0.2.3

A multi-profile wrapper for Codex CLI with isolated CODEX_HOME state and quota checks
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

# Quick Start

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

```bash
cargo install prodex
```

## Use the Installed Binary

```bash
prodex
```

## Import your current `codex` login

If `~/.codex` already contains an active login:

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

## Or log in and let `prodex` create the profile

```bash
prodex login
```

`prodex login` creates a managed profile from the logged-in account email, reuses the same profile if that email is already known, and makes that profile active.

If the email-derived name is already taken by another account, `prodex` adds a numeric suffix instead of merging the two accounts into one profile.

If you want to log in to a specific profile name instead:

```bash
prodex profile add second
prodex login --profile second
```

Use `--profile` when you want a fixed profile name, or when the login flow is not the ChatGPT account flow that writes an email-bearing `id_token`.

## Check all profiles and quotas

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

## Select the active profile

```bash
prodex use main
prodex current
```

## Run `codex` through `prodex`

```bash
prodex run
```

Examples:

```bash
prodex run -- --version
prodex run exec "review this repo"
prodex run --profile second
prodex run --profile second --no-auto-rotate
```

## Debug the Environment

```bash
prodex doctor
prodex doctor --quota
```

## Notes

- `prodex` is only a wrapper; login is still handled by `codex`
- `prodex login` without `--profile` auto-creates or reuses a unique profile derived from the logged-in email
- that auto-create flow relies on being able to read the ChatGPT account email from `tokens.id_token` in `auth.json`
- built-in quota checks only work for profiles using ChatGPT auth
- `prodex run` performs quota preflight unless you use `--skip-quota-check`
- a profile is only treated as ready when both `5h` and `weekly` quota windows exist and still have remaining capacity
- `prodex run` auto-rotates to the next ready profile when the current one hits a limit, including when you pass `--profile`
- use `--no-auto-rotate` if you want the selected profile to stay blocked instead