Codex AM

Manage saved Codex accounts, check remaining usage, and switch accounts from a VS Code sidebar on Windows.

Features

• Automatically save the current Codex account.
• Add another account through browser sign-in without logging out of the current account.
• View remaining 5-hour and weekly usage, reset times, plan, and workspace information when available.
• Search saved accounts and keep the filter when the sidebar refreshes or reopens.
• Switch to a saved account and reload the current VS Code window.
• Remove inactive saved accounts without signing out of Codex.
• Store saved credentials locally with Windows DPAPI encryption.

Installation

Install Codex AM from the Visual Studio Marketplace, or install build/codex-am-0.9.19.vsix with Extensions: Install from VSIX....

Requirements:

• Native Windows x64 with a local VS Code installation.
• The Codex extension (openai.chatgpt).
• The Codex CLI available as codex on your PATH for adding accounts through browser sign-in.
• A ChatGPT account using Codex's file-based login cache.

The Marketplace extension ID is codexam.codex-am. If you installed the earlier local extension, codexam-local.codex-account-manager, uninstall it before using this release so that two account managers do not run together. Saved account snapshots in %LOCALAPPDATA%\CodexAM\sessions are shared; usage data is refreshed for the new extension ID.

Getting started

1. Sign in to Codex normally. Codex AM automatically saves and recognizes the current account.
2. Open Codex AM from the Activity Bar, or run Codex AM: Open Accounts in the Command Palette.
3. To add an account, click + in the sidebar and complete the browser sign-in. Codex AM saves the new account without requiring you to log out of the current one.
4. Finish active tasks before switching. Click the arrow beside another saved account to switch. Codex AM updates the shared Codex login cache and reloads the current VS Code window.

Other Codex windows and CLI processes on the same machine can share the same login cache. Switching does not automatically reload those windows or verify that every running Codex process is idle. Resuming a cloud conversation across different accounts has not been verified.

Usage and account controls

The sidebar shows remaining quota. Unknown usage stays unknown rather than appearing as 0%. A full bar means 100% remaining; low remaining usage is highlighted. When the 5-hour quota is exhausted and weekly quota remains, an additional row shows reset progress and the reset time.

Usage refreshes when the sidebar opens or when you click Refresh usage. While loading or after a refresh error, cards keep the latest cached data and show its timestamp. Error details appear in tooltips and expanded account details. The status bar shows the active account and available quota information.

Use Codex AM: Save Current Account in the Command Palette to give the current saved account a name. Account names are preserved as entered. The interface uses English, follows the VS Code color theme, and displays dates in English using the machine's local time zone.

To remove an inactive account, click its trash icon and confirm. This removes its encrypted snapshot and usage cache from Codex AM. It does not sign out of Codex, delete Codex's active login cache, or revoke the account's tokens. The current account cannot be removed; switch to another account first. You can add a removed account again later.

Compatibility

This is an experimental Windows extension developed against Codex extension 26.1021.22027 and its bundled CLI 0.164.0-alpha.11.1. Compatibility with other releases, WSL, Remote SSH, macOS, and Linux has not been verified.

The integration uses file-based authentication. It does not extract credentials from an operating-system keyring. If a saved session expires or is revoked, sign in again and save the account.

Local data

• Saved accounts: %LOCALAPPDATA%\CodexAM\sessions\*.dpapi, encrypted with Windows DPAPI and bound to the current Windows user and machine.
• Active Codex login: CODEX_HOME\auth.json, or %USERPROFILE%\.codex\auth.json by default. Codex AM replaces this file when switching accounts.
• Usage cache: VS Code extension global state.
• Temporary sign-in data: a separate codexam-login-* directory in the system temporary folder. Codex uses this directory during browser sign-in; Codex AM attempts to remove it when the operation finishes or is cancelled.

Do not share login-cache files, account snapshots, access tokens, or refresh tokens.

Development and verification

Use Node.js 22 or later on Windows. Building the optional native bridge also requires the Windows .NET Framework C# compiler.

npm ci --ignore-scripts
npm run check
npm test
npm run test:host
npm run test:ui
npm run package

npm test covers account storage, removal, usage caching, refresh coordination, account switching, RPC handling, and the webview controller.

npm run test:host opens the sidebar in an isolated VS Code Extension Host and checks activation, script loading, refresh, and reopening. It does not switch or reload your current working session. The earlier local extension is disabled in this test host to avoid duplicate command registration.

npm run test:ui uses synthetic account data in headless Chrome to check remaining quota, cached data, errors, filtering, keyboard actions, and narrow, light, and dark layouts. Screenshots are saved in build/ui-preview/. It does not read account credentials or call Codex. Set CODEXAM_TEST_BROWSER to use a different Chrome or Edge executable.

Additional development probes:

npm run probe -- login-sandbox
npm run probe -- capture --label A
npm run probe -- list
npm run probe -- usage --session <session-id>
npm run bridge:build
npm run bridge:probe -- --with-model
npm run test:integration -- --usable <account-with-quota> --exhausted <account-without-quota>

capture reads the selected login cache and writes an encrypted snapshot. Use --auth-file to select the sandbox's auth.json when capturing a sandbox account.

Bridge and integration probes use temporary homes and separate app-server processes. The model probe makes a small model request. For a two-account switch/context check with two usable accounts, use --alternate <second-account-id> instead of --exhausted; this does not reproduce quota exhaustion.

Historical implementation notes and acceptance work are recorded in specs/codex-account-manager/implementation-plan.md and task-list.md. Passing automated checks does not establish that every account-switching or quota-recovery scenario has been verified through the UI.