@loongphy/codex-auth-linux-x64 0.2.5 → 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 +10 -23
- 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 22+ 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
|
package/bin/codex-auth
CHANGED
|
Binary file
|