llm-openai-codex

LLM plugin for accessing ChatGPT/Codex-backed OpenAI models through the Responses API.

Changes from the original plugin

• Package renamed to llm-openai-codex.
• Model prefix changed to codex/.
• Plugin-owned auth is stored in LLM's user config directory as auth-codex.json, with borrowed fallback to ${CODEX_HOME:-~/.codex}/auth.json.
• llm codex auth commands manage login, local or SCP import, status, refresh, and logout.
• Explicit verbosity option maps to Responses API text.verbosity.
• Extra Responses API options are forwarded when LLM accepts them.
• Missing account_id values are derived from OAuth JWT claims when possible.
• Added llm codex usage showing current Codex plan usage.
• Registers known hidden/fallback Codex models such as gpt-5.3-codex-spark.
• Added OpenAI's server-side web_search tool via -T WebSearch (shared with LLM's built-in OpenAI models) or -o web_search 1.
• Streams visible reasoning summaries and round-trips encrypted reasoning between turns (requires LLM 0.32 or later).
• Tool call names stream as soon as the model starts a call, before the arguments finish generating.

Installation

Install the plugin in the same environment as LLM:

llm install llm-openai-codex

Authentication: plugin-owned or borrowed

The plugin can use ChatGPT OAuth credentials from two places, in this order:

1. Plugin-owned auth at auth-codex.json in LLM's user config directory. This is used whenever the file exists. Create it with llm codex login, copy local Codex CLI credentials with llm codex import, or import a remote access-token snapshot over SCP.
2. Borrowed Codex CLI auth at ${CODEX_HOME:-~/.codex}/auth.json. If plugin-owned auth does not exist, the plugin automatically uses this file; no import is required.

Choose how to set up plugin-owned auth:

# Perform a new OAuth login and save its credentials for this plugin
llm codex login [--device-code]

# Reuse an existing Codex CLI login by copying its current credentials
llm codex import

# Import an explicit local Codex auth file
llm codex import --path /path/to/auth.json

# Import a remote access-token snapshot (the trailing colon selects SCP)
llm codex import --path hostname:
llm codex import --path user@hostname:

login performs a new OAuth flow. A local import performs no login: it copies the current Codex CLI tokens into auth-codex.json, so later plugin refreshes update the plugin's copy instead of the Codex CLI file. Import creates separate storage, not a fresh OAuth authorization. It is useful when you are already logged in with Codex CLI but do not want the plugin to keep writing to its auth file. Local imports refuse to overwrite existing plugin-owned auth; run llm codex logout first if you intend to replace it.

An import target ending in : uses the system scp executable to copy the fixed remote file ~/.codex/auth.json. Arbitrary remote paths and remote CODEX_HOME discovery are not supported. The machine running LLM must have scp installed and SSH configured for the target; host-key, password, and key-passphrase prompts use the current terminal. The downloaded JSON is validated in a temporary directory before plugin auth is written, and temporary files are always removed.

SCP imports deliberately discard the remote refresh token and store only a non-refreshable snapshot (login_type: "scp"). The access token is used until its JWT expiry. If the expiry cannot be decoded, the token is sent unchanged so the backend can accept or reject it. Once a decoded expiry has passed, commands report that the SCP import must be repeated; llm codex refresh never refreshes an SCP snapshot.

Repeating an SCP import can safely replace existing plugin auth without a logout only when the existing auth has no refresh token and has a decodable, expired access-token expiry. This check happens before scp runs. Otherwise the command identifies the existing auth file and asks you to inspect it with llm codex status; remove it with llm codex logout only when replacement is intended. A failed SCP transfer or invalid download leaves the existing snapshot untouched. If plugin auth changes while the transfer is running, installation is aborted rather than overwriting the newer auth.

OAuth login, local imports, and borrowed Codex CLI auth refresh when a token nears expiry and with llm codex refresh. Refreshing rotates the refresh token. In borrowed mode this modifies the file shared with Codex CLI and can briefly disrupt a simultaneous CLI session; the plugin prints a warning. llm codex status shows the active source and refreshable: yes/no.

llm codex logout only deletes the local plugin-owned auth file, making Codex CLI auth the fallback again. It does not contact an API, revoke a token, or alter a remote machine, and routine re-import of an expired SCP snapshot does not require it.

Plugin commands

llm codex login [--device-code]  # create plugin-owned auth with OAuth
llm codex import                 # copy Codex CLI auth into plugin-owned auth
llm codex import --path PATH     # copy an explicit local auth file
llm codex import --path HOST:    # SCP HOST:~/.codex/auth.json as a snapshot
llm codex status                 # show the active source and refreshability
llm codex refresh                # refresh the active source
llm codex usage                  # show current Codex plan usage
llm codex logout                 # delete local plugin-owned auth only

Usage

List available models:

llm models -q codex

Models are discovered from the Codex API and combined with known hidden/fallback slugs. Availability depends on your plan; a listed fallback may still fail at request time. Discovery is cached for 24 hours in codex_models.json in LLM's user config directory; delete it to force a re-fetch.

Run a prompt and optionally set Responses API verbosity:

llm -m codex/gpt-5.6-luna "Hello"
llm -m codex/gpt-5.6-terra -o verbosity low "Summarize this"

Image attachments (-a image.png) are sent at low detail to limit token use.

Reasoning

Codex models are reasoning models. Visible reasoning summaries stream to standard error while a response runs; hide them with -R/--hide-reasoning. Requests run stateless (store: false), so the plugin asks the API for encrypted reasoning items and echoes them back on later turns. The model keeps its chain of thought across tool calls and continued conversations (llm -c, llm chat -c).

Web search

OpenAI's server-side search (it runs on OpenAI's servers, not locally) is available as a server-side tool using the same WebSearch class as LLM's built-in OpenAI models:

llm -m codex/gpt-5.6-luna -T WebSearch "What happened in AI news today?"
llm -m codex/gpt-5.6-luna -T 'WebSearch(external_web_access=True)' "Latest stable Python release?"
llm -m codex/gpt-5.6-luna -T 'WebSearch(allowed_domains=["python.org"], search_context_size="high")' "Recent Python changes"

external_web_access requests live internet access instead of the cached index. Run llm tools -m codex/gpt-5.6-luna to see every constructor argument, including domain filters, user location, and image search. Conversations continued with llm -c restore the configured tool automatically. Searches are recorded in the conversation log as server-executed tool calls; when the final response payload carries more complete search data than the stream did, the recorded values are refreshed from it. Raw provider specifications also work, for server-side tools the plugin does not know about yet:

llm -m codex/gpt-5.6-luna -T 'ServerSideTool({"type": "web_search"})' "..."

The older option-based form is still supported and remains the way to set a per-model default:

llm -m codex/gpt-5.6-luna -o web_search 1 -o web_search_live 1 "Latest stable Python release?"
llm models options set codex/gpt-5.6-luna web_search 1

web_search_live maps to external_web_access and web_search_context_size to search_context_size. An explicit -T WebSearch tool takes precedence over the option-based form. Availability depends on the plan and model.

Development

uv run pytest
uv run llm plugins
uv run llm codex status

Releasing

1. Finish and verify the feature/fix commits.
2. Bump pyproject.toml and commit it separately: git add pyproject.toml && git commit -m "bump: v0.5.0".
3. Tag and push: git tag v0.5.0 && git push origin main v0.5.0.
4. Create the release: gh release create v0.5.0 --generate-notes.

The whole flow is version commit, tag, push, then GitHub Release. The release triggers testing and PyPI publication.