@loongphy/codex-auth-linux-x64 0.2.4 → 0.2.6-alpha.1
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 +11 -26
- package/bin/codex-auth +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,29 +41,6 @@ npx @loongphy/codex-auth list
|
|
|
41
41
|
|
|
42
42
|
npm packages currently support Linux x64, Linux arm64, macOS x64, macOS arm64, Windows x64, and Windows arm64.
|
|
43
43
|
|
|
44
|
-
> [!NOTE]
|
|
45
|
-
> If you only installed `@loongphy/codex-auth` with npm, you do not need any legacy cleanup steps.
|
|
46
|
-
> Older Bash/PowerShell GitHub-release installs could leave a standalone `codex-auth` binary outside npm's install path.
|
|
47
|
-
> If you previously used those legacy installers, remove the leftover binaries and profile changes during migration.
|
|
48
|
-
> API-backed usage refresh and team-name refresh use Node.js `fetch`.
|
|
49
|
-
> npm installs already satisfy that requirement.
|
|
50
|
-
> Legacy standalone binary installs need Node.js 18+ on `PATH` when `codex-auth config api enable` is used.
|
|
51
|
-
|
|
52
|
-
## Storage Root
|
|
53
|
-
|
|
54
|
-
`codex-auth` uses the same Codex state root as the current process. Resolution order:
|
|
55
|
-
|
|
56
|
-
1. `CODEX_HOME` when set to a non-empty existing directory
|
|
57
|
-
2. `HOME/.codex`
|
|
58
|
-
3. `USERPROFILE/.codex` on Windows
|
|
59
|
-
|
|
60
|
-
When `CODEX_HOME` is set, `codex-auth` follows Codex and requires that directory to already exist.
|
|
61
|
-
That means you can isolate auth, registry, config, and session files by running:
|
|
62
|
-
|
|
63
|
-
```shell
|
|
64
|
-
CODEX_HOME=/path/to/custom-codex codex-auth list
|
|
65
|
-
```
|
|
66
|
-
|
|
67
44
|
### Uninstall
|
|
68
45
|
|
|
69
46
|
#### npm
|
|
@@ -76,6 +53,13 @@ npm uninstall -g @loongphy/codex-auth
|
|
|
76
53
|
|
|
77
54
|
#### Legacy Bash Installer
|
|
78
55
|
|
|
56
|
+
> [!NOTE]
|
|
57
|
+
> If you only installed `@loongphy/codex-auth` with npm, you do not need any legacy cleanup steps.
|
|
58
|
+
> Older Bash/PowerShell GitHub-release installs could leave a standalone `codex-auth` binary outside npm's install path.
|
|
59
|
+
> If you previously used those legacy installers, remove the leftover binaries and profile changes during migration.
|
|
60
|
+
> API-backed usage refresh and team-name refresh use Node.js `fetch`.
|
|
61
|
+
> npm installs already satisfy that requirement.
|
|
62
|
+
|
|
79
63
|
For non-npm installs on Linux/macOS/WSL2 only:
|
|
80
64
|
|
|
81
65
|
```shell
|
|
@@ -138,6 +122,9 @@ Remove-Item "$env:LOCALAPPDATA\codex-auth\bin\codex-auth-auto.exe" -Force -Error
|
|
|
138
122
|
|
|
139
123
|
### List Accounts
|
|
140
124
|
|
|
125
|
+
> [!IMPORTANT]
|
|
126
|
+
> Built-in Node proxy support for API refresh requires Node.js `22.21.0+` or `24.0.0+`.
|
|
127
|
+
|
|
141
128
|
```shell
|
|
142
129
|
codex-auth list
|
|
143
130
|
codex-auth list --debug
|
|
@@ -151,8 +138,6 @@ Interactive: shows email, 5h, weekly, and last activity.
|
|
|
151
138
|
codex-auth switch
|
|
152
139
|
```
|
|
153
140
|
|
|
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
141
|
|
|
157
142
|
|
|
158
143
|
Non-interactive: fuzzy match by email or alias.
|
|
@@ -326,7 +311,7 @@ This project is provided as-is and use is at your own risk.
|
|
|
326
311
|
**Usage Data Refresh Source:**
|
|
327
312
|
`codex-auth` supports two sources for refreshing account usage/usage limit information:
|
|
328
313
|
|
|
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.
|
|
314
|
+
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
315
|
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
316
|
|
|
332
317
|
**API Call Declaration:**
|
package/bin/codex-auth
CHANGED
|
Binary file
|