@loongphy/codex-auth-linux-x64 0.2.4 → 0.2.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -4
- package/bin/codex-auth +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -47,7 +47,7 @@ npx @loongphy/codex-auth list
|
|
|
47
47
|
> If you previously used those legacy installers, remove the leftover binaries and profile changes during migration.
|
|
48
48
|
> API-backed usage refresh and team-name refresh use Node.js `fetch`.
|
|
49
49
|
> npm installs already satisfy that requirement.
|
|
50
|
-
> Legacy standalone binary installs need Node.js
|
|
50
|
+
> Legacy standalone binary installs need Node.js 22+ on `PATH` when `codex-auth config api enable` is used.
|
|
51
51
|
|
|
52
52
|
## Storage Root
|
|
53
53
|
|
|
@@ -151,8 +151,6 @@ Interactive: shows email, 5h, weekly, and last activity.
|
|
|
151
151
|
codex-auth switch
|
|
152
152
|
```
|
|
153
153
|
|
|
154
|
-
Before the picker opens, `switch` refreshes usage for all stored accounts with a maximum concurrency of `3`, so the picker is based on a fresh cross-account snapshot. If a refresh returns a non-`200` HTTP status such as `401` or `403`, that row shows the status in both usage columns. If a stored account snapshot cannot make a ChatGPT usage request at all because the required auth fields are missing, that row shows `MissingAuth` instead of the previous usage values. No extra usage refresh is attempted after the switch completes.
|
|
155
|
-
|
|
156
154
|
|
|
157
155
|
|
|
158
156
|
Non-interactive: fuzzy match by email or alias.
|
|
@@ -326,7 +324,7 @@ This project is provided as-is and use is at your own risk.
|
|
|
326
324
|
**Usage Data Refresh Source:**
|
|
327
325
|
`codex-auth` supports two sources for refreshing account usage/usage limit information:
|
|
328
326
|
|
|
329
|
-
1. **API (default):** When `config api enable` is on, the tool makes direct HTTPS requests to OpenAI's endpoints using your account's access token. This enables both usage refresh and team name refresh.
|
|
327
|
+
1. **API (default):** When `config api enable` is on, the tool makes direct HTTPS requests to OpenAI's endpoints using your account's access token. This enables both usage refresh and team name refresh. npm installs already satisfy the runtime requirement; legacy standalone binary installs need Node.js 22+ on `PATH`.
|
|
330
328
|
2. **Local-only:** When `config api disable` is on, the tool scans local `~/.codex/sessions/*/rollout-*.jsonl` files for usage data and skips team name refresh API calls. This mode is safer, but it can be less accurate because recent Codex rollout files often contain `rate_limits: null`, so the latest local usage limit data may lag by several hours.
|
|
331
329
|
|
|
332
330
|
**API Call Declaration:**
|
package/bin/codex-auth
CHANGED
|
Binary file
|