How do I keep the Codex login state while using a third-party API?

If you only want to use a third-party API in Codex CLI or Codex App, follow the regular Codex setup guide. If you also need plugins, Remote Control, mobile control, or official session sync, keep the official Codex login state and route model requests to the third-party API. The key is to separate two layers:

Layer	Handles	Recommended source
Auth layer	Codex App login state, plugins, Remote Control, session sync	Official ChatGPT / Codex login
Inference layer	Model requests, model list, API Key usage	LLMEasy or another third-party API

Do not share auth.json, refresh_token, id_token, experimental_bearer_token, or any API Key in public issues, chats, screenshots, or logs.

Setup options

Configure with CC Switch
Manual setup

This is the recommended path. CC Switch exposes the login-preserving behavior as a UI setting, which is safer for most users.

Configure the Codex API provider first

Follow the Codex CLI steps in the CC Switch guide to install CC Switch and add a Codex API provider.Fill the provider fields with your LLMEasy settings:

Field	Value
Provider Name	`LLMEasy` or your preferred name
Base URL	`https://www.llmeasy.ru/v1`
API Key	Your LLMEasy API Key
API format	`OpenAI Responses API`

Save the provider, then set it to In Use.

CC Switch shows a configured third-party Codex API provider and highlights the settings entry.

Open CC Switch settings

Return to the CC Switch main window and click the Settings icon in the upper-left corner.

Enable Codex App Enhancements

In the General tab, find Codex App Enhancements and turn on Keep official login when switching third-party providers.This keeps the official Codex App login state when you switch to a third-party provider. After enabling it, Codex App can continue using official plugins, Remote Control, and mobile control while model requests use the selected third-party API provider.

The Codex App Enhancements toggle is enabled in the CC Switch settings page.

Restart Codex App and verify

Fully quit and reopen Codex App. Confirm:

Codex App still shows the official account login state
Plugins, Remote Control, or mobile control still work
The active provider is the third-party API provider selected in CC Switch
A test message returns normally

Manual setup is for advanced users who are comfortable editing local Codex files. Use CC Switch when possible.

Keep the official Codex login state

Sign in to your official ChatGPT / Codex account in Codex App or Codex CLI first, then confirm Remote Control or plugins work.Your ~/.codex/auth.json should keep the official login state. It usually has the auth_mode = chatgpt token structure, not a plain OPENAI_API_KEY object.The structure looks like this. Do not copy the placeholder values; keep the real file generated by your local official login:

{
  "auth_mode": "chatgpt",
  "tokens": {
    "id_token": "OFFICIAL_ID_TOKEN",
    "refresh_token": "OFFICIAL_REFRESH_TOKEN",
    "account_id": "OFFICIAL_ACCOUNT_ID"
  },
  "last_refresh": "2026-05-10T14:42:19+08:00"
}

These tokens represent your official account login state. Keep them local and never commit or share them.

Edit config.toml

Open ~/.codex/config.toml, then add or merge this provider config.

model_provider = "llmeasy"
model = "gpt-5.5"
review_model = "gpt-5.4"
model_reasoning_effort = "high"
model_context_window = 1000000
model_auto_compact_token_limit = 900000
windows_wsl_setup_acknowledged = true

[model_providers]
[model_providers.llmeasy]
name = "LLM Easy"
base_url = "https://www.llmeasy.ru/v1"
wire_api = "responses"
requires_openai_auth = true
experimental_bearer_token = "YOUR_API_KEY"
request_max_retries = 4
stream_max_retries = 8
stream_idle_timeout_ms = 300000
supports_websockets = false

Replace YOUR_API_KEY with your LLMEasy API Key.This differs from the regular API Key mode:

Config	Purpose
`requires_openai_auth = true`	Keeps the official Codex login state for plugins, Remote Control, and session sync
`experimental_bearer_token = "YOUR_API_KEY"`	Uses your third-party API Key for model requests
`base_url = "https://www.llmeasy.ru/v1"`	Sends model requests to the LLMEasy OpenAI-compatible / Responses API endpoint

Restart and verify

Fully quit Codex App, then reopen it. Check in this order:

The official login state is still present
Remote Control or plugins can open
A test message routes through the third-party API provider
If the model is unavailable, confirm model is copied from the GPT Key group in the model plaza

FAQ

How is this different from the regular Codex API setup?

The regular setup only makes model requests use a third-party API. This setup also keeps the official login state, so Codex App official features still work. If you do not need plugins, Remote Control, or mobile control, the regular Codex setup guide is simpler.

Why not put the API Key in auth.json?

In this mode, auth.json stores the official login state. The third-party API Key belongs in experimental_bearer_token inside config.toml. If you replace auth.json with a plain OPENAI_API_KEY object, Codex App may stop recognizing the official login state, and plugins or Remote Control may stop working.

​Setup options

​FAQ

​How is this different from the regular Codex API setup?

​Why not put the API Key in auth.json?

​References

Setup options

FAQ

How is this different from the regular Codex API setup?

Why not put the API Key in auth.json?

References