Hannes Rudolph
34c3d15a6b
* fix(setup): refresh Codex registry with staged install * fix(macos): verify inference before onboarding handoff * fix(setup): use native Codex home for subscription auth * fix(codex): honor attempt-scoped setup config * fix(macos): align onboarding handoff with reopen * fix(setup): await prepared model convergence * fix(ui): avoid false auth state for empty catalog * fix(setup): scope catalog convergence to Codex gateway * fix(setup): publish the committed runtime catalog * fix(models): project configured static runtime models * fix(codex): expose app-server model catalog * fix(models): preserve Codex auth across reloads * fix(ci): align Codex onboarding checks * test(ui): stabilize dock suppression environment * fix(codex): honor discovery config in app-server model catalog The manifest documents discovery.enabled (bundled fallback list) and discovery.timeoutMs (default 2500ms) for model discovery; the new catalog path used the generic 60s request timeout and ignored the enable gate. Also drop the test-only listModels injection seam in favor of vi.mock. * fix(setup): refuse prepared Codex auth over an explicit remote transport configureCodexCliPreparedAuth silently rewrote an explicitly configured websocket/unix app-server to local stdio (keeping a dangling url), moving the credential boundary onto this host. Fail setup with actionable guidance instead; also surface the root cause when the prepared model catalog refresh fails after activation. * refactor(agents): one canonical model-catalog identity key Three near-identical key helpers existed (models-list-result, models-list-configured-static, harness/model-catalog). Export resolveModelCatalogIdentityKey from the route-policy owner, collapse the duplicate dedupe loops into dedupeByKey, make donor enrichment Map-based, and inline the one-off harness-augment wrapper. * fix(macos): restore custodian handoff for fresh activations Landing every finish on the plain dashboard stranded the custodian first-run flow (memory import, channels, permissions, hatch). Fresh activations now hand off to custodian onboarding; live-verified pre-existing setups reopen the normal dashboard, matching the removed already-configured shortcut. Tests pin the destination per path. Also isolate the post-startup Codex login test from developer machines: ambient OPENAI_API_KEY and a real Codex login made it assert-fail. --------- Co-authored-by: Peter Steinberger <steipete@gmail.com>
OpenClaw Codex
Official OpenClaw plugin for OpenAI Codex app-server integration. It exposes the Codex-managed GPT model catalog, the Codex runtime surfaces used by OpenClaw agents, and opt-in supervision of native Codex sessions.
Install from OpenClaw:
openclaw plugins install @openclaw/codex
Use this plugin when you want OpenClaw to run Codex-backed model turns, media understanding, and prompt overlays through the Codex app-server harness, or to browse non-archived Codex CLI, VS Code, Atlas, and ChatGPT sessions and paginated transcripts across paired computers.
Guided onboarding attempts to install and enable supervision after it detects a native Codex installation and the selected inference backend passes its live check; Codex does not need to be the primary backend. Supervision activates when that opportunistic plugin setup succeeds. App Server availability is checked when supervision connects. An explicit Codex plugin disable, plugin-policy block, or supervision.enabled: false prevents opportunistic enablement. Manual setups enable plugins.entries.codex.config.supervision.enabled. Without explicit App Server connection settings, supervision uses a managed user-home stdio connection; explicit appServer settings are honored.
The Gateway-backed operator CLI is:
openclaw codex sessions [--search <text>] [--host <id>] [--limit <count>] [--cursor <cursor>] [--json] [--url <url>] [--token <token>] [--timeout <ms>] [--expect-final]
openclaw codex continue <thread-id> [--json] [--url <url>] [--token <token>] [--timeout <ms>] [--expect-final]
openclaw codex archive <thread-id> --confirm-no-other-runner [--json] [--url <url>] [--token <token>] [--timeout <ms>] [--expect-final]
The catalog never includes archived threads and has no archived or include-archived option. Rows appear in the normal Control UI sessions sidebar and open in the normal Chat pane. Transcript history requires a recent Codex App Server with thread/turns/list and is fetched 20 full-item turns at a time through opaque cursors; OpenClaw does not fall back to an unbounded thread/read, and rejects a serialized transcript page above 20 MiB before transport. --limit defaults to 50 sessions per host, --cursor requires --host, and the sessions Gateway timeout defaults to 75,000 ms so cold paired-node catalogs can complete. Continue and archive retain the shared 30,000 ms default. All operator surfaces require operator.write. Paired-node rows can be listed and read; continue and archive operate only on the Gateway-local host, and archive requires the no-other-runner confirmation. Catalog registration does not require supervision.enabled; that setting gates agent-facing supervision tools.
A supervised OpenClaw Chat cannot be deleted while its model-selection lock protects the native binding. Before native archive, OpenClaw checks the exact target and every non-archived spawned descendant reported by Codex; any active OpenClaw binding blocks the operation. Descendant pagination errors, cycles, and safety-limit exhaustion also fail closed. Codex still does not expose a conditional archive operation or cross-process runner lease, so the confirmation covers unknown native clients and the race between the status read and archive request.
Disabling or uninstalling the plugin leaves supervised Chats locked and unavailable rather than rerouting them. Reinstall or re-enable the same plugin and restart the Gateway to resume those Chats.
These shell commands differ from the in-chat /codex runtime commands. In particular, /codex sessions --host <node> lists Codex CLI session files on one node, /codex threads uses the current conversation's App Server connection, and /codex resume or /codex bind changes that conversation's binding. There is no /codex archive runtime command.
Native Codex plugin catalogs are discoverable with /codex plugins available, including repository marketplaces declared in .agents/plugins/marketplace.json in the bound workspace. An owner or operator.admin can install and authorize an exact plugin with /codex plugins install <plugin>@<marketplace>. The owner-scoped codex_plugins agent tool only reads marketplace metadata; installation and policy changes stay on authenticated /codex management commands. Explicitly installing a plugin trusts its skills, apps, MCP servers, and hooks.
For a supervised branch, Codex App Server selects the snapshot fork's model and provider from its current native configuration. OpenClaw starts the canonical harness thread with exactly that returned pair. Codex persists the canonical thread's native selection, and later resumes preserve it because OpenClaw omits model and provider overrides. OpenClaw cannot substitute its outer runtime, model, or fallback. The returned initial pair can differ from the source's last recorded model.
The visible-history mirror keeps at most 200 user or assistant messages, 512 KiB total, and 64 KiB per message. Image inputs become [Image attachment]; image data and local paths are not copied.
See the Codex harness and Codex supervision guides.