provider-codexlisted

Track and maintain the upstream OpenAI Codex CLI contract. Use when OpenAI ships a Codex release, when a `codex exec` flag/sandbox/approval/resume behaviour changes, or when an upstream scan flags drift. Process guidance only — `src/upstream-contracts.ts` is the mechanical source of truth.
verivus-oss/llm-cli-gateway · ★ 8 · AI & Automation · score 78

Install: claude install-skill verivus-oss/llm-cli-gateway

# Provider: OpenAI Codex CLI Process guidance for keeping the gateway's Codex (`codex`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour — the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.codex` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, sandbox/approval modes, or resume rules here or in TOML. ## Identity | Field | Value | |-------|-------| | CliType | `codex` | | Executable | `codex` | | Package | `@openai/codex` (npm) | | Repo | https://github.com/openai/codex | | Releases | https://github.com/openai/codex/releases | | Changelog | https://developers.openai.com/codex/changelog | | Watch categories | `flags`, `sandbox-modes`, `approval-modes`, `session-resume`, `output-schema` | These values mirror `UPSTREAM_CLI_CONTRACTS.codex.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.codex]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - An OpenAI Codex CLI release lands and you need to check for contract drift. - A `codex` request fails the upstream contract check before spawn. - `npm run upstream:scan -- --live` reports a change on the Codex release notes or changelog. ## Scan for upstream change ```bash npm run upstream:scan -- --provider codex npm run upstream:scan -- --live --provider codex --fail-on-critical npm run upstream:scan -- --live --provider codex --w