@loongphy/codex-auth 0.2.2-alpha.3 → 0.2.2

package/README.md

@@ -42,18 +42,23 @@ npx @loongphy/codex-auth list
   npm packages currently support Linux x64, macOS x64, macOS arm64, and Windows x64.
 
 > [!NOTE]
+> If you only installed `@loongphy/codex-auth` with npm, you do not need any legacy cleanup steps.
 > Older Bash/PowerShell GitHub-release installs could leave a standalone `codex-auth` binary outside npm's install path.
-> Those legacy installs can shadow the npm package or a local source build, so remove them during migration.
+> If you previously used those legacy installers, remove the leftover binaries and profile changes during migration.
 
 ### Uninstall
 
+#### npm
+
 Remove the npm package:
 
 ```shell
 npm uninstall -g @loongphy/codex-auth
 ```
 
-Remove old Bash-installer leftovers on Linux/macOS/WSL2:
+#### Legacy Bash Installer
+
+For non-npm installs on Linux/macOS/WSL2 only:
 
 ```shell
 rm -f ~/.local/bin/codex-auth
@@ -61,13 +66,15 @@ rm -f ~/.local/bin/codex-auth-auto
 sed -i '/# Added by codex-auth installer/,+1d' ~/.bashrc ~/.bash_profile ~/.profile ~/.zshrc ~/.zprofile 2>/dev/null || true
 ```
 
-If you used fish:
+If you used fish, also remove the old profile entry:
 
 ```shell
 sed -i '/# Added by codex-auth installer/,+3d' ~/.config/fish/config.fish 2>/dev/null || true
 ```
 
-Remove old PowerShell-installer leftovers on Windows:
+#### Legacy PowerShell Installer
+
+For non-npm installs on Windows only:
 
 ```powershell
 Remove-Item "$env:LOCALAPPDATA\codex-auth\bin\codex-auth.exe" -Force -ErrorAction SilentlyContinue
@@ -79,13 +86,6 @@ Remove-Item "$env:LOCALAPPDATA\codex-auth\bin\codex-auth-auto.exe" -Force -Error
 )
 ```
 
-After cleanup, verify which binary is still active:
-
-```shell
-which codex-auth
-codex-auth --version
-```
-
 ## Commands
 
 ### Account Management
@@ -98,8 +98,6 @@ codex-auth --version
 | `codex-auth remove` | Remove accounts with interactive multi-select |
 | `codex-auth status` | Show auto-switch, service, and usage status |
 
-> `codex-auth add` is still accepted as a deprecated alias for `codex-auth login`.
-
 ### Import
 
 | Command | Description |
@@ -114,7 +112,7 @@ codex-auth --version
 |---------|-------------|
 | `codex-auth config auto enable\|disable` | Enable or disable background auto-switching |
 | `codex-auth config auto [--5h <%>] [--weekly <%>]` | Set auto-switch thresholds |
-| `codex-auth config api enable\|disable` | Use API-backed fallback or local-only usage refresh |
+| `codex-auth config api enable\|disable` | Enable or disable both usage refresh and team name refresh API calls |
 
 ---
 
@@ -243,25 +241,12 @@ When auto-switching is enabled, a long-running background watcher refreshes the
 - 5h remaining drops below the configured 5h threshold (default `10%`), or
 - weekly remaining drops below the configured weekly threshold (default `5%`)
 
-Candidate selection follows the current watcher behavior:
-
-- when `config api enable` is on, the watcher keeps a daemon-local in-memory candidate index, does bounded top-candidate upkeep in the background, and revalidates only the best few stale candidates before a switch
-- in local-only mode, accounts without any usage snapshot are still treated as fresh candidates with full quota
-- when the 5h trigger comes from an actual 300-minute window or an unlabeled primary window, free accounts use a stronger real-time 5h guard and switch no later than `35%` remaining even if the configured 5h threshold is lower
-- free accounts that expose only a single `10080`-minute weekly window are still eligible auto-switch candidates; that weekly remaining percentage is used as their candidate score
-
 The managed background worker is long-running on all supported platforms:
 
 - Linux/WSL: persistent `systemd --user` service
 - macOS: `LaunchAgent`
 - Windows: scheduled task that launches the long-running helper at logon, restarts it after failures, has no 72-hour execution cap, and also starts it immediately on enable
 
-The watcher checks local rollout usage roughly once per second and prefers local rollout events over API polling. In watch mode it caches the newest rollout file between bounded full rescans so large `~/.codex/sessions` trees are not re-walked every second. When `config api enable` is on, the usage API remains a slower fallback, active-account API cooldown resets when the active account changes, and candidate revalidation is driven by a daemon-local in-memory candidate index instead of batch-refreshing every account on every loop.
-
-Successful foreground `codex-auth` commands also reconcile the managed auto-switch service, so a disabled config removes stale background units while an enabled background worker is refreshed onto the current binary after upgrades or service drift.
-
-Changing thresholds updates `registry.json`, and the running watcher picks them up on the next polling cycle without a service restart.
-
 #### Usage Refresh Source
 
 API-backed fallback:
@@ -278,8 +263,6 @@ codex-auth config api disable
 
 Changing `config api` updates `registry.json` immediately. `api enable` is shown as API mode and `api disable` is shown as local mode.
 
-Implementation details are documented in [`docs/auto-switch.md`](docs/auto-switch.md).
-
 ## Q&A
 
 ### Why is my usage limit not refreshing?
@@ -345,8 +328,6 @@ Verify with:
 codex exec "say hello"
 ```
 
-> **Output format:** Each converted file contains `auth_mode`, `OPENAI_API_KEY`, `tokens` (with `id_token`, `access_token`, `refresh_token`, `account_id`), and `last_refresh`. The `refresh_token` field is required for token refresh to work.
-
 ## Disclaimer
 
 This project is provided as-is and use is at your own risk.
@@ -354,8 +335,8 @@ This project is provided as-is and use is at your own risk.
 **Usage Data Refresh Source:**
 `codex-auth` supports two sources for refreshing account usage/usage limit information:
 
-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 is the current default mode.
-2. **Local-only:** When `config api disable` is on, the tool scans local `~/.codex/sessions/*/rollout-*.jsonl` files without making 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.
+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.
+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.
 
 **API Call Declaration:**
-By enabling API-based usage refresh, this tool will send your ChatGPT access token to OpenAI's servers (specifically `https://chatgpt.com/backend-api/wham/usage`) to fetch current quota information. This behavior may be detected by OpenAI and could violate their terms of service, potentially leading to account suspension or other risks. The decision to use this feature and any resulting consequences are entirely yours.
+By enabling API(`codex-auth config api enable`), this tool will send your ChatGPT access token to OpenAI's servers, including `https://chatgpt.com/backend-api/wham/usage` for usage limit and `https://chatgpt.com/backend-api/accounts/check/v4-2023-04-27` for team name. This behavior may be detected by OpenAI and could violate their terms of service, potentially leading to account suspension or other risks. The decision to use this feature and any resulting consequences are entirely yours.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loongphy/codex-auth",
-  "version": "0.2.2-alpha.3",
+  "version": "0.2.2",
   "description": "CLI for switching Codex accounts",
   "license": "MIT",
   "repository": {
@@ -20,10 +20,10 @@
     "README.md"
   ],
   "optionalDependencies": {
-    "@loongphy/codex-auth-linux-x64": "0.2.2-alpha.3",
-    "@loongphy/codex-auth-darwin-x64": "0.2.2-alpha.3",
-    "@loongphy/codex-auth-darwin-arm64": "0.2.2-alpha.3",
-    "@loongphy/codex-auth-win32-x64": "0.2.2-alpha.3"
+    "@loongphy/codex-auth-linux-x64": "0.2.2",
+    "@loongphy/codex-auth-darwin-x64": "0.2.2",
+    "@loongphy/codex-auth-darwin-arm64": "0.2.2",
+    "@loongphy/codex-auth-win32-x64": "0.2.2"
   },
   "scripts": {
     "check:versions": "node scripts/npm/check-versions.mjs",