Codex

For one account, use the default Codex provider with your normal Codex login. Provider setup covers installation, Settings > Providers, and custom binaries or environment variables.

Quota through tproxy

When Codex connects through tproxy, VC reads the endpoint and API credentials from that Codex instance. Use Refresh provider status in Settings > Providers, then open Usage > Limits to see each upstream account’s quota. No separate quota source is needed.

The tproxy server must support GET /v1/limits. VC checks for this API before showing proxy quota, and marks missing or stale data as unavailable. Each account’s windows remain separate; their percentages are not added together.

Use multiple accounts

A shared Codex home with a shadow home lets work and personal accounts continue the same threads. The accounts share Codex sessions and configuration while keeping their own login and available models.

Add a second Codex instance in Settings > Providers with the Add Codex account button in the Codex instance’s detail pane. The dialog suggests a matching shadow home path from the instance’s name; accept it or set the values yourself:

Both instances must use the same CODEX_HOME path. VC prepares the shared state in the shadow directory; do not populate it by copying your whole Codex home.

Then sign the second account in from its detail pane: Sign in to Codex uses the same browser flow as codex login. Open the sign-in page and finish signing in with your ChatGPT account. If you are connecting from another machine and the browser cannot reach localhost after sign-in, copy the full URL from its address bar and paste it into the provider’s sign-in form in VC.

You can also sign in from a terminal on the environment’s machine instead:

mkdir -p ~/.codex_personal
CODEX_HOME=~/.codex_personal codex login

The shadow account needs its own auth.json file. If Codex uses an OS credential store, configure file storage for this setup. See OpenAI’s credential storage guide.

Use a completely separate CODEX_HOME path, with no shadow home, when you want separate Codex sessions and configuration. That instance cannot continue threads from the other home.

Import account credentials

In web or desktop Settings > Providers, select Codex and choose a JSON file under Import Codex JSON. VC accepts Codex auth.json files and sub2api OAuth exports, including files containing several accounts.

For each account, create a new Codex account or replace the selected account. VC checks account IDs for duplicates and offers the existing account as the destination. Confirm replacement before importing over existing credentials; this stops running threads for that account and keeps their history. Credentials are saved on the selected environment, including when you connect remotely.

Switch accounts in an existing thread

Choose the other account from the thread’s model picker and confirm the switch. Accounts sharing the thread’s CODEX_HOME path can resume the native conversation. A separate home starts a fresh agent with saved task context in the same VC thread. See account recovery.

Older environments offer only accounts with compatible home paths. If two instances show the same unexpected account or models, check their reported accounts, refresh provider status, and confirm the second instance has its own shadow path and login. A shadow-home conflict usually means the directory contains a copied Codex setup. Use a fresh shadow directory and sign in again.

Answer questions

Answer in the thread’s question panel to let Codex continue. Codex is asked to pause its task while waiting for your response. Queued and scheduled messages wait while a question is open, and your answer takes priority over queued work.

Some Codex versions send questions as messages. These questions survive reconnects and can be dismissed without sending an answer. Other questions need the original running Codex session; if the environment or provider restarts, start a new turn so Codex can ask again.

Approve app access

Codex tools can request access to another app. Respond to the named app’s request in the thread on web, desktop, or mobile. Some tools offer access for one request, the current session, or permanently. See Permission modes for command and file approvals.

Send feedback to OpenAI

In an existing Codex thread, send /feedback with an optional description, for example /feedback The agent stopped before finishing the tests. This uploads the conversation and Codex logs to OpenAI. The returned thread ID can be shared with OpenAI support.