DocumentationIntegrations

Integrations

Codex App

A persistent XEDOC connection for the desktop app, with the models ready to select.

Connect automatically

#

Install Node.js 20 or later, fully quit the selected client, and run this command. The assistant checks your key, shows the files it will update, and saves a private backup before applying changes.

Windowspowershell
npx.cmd --yes https://xedoc.top/downloads/xedoc-setup-1.0.1.tgz --clients codex-app

Reopen Codex

#

Fully quit and reopen the app. Start a new task and choose a model below the input. Setup selects XEDOC in the shared Codex configuration and installs the current model catalog. Setup preserves native Codex model instructions, tool capabilities and supported reasoning levels. Choose the same reasoning level when comparing providers; Ultra enables proactive subagent delegation on supported Codex models.

The App and CLI share settings

Changing the global model_provider affects clients using the same Codex configuration directory. CLI-only setup uses a separate profile; choosing the App intentionally updates the shared global provider.

A key the app can actually find

#

Automatic setup creates a private XEDOC credential file and a small persistent helper. Codex invokes that helper through an absolute Node.js path. This avoids relying on shell-only environment variables that a desktop app may not inherit.

The helper stays in your XEDOC configuration directory, not an npm temporary directory. If Node.js is moved or removed, install Node again and rerun xedoc. Existing Codex login credentials are preserved.

Manual provider settings

#

Open Settings → Configuration → Open config.toml. Merge these values into the existing file, keeping other settings and provider tables. Ensure XEDOC_API_KEY is available in the environment of the process that launches Codex.

config.tomltoml
model = "gpt-5.6-terra"
model_provider = "xedoc"

[model_providers.xedoc]
name = "XEDOC"
base_url = "https://api.xedoc.top/v1"
env_key = "XEDOC_API_KEY"
wire_api = "responses"

Desktop environment

Setting $env:XEDOC_API_KEY or export XEDOC_API_KEY only affects that terminal and processes it launches. For a normal desktop launch, use the automatic credential helper or configure the variable in the app’s launch environment.

The manual provider alone may not list every XEDOC model. Automatic setup also writes model_catalog_json. Select a model supported by your current model list.