ed15b24c1ccf0234e6b3435149a6f1c1e709579d1259f1d09402688799b149bd config-baseline.channel.json

back to local runtimes already present on the machine:

- Claude Code CLI: `claude-cli/claude-opus-4-7`

- Codex CLI: `codex-cli/gpt-5.5`

The model-assisted planner cannot mutate config directly. It must translate the

- Doctor also scans `~/.openclaw/cron/jobs.json` (or `cron.store`) for legacy cron job shapes and can rewrite them in place before the scheduler has to auto-normalize them at runtime.

- On Linux, doctor warns when the user's crontab still runs legacy `~/.openclaw/bin/ensure-whatsapp.sh`; that script is no longer maintained and can log false WhatsApp gateway outages when cron lacks the systemd user-bus environment.

- When WhatsApp is enabled, doctor checks for a degraded Gateway event loop with local `openclaw-tui` clients still running. `doctor --fix` stops only verified local TUI clients so WhatsApp replies are not queued behind stale TUI refresh loops.

- Doctor cleans legacy plugin dependency staging state created by older OpenClaw versions. It also repairs missing downloadable plugins that are referenced by config, such as `plugins.entries`, configured channels, configured provider/search settings, or configured agent runtimes. During package updates, doctor skips package-manager plugin repair until the package swap is complete; rerun `openclaw doctor --fix` afterward if a configured plugin still needs recovery. If the download fails, doctor reports the install error and preserves the configured plugin entry for the next repair attempt.

- Doctor repairs stale plugin config by removing missing plugin ids from `plugins.allow`/`plugins.entries`, plus matching dangling channel config, heartbeat targets, and channel model overrides when plugin discovery is healthy.

- Doctor quarantines invalid plugin config by disabling the affected `plugins.entries.<id>` entry and removing its invalid `config` payload. Gateway startup already skips only that bad plugin so other plugins and channels can keep running.

You will also see the word **harness** in code. A harness is the implementation

that provides an agent runtime. For example, the bundled Codex harness

There are two runtime families:

`codex`.

- **CLI backends** run a local CLI process while keeping the model ref

canonical. For example, `anthropic/claude-opus-4-7` with

2. If the user asks for **Codex as the embedded runtime** or wants the normal

subscription-backed Codex agent experience, use `openai/<model>`.

3. If the user explicitly chooses **PI for an OpenAI model**, keep the model ref

4. If legacy config still contains **`openai-codex/*` model refs**, repair it to

`openai/<model>` with `openclaw doctor --fix`.

5. If the user explicitly says **ACP**, **acpx**, or **Codex ACP adapter**, use

OpenClaw chooses an embedded runtime after provider and model resolution:

pairs.

compatibility runtime. Use an explicit runtime id when the run must be

strict.

CLI backend aliases are different from embedded harness ids. The preferred

Claude CLI form is:

agents: {

defaults: {

model: "anthropic/claude-opus-4-7",

},

},

}

Legacy refs such as `claude-cli/claude-opus-4-7` remain supported for

compatibility, but new config should keep the provider/model canonical and put

`auto` mode is intentionally conservative for most providers. OpenAI agent

models are the exception: unset runtime and `auto` both resolve to the Codex

harness. Explicit PI runtime config remains an opt-in compatibility route for

`openai/*` agent turns; when paired with a selected `openai-codex` auth profile,

OpenClaw routes PI internally through the legacy Codex-auth transport while

If `openclaw doctor` warns that the `codex` plugin is enabled while

`openai-codex/*` remains in config, treat that as legacy route state. Run

- A runtime id such as `codex` tells you which loop is executing the turn.

- A channel label such as Telegram or Discord tells you where the conversation is happening.

<Accordion title="OpenAI provider/runtime split">

OpenAI-family routes are prefix-specific:

See [OpenAI](/providers/openai) and [Codex harness](/plugins/codex-harness). If the provider/runtime split is confusing, read [Agent runtimes](/concepts/agent-runtimes) first.

</Accordion>

<Accordion title="CLI runtimes">

Legacy `claude-cli/*`, `google-gemini-cli/*`, and `codex-cli/*` refs migrate back to canonical provider refs with the runtime recorded separately.

- Direct public Anthropic requests support the shared `/fast` toggle and `params.fastMode`, including API-key and OAuth-authenticated traffic sent to `api.anthropic.com`; OpenClaw maps that to Anthropic `service_tier` (`auto` vs `standard_only`)

- Preferred Claude CLI config keeps the model ref canonical and selects the CLI

backend separately: `anthropic/claude-opus-4-7` with

`claude-cli/claude-opus-4-7` refs still work for compatibility.

<Note>

- Provider: `openai-codex`

- Auth: OAuth (ChatGPT)

- Native Codex app-server harness docs: [Codex harness](/plugins/codex-harness)

- Legacy model refs: `codex/gpt-*`

- Plugin boundary: `openai-codex/*` loads the OpenAI plugin; the native Codex app-server plugin is selected only by the Codex harness runtime or legacy `codex/*` refs.

- Shares the same `/fast` toggle and `params.fastMode` config as direct `openai/*`; OpenClaw maps that to `service_tier=priority`

- `openai-codex/gpt-5.5` uses the Codex catalog native `contextWindow = 400000` and default runtime `contextTokens = 272000`; override the runtime cap with `models.providers.openai-codex.models[].contextTokens`

- Policy note: OpenAI Codex OAuth is explicitly supported for external tools/workflows like OpenClaw.

- Older `openai-codex/gpt-5.1*`, `openai-codex/gpt-5.2*`, and `openai-codex/gpt-5.3*` refs are suppressed because ChatGPT/Codex OAuth accounts reject them; use `openai-codex/gpt-5.5` or the native Codex runtime route instead.

agents: {

defaults: {

model: { primary: "openai/gpt-5.5" },

},

},

}

</Card>

</CardGroup>