@loongphy/codex-auth-linux-x64 0.2.2-alpha.3 → 0.2.2-alpha.4

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
@@ -243,25 +243,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:
@@ -345,8 +332,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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loongphy/codex-auth-linux-x64",
-  "version": "0.2.2-alpha.3",
+  "version": "0.2.2-alpha.4",
   "description": "@loongphy/codex-auth binary for linux x64",
   "license": "MIT",
   "repository": {