79 Commits

• [codex] Remove unused legacy shell tools (#22246)

  ## Why
  
  Recent session history showed no active use of the raw `shell`,
  `local_shell`, or `container.exec` execution surfaces. Keeping those
  handlers/specs wired into core leaves duplicate shell execution paths
  alongside the supported `shell_command` and unified exec tools.
  
  ## What changed
  
  - Removed the raw `shell` handler/spec and its `ShellToolCallParams`
  protocol helper.
  - Removed the legacy `local_shell` and `container.exec` handler/spec
  plumbing while preserving persisted-history compatibility for old
  response items.
  - Normalized model/config `default` and `local` shell selections to
  `shell_command`.
  - Pruned tests that exercised removed raw-shell/local-shell/apply-patch
  variants and kept coverage on `shell_command`, unified exec, and
  freeform `apply_patch`.
  
  ## Verification
  
  - `git diff --check`
  - `cargo test -p codex-protocol`
  - `cargo test -p codex-tools`
  - `cargo test -p codex-core tools::handlers::shell`
  - `cargo test -p codex-core tools::spec`
  - `cargo test -p codex-core tools::router`
  - `cargo test -p codex-core
  active_call_preserves_triggering_command_context`
  - `cargo test -p codex-core guardian_tests`
  - `cargo test -p codex-core --test all shell_serialization`
  - `cargo test -p codex-core --test all apply_patch_cli`
  - `cargo test -p codex-core --test all shell_command_`
  - `cargo test -p codex-core --test all local_shell`
  - `cargo test -p codex-core --test all otel::`
  - `cargo test -p codex-core --test all hooks::`
  - `just fix -p codex-core`
  - `just fix -p codex-tools`

  pakrym-oai · 2026-05-13 16:43:25 +00:00
  83decfa300
• fix: prevent fmt from updating Python SDK lockfile (#22505)

  ## Why
  
  `just fmt` should align source formatting without resolving dependencies
  or rewriting lockfiles. The Python SDK formatting steps run through
  `uv`, so differing local `uv` versions could decide the SDK lock was
  stale and mutate `sdk/python/uv.lock` before Ruff ran.
  
  ## What
  
  - Add `--frozen` to both Python SDK `uv run ... ruff` commands in the
  root `fmt` recipe.
  - Update the existing Python SDK artifact workflow guard test so future
  changes keep the formatter recipe non-lock-mutating.
  
  ## Verification
  
  - `uv run --frozen --project ../sdk/python --extra dev pytest
  ../sdk/python/tests/test_artifact_workflow_and_binaries.py -q`

  jif-oai · 2026-05-13 17:58:08 +02:00
  382404db99
• fix: uv lock (#22323)

  Update the lock of UV

  jif-oai · 2026-05-12 16:24:54 +02:00
  89c8e9a4db
• [8/8] Add Python SDK Ruff formatting (#22021)

  ## Why
  
  The Python SDK needs the same tight formatter/lint loop as the rest of
  the repo: a safe Ruff autofix pass, Ruff formatting, editor save
  behavior, and CI checks that catch drift. Without that loop, SDK changes
  can land with formatting or import ordering that differs from what
  reviewers and CI expect.
  
  ## What
  
  - Add Ruff configuration to `sdk/python/pyproject.toml`, excluding
  generated protocol code and notebooks from the normal lint/format pass.
  - Update `just fmt` so it still formats Rust and also runs Python SDK
  Ruff autofix and formatting.
  - Add Python SDK CI steps for `ruff check` and `ruff format --check`
  before pytest.
  - Recommend the Ruff VS Code extension and enable Python
  format/fix/organize-on-save so Cmd+S uses the same tooling.
  - Apply the resulting Ruff formatting to SDK Python files, examples, and
  the checked-in generated `v2_all.py` output emitted by the pinned
  generator.
  - Add a guard test for the `just fmt` recipe so it keeps working from
  both Rust and Python SDK working directories.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. This PR `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added `test_root_fmt_recipe_formats_rust_and_python_sdk` for the
  shared format recipe.
  - Ran `just fmt` after the recipe update.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 01:10:29 +03:00
  aa9e8f0262
• [7/8] Add Python SDK app-server integration harness (#22014)

  ## Why
  
  The SDK had behavioral tests that replaced SDK client internals. Those
  tests could catch wrapper mistakes, but they did not prove the pinned
  app-server runtime, generated notification models, request routing, and
  sync/async public clients worked together.
  
  This PR adds deterministic integration coverage that starts the pinned
  `codex app-server` process and mocks only the upstream Responses HTTP
  boundary.
  
  ## What
  
  - Add `AppServerHarness` and `MockResponsesServer` helpers for isolated
  `CODEX_HOME`, mock-provider config, queued SSE responses, and captured
  `/v1/responses` requests.
  - Add shared helpers for SSE construction, stream assertions,
  approval-policy inspection, and image fixtures.
  - Split integration coverage into focused modules for run behavior,
  inputs, streaming, turn controls, approvals, and thread lifecycle.
  - Cover sync and async `Thread.run`, `TurnHandle.stream`, interleaved
  streams, approval-mode persistence, lifecycle helpers, final-answer
  phase handling, image inputs, loaded skill input injection, steering,
  interruption, listing, history reads, run overrides, and token usage
  mapping.
  - Replace public-wrapper tests that duplicated integration-test behavior
  with lower-level client tests only where direct client behavior is the
  thing under test.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. This PR `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added pinned app-server integration tests under
  `sdk/python/tests/test_app_server_*.py` and
  `test_real_app_server_integration.py`.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 01:06:41 +03:00
  3e10e09e24
• [6/8] Add high-level Python SDK approval mode (#21910)

  ## Why
  
  The high-level SDK should expose the approval behavior it actually
  supports instead of leaking generated app-server routing fields. New
  work should have two clear choices: default auto review, or explicitly
  deny escalated permission requests. Existing threads and subsequent
  turns should preserve their current approval behavior unless the caller
  passes an override.
  
  ## What
  
  - Add the public `ApprovalMode` enum with `auto_review` and `deny_all`.
  - Default new thread creation to `ApprovalMode.auto_review`.
  - Preserve existing approval settings by default for resume, fork, run,
  and turn helpers.
  - Remove raw `approval_policy` / `approvals_reviewer` kwargs from
  high-level SDK wrappers.
  - Update generated wrapper output, docs, examples, notebooks, and tests
  for the high-level approval mode API.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. This PR `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added approval-mode mapping/default tests for new threads, existing
  threads, forks, resumes, and subsequent turns.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 01:02:43 +03:00
  2b90c37069
• [5/8] Rename Python SDK package to openai-codex (#21905)

  ## Why
  
  The SDK should publish under the reserved public distribution name
  `openai-codex`, and its import module should match that name in the
  Python style. Since package names can contain hyphens but import modules
  cannot, the public import path becomes `openai_codex`.
  
  Keeping the rename separate from the public API surface change makes the
  naming change easy to review and avoids mixing it with API curation.
  
  ## What
  
  - Rename the SDK distribution from `openai-codex-app-server-sdk` to
  `openai-codex`.
  - Rename the import package from `codex_app_server` to `openai_codex`.
  - Keep the runtime wheel as the separate `openai-codex-cli-bin`
  dependency.
  - Update docs, examples, notebooks, artifact scripts, lockfile metadata,
  and tests for the new distribution/module names.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. This PR `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Updated package metadata and public API tests to assert the
  distribution and import names.
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 00:59:25 +03:00
  f1b84fac63
• [4/8] Define Python SDK public API surface (#21896)

  ## Why
  
  The SDK package root should be the ergonomic public client API, not a
  dump of every generated app-server schema type. Generated models still
  need a supported import path, but callers should be able to tell which
  names are high-level SDK entrypoints and which names are protocol value
  models.
  
  ## What
  
  - Define a curated root `__all__` for clients, handles, input helpers,
  retry helpers, config, and public errors.
  - Add a `types` module as the supported home for generated app-server
  response, event, enum, and helper models.
  - Update docs and examples to import protocol/value models from the type
  module.
  - Add tests that lock root exports, type-module exports, star-import
  behavior, and example import hygiene.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. This PR `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added public API signature tests for root exports, `types` exports,
  and example imports.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 00:57:44 +03:00
  b4bc02439f
• [2/8] Generate Python SDK types from pinned runtime (#21893)

  ## Why
  
  Once the SDK declares its runtime package, generated Python artifacts
  should come from that pinned runtime rather than whatever app-server
  schema happens to be in the current checkout. That keeps the generated
  API and model surface aligned with the runtime users install.
  
  ## What
  
  - Teach `scripts/update_sdk_artifacts.py generate-types` to invoke the
  pinned runtime package for schema generation.
  - Regenerate `v2_all.py`, `notification_registry.py`, and generated
  public wrapper methods from that schema.
  - Add freshness coverage so regenerating from the pinned runtime must
  leave checked-in artifacts unchanged.
  
  ## Stack
  
  1. #21891 `[1/8]` Pin Python SDK runtime dependency
  2. This PR `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added `test_generated_files_are_up_to_date` for pinned-runtime
  generation drift.
  - Added generator-structure tests for schema annotation and notification
  metadata generation.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 00:53:21 +03:00
  6a4653efc8
• [1/8] Pin Python SDK runtime dependency (#21891)

  ## Why
  
  The Python SDK depends on the app-server runtime package for the bundled
  `codex` binary and schema source of truth. That relationship should be
  explicit in package metadata instead of inferred from matching version
  numbers, so installers, lockfiles, and reviewers can see exactly which
  runtime the SDK expects.
  
  ## What
  
  - Declare `openai-codex-cli-bin==0.131.0a4` as a Python SDK dependency.
  - Update runtime setup helpers to resolve the runtime version from the
  declared dependency pin.
  - Refresh the SDK lockfile for the pinned runtime wheel.
  - Update package/runtime tests and docs that describe where the runtime
  version comes from.
  
  ## Stack
  
  1. This PR `[1/8]` Pin Python SDK runtime dependency
  2. #21893 `[2/8]` Generate Python SDK types from pinned runtime
  3. #21895 `[3/8]` Run Python SDK tests in CI
  4. #21896 `[4/8]` Define Python SDK public API surface
  5. #21905 `[5/8]` Rename Python SDK package to `openai-codex`
  6. #21910 `[6/8]` Add high-level Python SDK approval mode
  7. #22014 `[7/8]` Add Python SDK app-server integration harness
  8. #22021 `[8/8]` Add Python SDK Ruff formatting
  
  ## Verification
  
  - Added coverage for the SDK runtime dependency pin and runtime
  distribution naming.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-12 00:42:26 +03:00
  5fe33443b0
• Route Python SDK turn notifications by ID (#21778)

  ## Why
  
  The Python SDK previously protected the stdio transport with a single
  active turn-consumer guard. That avoided competing reads from stdout,
  but it also meant one `Codex`/`AsyncCodex` client could not stream
  multiple active turns at the same time. Notifications could also arrive
  before the caller received a `TurnHandle` and registered for streaming,
  so the SDK needed an explicit routing layer instead of letting
  individual API calls read directly from the shared transport.
  
  ## What Changed
  
  - Added a private `MessageRouter` that owns per-request response queues,
  per-turn notification queues, pending turn-notification replay, and
  global notification delivery behind a single stdout reader thread.
  - Generated typed notification routing metadata so turn IDs come from
  known payload shapes instead of router-side attribute guessing, with
  explicit fallback handling for unknown notification payloads.
  - Updated sync and async turn streaming so `TurnHandle.stream()`/`run()`
  and `stream_text()` consume only notifications for their own turn ID,
  while `AsyncAppServerClient` no longer serializes all transport calls
  behind one async lock.
  - Cleared pending turn-notification buffers when unregistered turns
  complete so never-consumed turn handles do not leave stale queues
  behind.
  - Removed the internal stream-until helper now that turn completion
  waiting can register directly with routed turn notifications.
  - Updated Python SDK docs and focused tests for concurrent transport
  calls, interleaved turn routing, buffered early notifications, unknown
  notification routing, async delegation, and routed turn completion
  behavior.
  
  ## Validation
  
  - `uv run --extra dev ruff format scripts/update_sdk_artifacts.py
  src/codex_app_server/_message_router.py src/codex_app_server/client.py
  src/codex_app_server/generated/notification_registry.py
  tests/test_client_rpc_methods.py
  tests/test_public_api_runtime_behavior.py
  tests/test_async_client_behavior.py`
  - `uv run --extra dev ruff check scripts/update_sdk_artifacts.py
  src/codex_app_server/_message_router.py src/codex_app_server/client.py
  src/codex_app_server/generated/notification_registry.py
  tests/test_client_rpc_methods.py
  tests/test_public_api_runtime_behavior.py
  tests/test_async_client_behavior.py`
  - `uv run --extra dev pytest tests/test_client_rpc_methods.py
  tests/test_public_api_runtime_behavior.py
  tests/test_async_client_behavior.py`
  - `git diff --check`
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-09 04:16:23 +00:00
  ebe75bb683
• Revert "Publish Python runtime wheels on release" (#21810)

  Reverts openai/codex#21784

  Ahmed Ibrahim · 2026-05-08 22:37:10 +03:00
  cf941ede15
• Publish Python runtime wheels on release (#21784)

  ## Why
  
  Published Python SDK builds depend on an exact `openai-codex-cli-bin`
  runtime package, but the release workflow did not publish that runtime
  package to PyPI. That left the SDK packaging story incomplete: release
  artifacts could produce Codex binaries, but Python users still needed a
  matching wheel carrying the platform-specific runtime and helper
  executables.
  
  This PR is stacked on #21787 so release jobs can include helper binaries
  in runtime wheels: Linux wheels include `bwrap` for sandbox fallback,
  and Windows wheels include the signed sandbox/elevation helpers beside
  `codex.exe`.
  
  ## What changed
  
  - Builds platform-specific `openai-codex-cli-bin` wheels from signed
  release binaries on macOS, Linux, and Windows release runners.
  - Packages Linux `bwrap` into musllinux runtime wheels.
  - Packages Windows sandbox helper executables into Windows runtime
  wheels.
  - Uploads runtime wheels as GitHub release assets and publishes them to
  PyPI using trusted publishing from the `pypi` GitHub environment.
  - Keeps the new Python runtime publish job non-blocking so failures need
  follow-up but do not fail the Rust release workflow.
  - Pins the PyPA publish action to the `v1.13.0` commit SHA for
  reproducible release publishing.
  - Documents that runtime wheels are platform wheels published through
  PyPI trusted publishing.
  
  ## Testing
  
  - `ruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f); puts "ok
  #{f}" }' .github/workflows/rust-release.yml
  .github/workflows/rust-release-windows.yml`
  - `git diff --check`
  
  CI is the real end-to-end verification for the release workflow path.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-08 22:00:58 +03:00
  9183503b97
• Support resource binaries in Python runtime staging (#21787)

  ## Why
  
  Some Codex runtime distributions need helper executables beside the main
  bundled binary. Linux sandbox fallback needs a packaged `bwrap` when no
  suitable system `bwrap` is available, and Windows sandbox/elevation
  needs helper executables discoverable beside `codex.exe`. The checked-in
  `openai-codex-cli-bin` template already packages everything under
  `codex_cli_bin/bin/**`, but the staging script only copied the main
  Codex binary into that directory.
  
  This PR adds the generic staging primitive needed by release workflows
  to build complete platform runtime wheels without baking
  platform-specific helper names into the package template.
  
  ## What changed
  
  - Added repeatable `stage-runtime --resource-binary` support so release
  workflows can copy extra executables beside the bundled Codex binary.
  - Kept resource selection in workflow code, where the platform target is
  known.
  - Added tests that verify resource binaries are copied into the staged
  runtime package, that the wheel include config covers them, and that the
  CLI forwards repeated `--resource-binary` values.
  
  ## Testing
  
  - `uv run ruff check scripts/update_sdk_artifacts.py
  tests/test_artifact_workflow_and_binaries.py`
  - `uv run --extra dev pytest
  tests/test_artifact_workflow_and_binaries.py::test_stage_runtime_release_copies_resource_binaries
  tests/test_artifact_workflow_and_binaries.py::test_runtime_resource_binaries_are_included_by_wheel_config
  tests/test_artifact_workflow_and_binaries.py::test_stage_runtime_stages_binary_without_type_generation`
  
  Full `tests/test_artifact_workflow_and_binaries.py` still has unrelated
  schema-normalization drift in the local checkout.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-05-08 22:00:44 +03:00
  8956a928a1
• Add remote plugin skill read API (#20150)

  ## Summary
  
  Adds an app-server `plugin/skill/read` method for remote plugin skill
  markdown. The new method calls the plugin-service skill detail endpoint
  and returns `skill_md_contents`, so clients can preview skills for
  remote plugins before the bundle is installed locally.
  
  ## Why
  
  Uninstalled remote plugin skills do not have local `SKILL.md` files.
  Without an on-demand remote read, the desktop plugin details UI cannot
  render the skill details modal for those skills.
  
  ## Validation
  
  - `just write-app-server-schema`
  - `just fmt`
  - `cargo test -p codex-app-server-protocol`
  - `cargo test -p codex-app-server --test all --
  suite::v2::plugin_read::plugin_skill_read_reads_remote_skill_contents_when_remote_plugin_enabled
  --exact`
  - `just fix -p codex-app-server-protocol -p codex-core-plugins -p
  codex-app-server`

  xli-oai · 2026-05-01 00:16:25 -07:00
  96d2ea9058
• Publish Python SDK with Codex-pinned versioning (#18996)

  **note**: a large chunk of this diff comes from regenerating Python
  types after app-server schema changes on `main`.
  
  This is PR 3 of 3 for the Python SDK PyPI publishing split. PR #18862
  refreshed the generated SDK surface, and PR #18865 made the runtime
  package publishable as `openai-codex-cli-bin`; this final PR makes the
  SDK package publishable as `openai-codex-app-server-sdk` and pins both
  packages to the same Codex runtime version.
  
  The key idea is that the published SDK version is the Codex runtime
  version. That one version now drives the SDK package version, the exact
  runtime dependency, the client version reported by the SDK, and the
  bootstrap runtime pin. This keeps release-time versioning in one lane
  instead of scattering checked-in literals through the package.
  
  ## What changed
  
  - Rename the SDK distribution from `codex-app-server-sdk` to
  `openai-codex-app-server-sdk` for conflict-free PyPI publishing.
  - Use `stage-sdk --codex-version ...` with one Codex version for both
  the SDK package version and exact `openai-codex-cli-bin` dependency.
  - Preserve hidden legacy `--runtime-version` / `--sdk-version` args only
  to reject mismatched versions during staging.
  - Map PEP 440 package versions back to Codex release tags for runtime
  setup downloads, e.g. `0.116.0a1` -> `rust-v0.116.0-alpha.1`.
  - Derive `codex_app_server.__version__`, the default
  `AppServerConfig.client_version`, and
  `_runtime_setup.pinned_runtime_version()` from the SDK package/project
  version instead of hardcoding duplicate version strings.
  - Carry the current generated SDK refresh from `main` so
  `generate-types` stays clean after recent app-server schema changes.
  - Update `sdk/python/uv.lock` for the renamed editable package.
  
  ## Validation
  
  - `uv run --extra dev pytest` in `sdk/python` -> 59 passed, 37 skipped.
  - Targeted `uv run ruff check` for the touched SDK files.
  - `git diff --check`.
  - Staged runtime with `--codex-version rust-v0.116.0-alpha.1
  --platform-tag macosx_11_0_arm64`.
  - Staged SDK with `--codex-version rust-v0.116.0-alpha.1`.
  - Built runtime wheel, SDK wheel, and SDK sdist.
  - `twine check /tmp/codex-python-pr3-build/dist/*` -> passed.
  - Clean venv smoke installed `openai-codex-app-server-sdk==0.116.0a1`
  from local dist and pulled `openai-codex-cli-bin==0.116.0a1`.
  - Smoke imports passed for `Codex` and `bundled_codex_path()`.

  Steve Coffey · 2026-04-27 14:28:46 -07:00
  0f40261e86
• Harden package-manager install policy (#19163)

  ## Summary
  
  This PR hardens package-manager usage across the repo to reduce
  dependency supply-chain risk. It also removes the stale `codex-cli`
  Docker path, which was already broken on `main`, instead of keeping a
  bitrotted container workflow alive.
  
  ## What changed
  
  - Updated pnpm package manager pins and workspace install settings.
  - Removed stale `codex-cli` Docker assets instead of trying to keep a
  broken local container path alive.
  - Added uv settings and lockfiles for the Python SDK packages.
  - Updated Python SDK setup docs to use `uv sync`.
  
  ## Why
  
  This is primarily a security hardening change. It reduces
  package-install and supply-chain risk by ensuring dependency installs go
  through pinned package managers, committed lockfiles, release-age
  settings, and reviewed build-script controls.
  
  For `codex-cli`, the right follow-up was to remove the local Docker path
  rather than keep patching it:
  
  - `codex-cli/Dockerfile` installed `codex.tgz` with `npm install -g`,
  which bypassed the repo lockfile and age-gated pnpm settings.
  - The local `codex-cli/scripts/build_container.sh` helper was already
  broken on `main`: it called `pnpm run build`, but
  `codex-cli/package.json` does not define a `build` script.
  - The container path itself had bitrotted enough that keeping it would
  require extra packaging-specific behavior that was not otherwise needed
  by the repo.
  
  ## Gaps addressed
  
  - Global npm installs bypassed the repo lockfile in Docker and CLI
  reinstall paths, including `codex-cli/Dockerfile` and
  `codex-cli/bin/codex.js`.
  - CI and Docker pnpm installs used `--frozen-lockfile`, but the repo was
  missing stricter pnpm workspace settings for dependency build scripts.
  - Python SDK projects had `pyproject.toml` metadata but no committed
  `uv.lock` coverage or uv age/index settings in `sdk/python` and
  `sdk/python-runtime`.
  - The secure devcontainer install path used npm/global install behavior
  without a local locked package-manager boundary.
  - The local `codex-cli` Docker helper was already broken on `main`, so
  this PR removes that stale Docker path instead of preserving a broken
  surface.
  - pnpm was already pinned, but not to the current repo-wide pnpm version
  target.
  
  ## Verification
  
  - `pnpm install --frozen-lockfile`
  - `.devcontainer/codex-install`: `pnpm install --prod --frozen-lockfile`
  - `.devcontainer/codex-install`: `./node_modules/.bin/codex --version`
  - `sdk/python`: `uv lock --check`, `uv sync --locked --all-extras
  --dry-run`, `uv build`
  - `sdk/python-runtime`: `uv lock --check`, `uv sync --locked --dry-run`,
  `uv build --wheel`
  - `pnpm -r --filter ./sdk/typescript run build`
  - `pnpm -r --filter ./sdk/typescript run lint`
  - `pnpm -r --filter ./sdk/typescript run test`
  - `node --check codex-cli/bin/codex.js`
  - `docker build -f .devcontainer/Dockerfile.secure -t codex-secure-test
  .`
  - `cargo build -p codex-cli`
  - repo-wide package-manager audit

  mcgrew-oai · 2026-04-24 14:36:19 -04:00
  dee5f5ea38
• Surface reasoning tokens in exec JSON usage (#19308)

  ## Summary
  
  Fixes #19022.
  
  `codex exec --json` currently emits `turn.completed.usage` with input,
  cached input, and output token counts, but drops the reasoning-token
  split that Codex already receives through thread token usage updates.
  Programmatic consumers that rely on the JSON stream, especially
  ephemeral runs that do not write rollout files, need this field to
  accurately display reasoning-model usage.
  
  This PR adds `reasoning_output_tokens` to the public exec JSON `Usage`
  payload and maps it from the existing `ThreadTokenUsageUpdated` total
  token usage data.
  
  ## Verification
  
  - Added coverage to
  `event_processor_with_json_output::token_usage_update_is_emitted_on_turn_completion`
  so `turn.completed.usage.reasoning_output_tokens` is asserted.
  - Updated SDK expectations for `run()` and `runStreamed()` so TypeScript
  consumers see the new usage field.
  - Ran `cargo test -p codex-exec`.
  - Ran `pnpm --filter ./sdk/typescript run build`.
  - Ran `pnpm --filter ./sdk/typescript run lint`.
  - Ran `pnpm --filter ./sdk/typescript exec jest --runInBand
  --testTimeout=30000`.

  Eric Traut · 2026-04-24 01:54:11 -07:00
  ddfa691752
• Fix auto-review config compatibility across protocol and SDK (#19113)

  ## Why
  
  This keeps the partial Guardian subagent -> Auto-review rename
  forward-compatible across mixed Codex installations. Newer binaries need
  to understand the new `auto_review` spelling, but they cannot write it
  to shared `~/.codex/config.toml` yet because older CLI/app-server
  bundles only know `user` and `guardian_subagent` and can fail during
  config load before recovering.
  
  The Python SDK had the opposite compatibility gap: app-server responses
  can contain `approvalsReviewer: "auto_review"`, but the checked-in
  generated SDK enum did not accept that value.
  
  ## What Changed
  
  - Keep `ApprovalsReviewer::AutoReview` readable from both
  `guardian_subagent` and `auto_review`, while serializing it as
  `guardian_subagent` in both protocol crates.
  - Update TUI Auto-review persistence tests so enabling Auto-review
  writes `approvals_reviewer = "guardian_subagent"` while UI copy still
  says Auto-review.
  - Map managed/cloud `feature_requirements.auto_review` to the existing
  `Feature::GuardianApproval` gate without adding a broad local
  `[features].auto_review` key or changing config writes.
  - Add `auto_review` to the Python SDK `ApprovalsReviewer` enum and cover
  `ThreadResumeResponse` validation.
  
  ## Testing
  
  - `cargo test -p codex-protocol approvals_reviewer`
  - `cargo test -p codex-app-server-protocol approvals_reviewer`
  - `cargo test -p codex-tui
  update_feature_flags_enabling_guardian_selects_auto_review`
  - `cargo test -p codex-tui
  update_feature_flags_enabling_guardian_in_profile_sets_profile_auto_review_policy`
  - `cargo test -p codex-core
  feature_requirements_auto_review_disables_guardian_approval`
  - `pytest
  sdk/python/tests/test_client_rpc_methods.py::test_thread_resume_response_accepts_auto_review_reviewer`
  - `git diff --check`

  Won Park · 2026-04-23 03:12:56 -07:00
  17ae906048
• Stage publishable Python runtime wheels (#18865)

  This is PR 2 of the Python SDK PyPI publishing split. [PR
  1](https://github.com/openai/codex/pull/18862) refreshed the generated
  SDK bindings; this PR makes the runtime package itself publishable, and
  PR 3 will wire the SDK package/version pinning to this runtime package.
  
  ## Summary
  - Rename the runtime distribution to `openai-codex-cli-bin` while
  keeping the import package as `codex_cli_bin`.
  - Make the runtime package wheel-only and build `py3-none-<platform>`
  wheels instead of interpreter-specific wheels.
  - Add `stage-runtime --codex-version` and `--platform-tag` so release
  staging can produce the platform wheel matrix from Codex release tags.
  - Add focused artifact workflow tests for version normalization,
  platform tag injection, and runtime wheel metadata.
  
  ## Why Rename
  There is already an unofficial PyPI package,
  [`codex-bin`](https://pypi.org/project/codex-bin/), distributing OpenAI
  Codex binaries. Publishing the official SDK runtime dependency as
  `openai-codex-cli-bin` makes the ownership clear, avoids confusing the
  SDK-pinned runtime wheel with that unowned wrapper, and keeps the import
  package unchanged as `codex_cli_bin`.
  
  ## Tests
  - `uv run --extra dev pytest
  tests/test_artifact_workflow_and_binaries.py` -> 21 passed
  - `uv run --extra dev python scripts/update_sdk_artifacts.py
  stage-runtime /tmp/codex-python-pr2-rebased/runtime-stage
  /tmp/codex-python-pr2-rebased/codex --codex-version
  rust-v0.116.0-alpha.1 --platform-tag macosx_11_0_arm64`
  - `uv run --with build --extra dev python -m build --wheel
  /tmp/codex-python-pr2-rebased/runtime-stage`
  - `uv run --with twine --extra dev twine check
  /tmp/codex-python-pr2-rebased/runtime-stage/dist/openai_codex_cli_bin-0.116.0a1-py3-none-macosx_11_0_arm64.whl`
  
  ## Note
  - Full `uv run --extra dev pytest` currently fails because regenerating
  from schemas already on `main` adds new DeviceKey Python types. I left
  that generated catch-up out of this runtime-only PR.

  Steve Coffey · 2026-04-22 08:14:48 -07:00
  0127cef5db
• Refresh generated Python app-server SDK types (#18862)

  This is the first step in splitting the Python SDK PyPI publish work
  into reviewable layers: land the generated SDK refresh by itself before
  changing packaging mechanics. The next PRs will make the runtime wheel
  publishable, then wire the SDK package/version pinning to that runtime.
  
  ## Summary
  - Refresh generated Python app-server v2 models and notification
  registry from the current schema.
  - Update the public API signature expectations for the newly generated
  kwargs.
  
  ## Stack
  - PR 1 of 3 for the Python SDK PyPI publishing split.
  - Follow-up PRs will handle runtime wheel publishing mechanics, then
  SDK/package version pinning.
  
  ## Tests
  - `uv run --extra dev pytest` in `sdk/python` -> 51 passed, 37 skipped.

  Steve Coffey · 2026-04-21 10:23:27 -07:00
  38ba876ea9
• Remove OPENAI_BASE_URL config fallback (#16720)

  The `OPENAI_BASE_URL` environment variable has been a significant
  support issue, so we decided to deprecate it in favor of an
  `openai_base_url` config key. We've had the deprecation warning in place
  for about a month, so users have had time to migrate to the new
  mechanism. This PR removes support for `OPENAI_BASE_URL` entirely.

  Eric Traut · 2026-04-03 15:03:21 -07:00
  4b8bab6ad3
• ci: run SDK tests with a Bazel-built codex (#16046)

  ## Why
  
  Before this change, the SDK CI job built `codex` with Cargo before
  running the TypeScript package tests. That step has been getting more
  expensive as the Rust workspace grows, while the repo already has a
  Bazel-backed build path for the CLI.
  
  The SDK tests also need a normal executable path they can spawn
  repeatedly. Moving the job to Bazel exposed an extra CI detail: a plain
  `bazel-bin/...` lookup is not reliable under the Linux config because
  top-level outputs may stay remote and the wrapper emits status lines
  around `cquery` output.
  
  ## What Changed
  
  - taught `sdk/typescript/tests/testCodex.ts` to honor `CODEX_EXEC_PATH`
  before falling back to the local Cargo-style `target/debug/codex` path
  - added `--remote-download-toplevel` to
  `.github/scripts/run-bazel-ci.sh` so workflows can force Bazel to
  materialize top-level outputs on disk after a build
  - switched `.github/workflows/sdk.yml` from `cargo build --bin codex` to
  the shared Bazel CI setup and `//codex-rs/cli:codex` build target
  - changed the SDK workflow to resolve the built CLI with wrapper-backed
  `cquery --output=files`, stage the binary into
  `${GITHUB_WORKSPACE}/.tmp/sdk-ci/codex`, and point the SDK tests at that
  path via `CODEX_EXEC_PATH`
  - kept the warm-up step before Jest and the Bazel repository-cache save
  step
  
  ## Verification
  
  - `bash -n .github/scripts/run-bazel-ci.sh`
  - `./.github/scripts/run-bazel-ci.sh -- cquery --output=files --
  //codex-rs/cli:codex | grep -E '^(/|bazel-out/)' | tail -n 1`
  - `./.github/scripts/run-bazel-ci.sh --remote-download-toplevel -- build
  --build_metadata=TAG_job=sdk -- //codex-rs/cli:codex`
  - `CODEX_EXEC_PATH="$PWD/.tmp/sdk-ci/codex" pnpm --dir sdk/typescript
  test --runInBand`
  - `pnpm --dir sdk/typescript lint`

  Michael Bolin · 2026-03-27 17:17:22 -07:00
  2ffb32db98
• Add usage-based business plan types (#15934)

  ## Summary
  - add `self_serve_business_usage_based` and `enterprise_cbp_usage_based`
  to the public/internal plan enums and regenerate the app-server + Python
  SDK artifacts
  - map both plans through JWT login and backend rate-limit payloads, then
  bucket them with the existing Team/Business entitlement behavior in
  cloud requirements, usage-limit copy, tooltips, and status display
  - keep the earlier display-label remap commit on this branch so the new
  Team-like and Business-like plans render consistently in the UI
  
  ## Testing
  - `just write-app-server-schema`
  - `uv run --project sdk/python python
  sdk/python/scripts/update_sdk_artifacts.py generate-types`
  - `just fix -p codex-protocol -p codex-login -p codex-core -p
  codex-backend-client -p codex-cloud-requirements -p codex-tui -p
  codex-tui-app-server -p codex-backend-openapi-models`
  - `just fmt`
  - `just argument-comment-lint`
  - `cargo test -p codex-protocol
  usage_based_plan_types_use_expected_wire_names`
  - `cargo test -p codex-login usage_based`
  - `cargo test -p codex-backend-client usage_based`
  - `cargo test -p codex-cloud-requirements usage_based`
  - `cargo test -p codex-core usage_limit_reached_error_formats_`
  - `cargo test -p codex-tui plan_type_display_name_remaps_display_labels`
  - `cargo test -p codex-tui remapped`
  - `cargo test -p codex-tui-app-server
  plan_type_display_name_remaps_display_labels`
  - `cargo test -p codex-tui-app-server remapped`
  - `cargo test -p codex-tui-app-server
  preserves_usage_based_plan_type_wire_name`
  
  ## Notes
  - a broader multi-crate `cargo test` run still hits unrelated existing
  guardian-approval config failures in
  `codex-rs/core/src/config/config_tests.rs`

  bwanner-oai · 2026-03-27 14:25:13 -07:00
  82e8031338
• fix: disable plugins in SDK integration tests (#16036)

  ## Why
  
  The TypeScript SDK tests create a fresh `CODEX_HOME` for each Jest case
  and delete it during teardown. That cleanup has been flaking because the
  real `codex` binary can still be doing background curated-plugin startup
  sync under `.tmp/plugins-clone-*`, which races the test harness's
  recursive delete and leaves `ENOTEMPTY` failures behind.
  
  This path is unrelated to what the SDK tests are exercising, so letting
  plugin startup run during these tests only adds nondeterministic
  filesystem activity. This showed up recently in the `sdk` CI lane for
  [#16031](https://github.com/openai/codex/pull/16031).
  
  ## What Changed
  
  - updated `sdk/typescript/tests/testCodex.ts` to merge test config
  through a single helper
  - disabled `features.plugins` unconditionally for SDK integration tests
  so the CLI does not start curated-plugin sync in the temporary
  `CODEX_HOME`
  - preserved other explicit feature overrides from individual tests while
  forcing `plugins` back to `false`
  - kept the existing mock-provider override behavior intact for
  SSE-backed tests
  
  ## Verification
  
  - `pnpm test --runInBand`
  - `pnpm lint`

  Michael Bolin · 2026-03-27 13:04:34 -07:00
  95845cf6ce
• Fix stale quickstart integration assertion (#15677)

  TL;DR: update the quickstart integration assertion to match the current
  example output.
  
  - replace the stale `Status:` expectation for
  `01_quickstart_constructor` with `Server:`, `Items:`, and `Text:`
  - keep the existing guard against `Server: unknown`

  Shaqayeq · 2026-03-24 20:12:52 -07:00
  fece9ce745
• Pin Python SDK app-server stdio to UTF-8 on Windows (#15244)

  ## TL;DR
  Pin the Python app-server SDK subprocess pipes to UTF-8 so Windows users
  on non-UTF-8 locales do not hit `UnicodeDecodeError` when the `codex`
  child emits UTF-8 text.
  
  - add `encoding="utf-8"` to the `subprocess.Popen(...)` call in
  `AppServerClient.start()`
  - add a focused regression test that asserts the client launches the
  subprocess with UTF-8 text I/O
  - validates with `python -m pytest
  sdk/python/tests/test_client_rpc_methods.py
  sdk/python/tests/test_client_process_launch.py
  sdk/python/tests/test_public_api_runtime_behavior.py`
  
  Fixes #14311.

  Shaqayeq · 2026-03-20 18:26:24 +00:00
  9e31aeadce
• Add Python SDK thread.run convenience methods (#15088)

  ## TL;DR
  Add `thread.run(...)` / `async thread.run(...)` convenience methods to
  the Python SDK for the common case.
  
  - add `RunInput = Input | str` and `RunResult` with `final_response`,
  collected `items`, and optional `usage`
  - keep `thread.turn(...)` strict and lower-level for streaming,
  steering, interrupting, and raw generated `Turn` access
  - update Python SDK docs, quickstart examples, and tests for the sync
  and async convenience flows
  
  ## Validation
  - `python3 -m pytest sdk/python/tests/test_public_api_signatures.py
  sdk/python/tests/test_public_api_runtime_behavior.py`
  - `python3 -m pytest
  sdk/python/tests/test_real_app_server_integration.py -k
  'thread_run_convenience or async_thread_run_convenience'` (skipped in
  this environment)
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Shaqayeq · 2026-03-19 00:57:48 +00:00
  4fd2774614
• Revert "fix: harden plugin feature gating" (#15102)

  Reverts openai/codex#15020
  
  I messed up the commit in my PR and accidentally merged changes that
  were still under review.

  xl-openai · 2026-03-18 15:19:29 -07:00
  86982ca1f9
• fix: harden plugin feature gating (#15020)

  1. Use requirement-resolved config.features as the plugin gate.
  2. Guard plugin/list, plugin/read, and related flows behind that gate.
  3. Skip bad marketplace.json files instead of failing the whole list.
  4. Simplify plugin state and caching.

  xl-openai · 2026-03-18 10:11:43 -07:00
  580f32ad2a
• Prefer websockets when providers support them (#13592)

  Remove all flags and model settings.
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  pakrym-oai · 2026-03-17 19:46:44 -07:00
  770616414a
• Add Python SDK public API and examples (#14446)

  ## TL;DR
  WIP esp the examples
  
  Thin the Python SDK public surface so the wrapper layer returns
  canonical app-server generated models directly.
  
  - keeps `Codex` / `AsyncCodex` / `Thread` / `Turn` and input helpers,
  but removes alias-only type layers and custom result models
  - `metadata` now returns `InitializeResponse` and `run()` returns the
  generated app-server `Turn`
  - updates docs, examples, notebook, and tests to use canonical generated
  types and regenerates `v2_all.py` against current schema
  - keeps the pinned runtime-package integration flow and real integration
  coverage
  
    ## Validation
    - `PYTHONPATH=sdk/python/src python3 -m pytest sdk/python/tests`
  - `GH_TOKEN="$(gh auth token)" RUN_REAL_CODEX_TESTS=1
  PYTHONPATH=sdk/python/src python3 -m pytest sdk/python/tests -rs`
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Shaqayeq · 2026-03-17 16:05:56 -07:00
  fc75d07504
• Cleanup skills/remote/xxx endpoints. (#14977)

  Remote skills/remote/xxx as they are not in used for now.

  xl-openai · 2026-03-17 15:22:36 -07:00
  1a9555eda9
• feat: support remote_sync for plugin install/uninstall. (#14878)

  - Added forceRemoteSync to plugin/install and plugin/uninstall.
  - With forceRemoteSync=true, we update the remote plugin status first,
  then apply the local change only if the backend call succeeds.
  - Kept plugin/list(forceRemoteSync=true) as the main recon path, and for
  now it treats remote enabled=false as uninstall. We
  will eventually migrate to plugin/installed for more precise state
  handling.

  xl-openai · 2026-03-16 21:37:27 -07:00
  1d85fe79ed
• Refresh Python SDK generated types (#14646)

  ## Summary
  - regenerate `sdk/python` protocol-derived artifacts on latest
  `origin/main`
  - update `notification_registry.py` to match the regenerated
  notification set
  - fix the stale SDK test expectation for `GranularAskForApproval`
  
  ## Validation
  - `cd sdk/python && python scripts/update_sdk_artifacts.py
  generate-types`
  - `cd sdk/python && python -m pytest`

  sayan-oai · 2026-03-14 05:50:33 +00:00
  8ca358a13c
• Add openai_base_url config override for built-in provider (#12031)

  We regularly get bug reports from users who mistakenly have the
  `OPENAI_BASE_URL` environment variable set. This PR deprecates this
  environment variable in favor of a top-level config key
  `openai_base_url` that is used for the same purpose. By making it a
  config key, it will be more visible to users. It will also participate
  in all of the infrastructure we've added for layered and managed
  configs.
  
  Summary
  - introduce the `openai_base_url` top-level config key, update
  schema/tests, and route the built-in openai provider through it while
  - fall back to deprecated `OPENAI_BASE_URL` env var but warn user of
  deprecation when no `openai_base_url` config key is present
  - update CLI, SDK, and TUI code to prefer the new config path (with a
  deprecated env-var fallback) and document the SDK behavior change

  Eric Traut · 2026-03-13 20:12:25 -06:00
  4b9d5c8c1b
• app-server: Add platform os and family to init response (#14527)

  This allows the client to pick os-specific behavior while interacting
  with the app server, e.g. to use proper path separators.

  Ruslan Nigmatullin · 2026-03-13 19:07:54 +00:00
  50558e6507
• Add Python app-server SDK (#14435)

  ## TL;DR
  Bring the Python app-server SDK from `main-with-prs-13953-and-14232`
  onto current `main` as a standalone SDK-only PR.
  
  - adds the new `sdk/python` and `sdk/python-runtime` package trees
  - keeps the scope to the SDK payload only, without the unrelated
  branch-history or workflow changes from the source branch
  - regenerates `sdk/python/src/codex_app_server/generated/v2_all.py`
  against current `main` schema so the extracted SDK matches today's
  protocol definitions
  
  ## Validation
  - `PYTHONPATH=sdk/python/src python3 -m pytest sdk/python/tests`
  
  Co-authored-by: Codex <noreply@openai.com>

  Shaqayeq · 2026-03-12 09:22:01 -07:00
  ff6764e808
• Update pnpm versions to fix cve-2026-24842 (#12009)

  Update pnpm versions to resolve CVE-2026-24842

  mjr-openai · 2026-02-19 14:27:55 -08:00
  3293538e12
• Make codex-sdk depend on openai/codex (#11503)

  Do not bundle all binaries inside the SDK as it makes the package huge.
  Instead depend on openai/codex

  pakrym-oai · 2026-02-11 16:20:10 -08:00
  703fb38d2a
• fix: ensure resume args precede image args (#10709)

  ## Summary
  Fixes argument ordering when `resumeThread()` is used with
  `local_image`. The SDK previously emitted CLI args with `--image` before
  `resume <threadId>`, which caused the Codex CLI to treat `resume`/UUID
  as image paths and start a new session. This PR moves `resume
  <threadId>` before any `--image` flags and adds a regression test.
  
  ## Bug Report / Links
  - OpenAI issue: https://github.com/openai/codex/issues/10708
  - Repro repo:
  https://github.com/cryptonerdcn/codex-resume-local-image-repro
  - Repro issue (repo):
  https://github.com/cryptonerdcn/codex-resume-local-image-repro/issues/1
  
  ## Repro (pre-fix)
  1. Build SDK from source
  2. Run resume + local_image
  3. Args order: `--image <path> resume <id>`
  4. Result: new session created (thread id changes)
  
  ## Fix
  Move `resume <threadId>` before `--image` in `CodexExec.run` and add a
  regression test to assert ordering.
  
  ## Tests
  - `cd sdk/typescript && npm test`
    - **Failed**: `codex-rs/target/debug/codex` missing (ENOENT)
  
  ## Notes
  - I can rerun tests in an environment with `codex-rs` built and report
  results.

  cryptonerdcn · 2026-02-04 21:19:56 -08:00
  1dc06b6ffc
• Fix minor typos in comments and documentation (#10287)

  ## Summary
  
  I have read the contribution guidelines.  
  All changes in this PR are limited to text corrections and do not modify
  any business logic, runtime behavior, or user-facing functionality.
  
  ## Details
  
  This PR fixes several minor typos, including:
  
  - `create` -> `crate`
  - `analagous` -> `analogous`
  - `apply-patch` -> `apply_patch`
  - `codecs` -> `codex`
  - ` '/" ` -> ` '/' `
  - `Respesent` -> `Represent`

  Ruyut · 2026-01-30 22:11:02 -08:00
  9327e99b28
• fix: remove references to corepack (#10138)

  Currently, our `npm publish` logic is failing.
  
  There were a number of things that were merged recently that seemed to
  contribute to this situation, though I think we have fixed most of them,
  but this one stands out:
  
  https://github.com/openai/codex/pull/10115
  
  As best I can tell, we tried to fix the pnpm version to a specific hash,
  but we did not do it consistently (though `shell-tool-mcp/package.json`
  had it specified twice...), so for this PR, I ran:
  
  ```
  $ git ls-files | grep package.json
  codex-cli/package.json
  codex-rs/responses-api-proxy/npm/package.json
  package.json
  sdk/typescript/package.json
  shell-tool-mcp/package.json
  ```
  
  and ensured that all of them now have this line:
  
  ```json
    "packageManager": "pnpm@10.28.2+sha512.41872f037ad22f7348e3b1debbaf7e867cfd448f2726d9cf74c08f19507c31d2c8e7a11525b983febc2df640b5438dee6023ebb1f84ed43cc2d654d2bc326264"
  ```
  
  I also went and deleted all of the `corepack` stuff that was added by
  https://github.com/openai/codex/pull/10115.
  
  If someone can explain why we need it and verify it does not break `npm
  publish`, then we can bring it back.

  Michael Bolin · 2026-01-28 23:31:25 -08:00
  4d9ae3a298
• feat: make it possible to specify --config flags in the SDK (#10003)

  Updates the `CodexOptions` passed to the `Codex()` constructor in the
  SDK to support a `config` property that is a map of configuration data
  that will be transformed into `--config` flags passed to the invocation
  of `codex`.
  
  Therefore, something like this:
  
  ```typescript
  const codex = new Codex({
    config: {
      show_raw_agent_reasoning: true,
      sandbox_workspace_write: { network_access: true },
    },
  });
  ```
  
  would result in the following args being added to the invocation of
  `codex`:
  
  ```shell
  --config show_raw_agent_reasoning=true --config sandbox_workspace_write.network_access=true
  ```

  Michael Bolin · 2026-01-27 10:47:07 -08:00
  894923ed5d
• add WebSearchMode enum (#9216)

  ### What
  Add `WebSearchMode` enum (disabled, cached live, defaults to cached) to
  config + V2 protocol. This enum takes precedence over legacy flags:
  `web_search_cached`, `web_search_request`, and `tools.web_search`.
  
  Keep `--search` as live.
  
  ### Tests
  Added tests

  sayan-oai · 2026-01-14 12:51:42 -08:00
  5e426ac270
• fix: handle early codex exec exit (#8825)

  Fixes CodexExec to avoid missing early process exits by registering the
  exit handler up front and deferring the error until after stdout is
  drained, and adds a regression test that simulates a fast-exit child
  while still producing output so hangs are caught.

  Thibault Sottiaux · 2026-01-07 08:54:27 -08:00
  0d788e6263
• feat(sdk): add xhigh reasoning effort support to TypeScript SDK (#8108)

  Add "xhigh" to the ModelReasoningEffort type to match the Rust backend
  which already supports this reasoning level for models like
  gpt-5.1-codex-max.

  Conor Branagan · 2025-12-16 11:32:27 -08:00
  51865695e4
• fix: Upgrade @modelcontextprotocol/sdk to ^1.24.0 (#7817)

  ## What?
  Upgrades @modelcontextprotocol/sdk from ^1.20.2 to ^1.24.0 in the
  TypeScript SDK's devDependencies.
  
  ## Why?
  Related to #7737 - keeping development dependencies up to date with the
  latest MCP SDK version that includes the fix for CVE-2025-66414.
  
  Note: This change does not address the CVE for Codex users, as the MCP
  SDK is only in devDependencies here. The actual MCP integration that
  would be affected by the CVE is in the Rust codebase.
  
  ## How?
  •  Updated dependency version in sdk/typescript/package.json
  •  Ran pnpm install to update lockfile
  •  Fixed formatting (added missing newline in package.json)
  
  ## Related Issue
  Related to #7737
  
  ## Test Status
  ⚠️ After this upgrade, 2 additional tests timeout (1 test was already
  failing on main):
  •  tests/run.test.ts: "sends previous items when run is called twice" 
  •  tests/run.test.ts: "resumes thread by id"
  • tests/runStreamed.test.ts: "sends previous items when runStreamed is
  called twice"
  
  Marking as draft to investigate test timeouts. Maintainer guidance would
  be appreciated.
  
  Co-authored-by: HalfonA <amit@miggo.io>

  Amit Halfon · 2025-12-10 10:17:00 -08:00
  bd51d1b103
• feat(ts-sdk): allow overriding CLI environment (#6648)

  ## Summary
  - add an `env` option for the TypeScript Codex client and plumb it into
  `CodexExec` so the CLI can run without inheriting `process.env`
  - extend the test spy to capture spawn environments, add coverage for
  the new option, and document how to use it
  
  ## Testing
  - `pnpm test` *(fails: corepack cannot download pnpm because outbound
  network access is blocked in the sandbox)*
  
  ------
  [Codex
  Task](https://chatgpt.com/codex/tasks/task_i_6916b2d7c7548322a72d61d91a2dac85)

  Ryan Lopopolo · 2025-11-14 19:44:19 +00:00
  936650001f
• feat: Add support for --add-dir to exec and TypeScript SDK (#6565)

  ## Summary
  
  Adds support for specifying additional directories in the TypeScript SDK
  through a new `additionalDirectories` option in `ThreadOptions`.
  
  ## Changes
  
  - Added `additionalDirectories` parameter to `ThreadOptions` interface
  - Updated `CodexExec` to accept and pass through additional directories
  via the `--config` flag for `sandbox_workspace_write.writable_roots`
  - Added comprehensive test coverage for the new functionality
  
  ## Test plan
  
  - Added test case that verifies `additionalDirectories` is correctly
  passed as repeated flags
  - Existing tests continue to pass
  
  ---------
  
  Co-authored-by: Claude <noreply@anthropic.com>

  Dan Hernandez · 2025-11-13 13:47:10 -08:00
  b4a53aef47