4081 Commits

• Tweak /plugin menu wording (#15676)

  - Updated `/plugin` UI messaging for clearer wording.
  - Synced the same copy changes across `tui` and `tui_app_server`.

  canvrno-oai · 2026-03-24 14:44:09 -07:00
  b364faf4ec
• tui_app_server: cancel active login before Ctrl+C exit (#15673)

  ## Summary
  
  Fixes slow `Ctrl+C` exit from the ChatGPT browser-login screen in
  `tui_app_server`.
  
  ## Root cause
  
  Onboarding-level `Ctrl+C` quit bypassed the auth widget's cancel path.
  That let the active ChatGPT login keep running, and in-process
  app-server shutdown then waited on the stale login attempt before
  finishing.
  
  ## Changes
  
  - Extract a shared `cancel_active_attempt()` path in the auth widget
  - Use that path from onboarding-level `Ctrl+C` before exiting the TUI
  - Add focused tests for canceling browser-login and device-code attempts
  - Add app-server shutdown cleanup that explicitly drops any active login
  before draining background work

  Eric Traut · 2026-03-24 15:11:43 -06:00
  c023e9d959
• tui_app_server: open ChatGPT login in the local browser (#15672)

  ## Summary
  
  Fixes ChatGPT login in `tui_app_server` so the local browser opens again
  during in-process login flows.
  
  ## Root cause
  
  The app-server backend intentionally starts ChatGPT login with browser
  auto-open disabled, expecting the TUI client to open the returned
  `auth_url`. The app-server TUI was not doing that, so the login URL was
  shown in the UI but no browser window opened.
  
  ## Changes
  
  - Add a helper that opens the returned ChatGPT login URL locally
  - Call it from the main ChatGPT login flow
  - Call it from the device-code fallback-to-browser path as well
  - Limit auto-open to in-process app-server handles so remote sessions do
  not try to open a browser against a remote localhost callback

  Eric Traut · 2026-03-24 15:11:21 -06:00
  1b86377635
• tui: always restore the terminal on early exit (#15671)

  ## Summary
  
  Fixes early TUI exit paths that could leave the terminal in a dirty
  state and cause a stray `%` prompt marker after the app quit.
  
  ## Root cause
  
  Both `tui` and `tui_app_server` had early returns after `tui::init()`
  that did not guarantee terminal restore. When that happened, shells like
  `zsh` inherited the altered terminal state.
  
  ## Changes
  
  - Add a restore guard around `run_ratatui_app()` in both `tui` and
  `tui_app_server`
  - Route early exits through the guard instead of relying on scattered
  manual restore calls
  - Ensure terminal restore still happens on normal shutdown

  Eric Traut · 2026-03-24 14:29:29 -06:00
  989e513969
• Clean up TUI /plugins row allignment (#15669)

  - Remove marketplace from left column.
  - Change `Can be installed` to `Available`
  - Align right-column marketplace + selected-row hint text across states.
  - Changes applied to both `tui` and `tui_app_server`.
  - Update related snapshots/tests.
  
  
  <img width="2142" height="590" alt="image"
  src="https://github.com/user-attachments/assets/6e60b783-2bea-46d4-b353-f2fd328ac4d0"
  />

  canvrno-oai · 2026-03-24 20:27:10 +00:00
  3ba0e85edd
• Move git utilities into a dedicated crate (#15564)

  - create `codex-git-utils` and move the shared git helpers into it with
  file moves preserved for diff readability
  - move the `GitInfo` helpers out of `core` so stacked rollout work can
  depend on the shared crate without carrying its own git info module
  
  ---------
  
  Co-authored-by: Ahmed Ibrahim <219906144+aibrahim-oai@users.noreply.github.com>
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-03-24 13:26:23 -07:00
  0f957a93cd
• tui_app_server: tolerate missing rate limits while logged out (#15670)

  ## Summary
  
  Fixes a `tui_app_server` bootstrap failure when launching the CLI while
  logged out.
  
  ## Root cause
  
  During TUI bootstrap, `tui_app_server` fetched `account/rateLimits/read`
  unconditionally and treated failures as fatal. When the user was logged
  out, there was no ChatGPT account available, so that RPC failed and
  aborted startup with:
  
  ```
  Error: account/rateLimits/read failed during TUI bootstrap
  ```
  
  ## Changes
  
  - Only fetch bootstrap rate limits when OpenAI auth is required and a
  ChatGPT account is present
  - Treat bootstrap rate-limit fetch failures as non-fatal and fall back
  to empty snapshots
  - Log the fetch failure at debug level instead of aborting startup

  Eric Traut · 2026-03-24 14:01:06 -06:00
  fc97092f75
• fix: keep zsh-fork release assets after removing shell-tool-mcp (#15644)

  ## Why
  
  `shell-tool-mcp` and the Bash fork are no longer needed, but the patched
  zsh fork is still relevant for shell escalation and for the
  DotSlash-backed zsh-fork integration tests.
  
  Deleting the old `shell-tool-mcp` workflow also deleted the only
  pipeline that rebuilt those patched zsh binaries. This keeps the package
  removal, while preserving a small release path that can be reused
  whenever `codex-rs/shell-escalation/patches/zsh-exec-wrapper.patch`
  changes.
  
  ## What changed
  
  - removed the `shell-tool-mcp` workspace package, its npm
  packaging/release jobs, the Bash test fixture, and the remaining
  Bash-specific compatibility wiring
  - deleted the old `.github/workflows/shell-tool-mcp.yml` and
  `.github/workflows/shell-tool-mcp-ci.yml` workflows now that their
  responsibilities have been replaced or removed
  - kept the zsh patch under
  `codex-rs/shell-escalation/patches/zsh-exec-wrapper.patch` and updated
  the `codex-rs/shell-escalation` docs/code to describe the zsh-based flow
  directly
  - added `.github/workflows/rust-release-zsh.yml` to build only the three
  zsh binaries that `codex-rs/app-server/tests/suite/zsh` needs today:
    - `aarch64-apple-darwin` on `macos-15`
    - `x86_64-unknown-linux-musl` on `ubuntu-24.04`
    - `aarch64-unknown-linux-musl` on `ubuntu-24.04`
  - extracted the shared zsh build/smoke-test/stage logic into
  `.github/scripts/build-zsh-release-artifact.sh`, made that helper
  directly executable, and now invoke it directly from the workflow so the
  Linux and macOS jobs only keep the OS-specific setup in YAML
  - wired those standalone `codex-zsh-*.tar.gz` assets into
  `rust-release.yml` and added `.github/dotslash-zsh-config.json` so
  releases also publish a `codex-zsh` DotSlash file
  - updated the checked-in `codex-rs/app-server/tests/suite/zsh` fixture
  comments to explain that new releases come from the standalone zsh
  assets, while the checked-in fixture remains pinned to the latest
  historical release until a newer zsh artifact is published
  - tightened a couple of follow-on cleanups in
  `codex-rs/shell-escalation`: the `ExecParams::command` comment now
  describes the shell `-c`/`-lc` string more clearly, and the README now
  points at the same `git.code.sf.net` zsh source URL that the workflow
  uses
  
  ## Testing
  
  - `cargo test -p codex-shell-escalation`
  - `just argument-comment-lint`
  - `bash -n .github/scripts/build-zsh-release-artifact.sh`
  - attempted `cargo test -p codex-core`; unrelated existing failures
  remain, but the touched `tools::runtimes::shell::unix_escalation::*`
  coverage passed during that run

  Michael Bolin · 2026-03-24 12:56:26 -07:00
  e89e5136bd
• Hide numeric prefixes on disabled TUI list rows (#15660)

  - Remove numeric prefixes for disabled rows in shared list rendering.
  These numbers are shortcuts, Ex: Pressing "2" selects option `#2`.
  Disabled items can not be selected, so keeping numbers on these items is
  misleading.
  - Apply the same behavior in both tui and tui_app_server.
  - Update affected snapshots for apps/plugins loading and plugin detail
  rows.
  
  _**This is a global change.**_
  
  Before:
  <img width="1680" height="488" alt="image"
  src="https://github.com/user-attachments/assets/4bcf94ad-285f-48d3-a235-a85b58ee58e2"
  />
  
  After:
  <img width="1706" height="484" alt="image"
  src="https://github.com/user-attachments/assets/76bb6107-a562-42fe-ae94-29440447ca77"
  />

  canvrno-oai · 2026-03-24 12:52:56 -07:00
  363b373979
• Trim pre-turn context updates during rollback (#15577)

  ## Summary
  - trim contiguous developer/contextual-user pre-turn updates when
  rollback cuts back to a user turn
  - add a focused history regression test for the trim behavior
  - update the rollback request-boundary snapshots to show the fixed
  non-duplicating context shape
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-24 12:43:53 -07:00
  2d61357c76
• chore: stop app-server auth refresh storms after permanent token failure (#15530)

  built from #14256. PR description from @etraut-openai:
  
  This PR addresses a hole in [PR
  11802](https://github.com/openai/codex/pull/11802). The previous PR
  assumed that app server clients would respond to token refresh failures
  by presenting the user with an error ("you must log in again") and then
  not making further attempts to call network endpoints using the expired
  token. While they do present the user with this error, they don't
  prevent further attempts to call network endpoints and can repeatedly
  call `getAuthStatus(refreshToken=true)` resulting in many failed calls
  to the token refresh endpoint.
  
  There are three solutions I considered here:
  1. Change the getAuthStatus app server call to return a null auth if the
  caller specified "refreshToken" on input and the refresh attempt fails.
  This will cause clients to immediately log out the user and return them
  to the log in screen. This is a really bad user experience. It's also a
  breaking change in the app server contract that could break third-party
  clients.
  2. Augment the getAuthStatus app server call to return an additional
  field that indicates the state of "token could not be refreshed". This
  is a non-breaking change to the app server API, but it requires
  non-trivial changes for all clients to properly handle this new field
  properly.
  3. Change the getAuthStatus implementation to handle the case where a
  token refresh fails by marking the AuthManager's in-memory access and
  refresh tokens as "poisoned" so it they are no longer used. This is the
  simplest fix that requires no client changes.
  
  I chose option 3.
  
  Here's Codex's explanation of this change:
  
  When an app-server client asks `getAuthStatus(refreshToken=true)`, we
  may try to refresh a stale ChatGPT access token. If that refresh fails
  permanently (for example `refresh_token_reused`, expired, or revoked),
  the old behavior was bad in two ways:
  
  1. We kept the in-memory auth snapshot alive as if it were still usable.
  2. Later auth checks could retry refresh again and again, creating a
  storm of doomed `/oauth/token` requests and repeatedly surfacing the
  same failure.
  
  This is especially painful for app-server clients because they poll auth
  status and can keep driving the refresh path without any real chance of
  recovery.
  
  This change makes permanent refresh failures terminal for the current
  managed auth snapshot without changing the app-server API contract.
  
  What changed:
  - `AuthManager` now poisons the current managed auth snapshot in memory
  after a permanent refresh failure, keyed to the unchanged `AuthDotJson`.
  - Once poisoned, later refresh attempts for that same snapshot fail fast
  locally without calling the auth service again.
  - The poison is cleared automatically when auth materially changes, such
  as a new login, logout, or reload of different auth state from storage.
  - `getAuthStatus(includeToken=true)` now omits `authToken` after a
  permanent refresh failure instead of handing out the stale cached bearer
  token.
  
  This keeps the current auth method visible to clients, avoids forcing an
  immediate logout flow, and stops repeated refresh attempts for
  credentials that cannot recover.
  
  ---------
  
  Co-authored-by: Eric Traut <etraut@openai.com>

  Celia Chen · 2026-03-24 12:39:58 -07:00
  88694e8417
• chore: use access token expiration for proactive auth refresh (#15545)

  Follow up to #15357 by making proactive ChatGPT auth refresh depend on
  the access token's JWT expiration instead of treating `last_refresh` age
  as the primary source of truth.

  Celia Chen · 2026-03-24 19:34:48 +00:00
  7dc2cd2ebe
• feat: include marketplace loading error in plugin/list (#15438)

  Include error.

  xl-openai · 2026-03-24 11:47:23 -07:00
  621862a7d1
• feat: communication pattern v2 (#15647)

  See internal communication

  jif-oai · 2026-03-24 18:45:49 +00:00
  773fbf56a4
• app-server: Add back pressure and batching to command/exec (#15547)

  * Add
  `OutgoingMessageSender::send_server_notification_to_connection_and_wait`
  which returns only once message is written to websocket (or failed to do
  so)
  * Use this mechanism to apply back pressure to stdout/stderr streams of
  processes spawned by `command/exec`, to limit them to at most one
  message in-memory at a time
  * Use back pressure signal to also batch smaller chunks into ≈64KiB ones
  
  This should make commands execution more robust over
  high-latency/low-throughput networks

  Ruslan Nigmatullin · 2026-03-24 11:35:51 -07:00
  d61c03ca08
• core: Make FileWatcher reusable (#15093)

  ### Summary
  Make `FileWatcher` a reusable core component which can be built upon.
  Extract skills-related logic into a separate `SkillWatcher`.
  Introduce a composable `ThrottledWatchReceiver` to throttle filesystem
  events, coalescing affected paths among them.
  
  ### Testing
  Updated existing unit tests.

  Ruslan Nigmatullin · 2026-03-24 11:04:47 -07:00
  daf5e584c2
• Increase voice space hold timeout to 1s (#15579)

  Increase the space-hold delay to 1 second before voice capture starts,
  and mirror the change in tui_app_server.

  Ahmed Ibrahim · 2026-03-24 10:47:26 -07:00
  bb7e9a8171
• Pretty plugin labels, preserve plugin app provenance during MCP tool refresh (#15606)

  - Prefer plugin manifest `interface.displayName` for plugin labels.
  - Preserve plugin provenance when handling `list_mcp_tools` so connector
  `plugin_display_names` are not clobbered.
  - Add a TUI test to ensure plugin-owned app mentions are deduped
  correctly.

  canvrno-oai · 2026-03-24 10:34:19 -07:00
  66edc347ae
• [codex] Stabilize second compaction history test (#15605)

  ## Summary
  - replace the second-compaction test fixtures with a single ordered
  `/responses` sequence
  - assert against the real recorded request order instead of aggregating
  per-mock captures
  - realign the second-summary assertion to the first post-compaction user
  turn where the summary actually appears
  
  ## Root cause
  `compact_resume_after_second_compaction_preserves_history` collected
  requests from multiple `mount_sse_once_match` recorders. Overlapping
  matchers could record the same HTTP request more than once, so the test
  indexed into a duplicated synthetic list rather than the true request
  stream. That made the summary assertion depend on matcher evaluation
  order and platform-specific behavior.
  
  ## Impact
  - makes the flaky test deterministic by removing duplicate request
  capture from the assertion path
  - keeps the change scoped to the test only
  
  ## Validation
  - `just fmt`
  - `just argument-comment-lint`
  - `env -u CODEX_SANDBOX_NETWORK_DISABLED cargo test -p codex-core
  compact_resume_after_second_compaction_preserves_history -- --nocapture`
  - repeated the same targeted test 10 times
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-24 10:14:21 -07:00
  910cf49269
• feat: disable notifier v2 and start turn on agent interaction (#15624)

  Make the inter-agent communication start a turn
  
  As part of this, we disable the v2 notifier to prevent some odd
  behaviour where the agent restart working while you're talking to it for
  example

  jif-oai · 2026-03-24 17:01:24 +00:00
  b51d5f18c7
• Refresh mentions list after plugin install/uninstall (#15598)

  Refresh mentions list after plugin install/uninstall to that $mentions
  are updated without requiring exiting/launching the client.

  canvrno-oai · 2026-03-24 09:36:26 -07:00
  0f90a34676
• [Codex TUI] - Sort /plugins TUI menu by installed status first, alpha second (#15558)

  Updates plugin ordering so installed plugins are listed first, with
  alphabetical sorting applied within the installed and uninstalled
  groups. The behavior is now consistent across both `tui` and
  `tui_app_server`, and related tests/snapshots were updated.

  canvrno-oai · 2026-03-24 09:35:52 -07:00
  2d5a3bfe76
• Extract sandbox manager and transforms into codex-sandboxing (#15603)

  Extract sandbox manager

  pakrym-oai · 2026-03-24 08:20:57 -07:00
  f49eb8e9d7
• Finish moving codex exec to app-server (#15424)

  This PR completes the conversion of non-interactive `codex exec` to use
  app server rather than directly using core events and methods.
  
  ### Summary
  - move `codex-exec` off exec-owned `AuthManager` and `ThreadManager`
  state
  - route exec bootstrap, resume, and auth refresh through existing
  app-server paths
  - replace legacy `codex/event/*` decoding in exec with typed app-server
  notification handling
  - update human and JSONL exec output adapters to translate existing
  app-server notifications only
  - clean up "app server client" layer by eliminating support for legacy
  notifications; this is no longer needed
  - remove exposure of `authManager` and `threadManager` from "app server
  client" layer
  
  ### Testing
  - `exec` has pretty extensive unit and integration tests already, and
  these all pass
  - In addition, I asked Codex to put together a comprehensive manual set
  of tests to cover all of the `codex exec` functionality (including
  command-line options), and it successfully generated and ran these tests

  Eric Traut · 2026-03-24 08:51:32 -06:00
  45f68843b8
• Allow global network allowlist wildcard (#15549)

  ## Problem
  
  Today `codex-network-proxy` rejects a global `*` in
  `network.allowed_domains`, so there is no static way to configure a
  denylist-only posture for public hosts. Users have to enumerate broad
  allowlist patterns instead.
  
  ## Approach
  
  - Make global wildcard acceptance field-specific: `allowed_domains` can
  use `*`, while `denied_domains` still rejects a global wildcard.
  - Keep the existing evaluation order, so explicit denies still win first
  and local/private protections still apply unless separately enabled.
  - Add coverage for the denylist-only behavior and update the README to
  document it.
  
  ## Validation
  
  - `just fmt`
  - `cargo test -p codex-network-proxy` (full run had one unrelated flaky
  telemetry test:
  `network_policy::tests::emit_block_decision_audit_event_emits_non_domain_event`;
  reran in isolation and it passed)
  - `cargo test -p codex-network-proxy
  network_policy::tests::emit_block_decision_audit_event_emits_non_domain_event
  -- --exact --nocapture`
  - `just fix -p codex-network-proxy`
  - `just argument-comment-lint`

  rreichel3-oai · 2026-03-24 10:43:46 -04:00
  1db6cb9789
• nit: optim on list agents (#15623)

  Lazy computation

  jif-oai · 2026-03-24 12:01:01 +00:00
  95e1d59939
• feat: list agents for sub-agent v2 (#15621)

  Add a `list_agents` for multi-agent v2, optionally path based
  
  This return the task and status of each agent in the matched path

  jif-oai · 2026-03-24 11:24:08 +00:00
  38c088ba8d
• fix: flaky test (#15614)
  jif-oai · 2026-03-24 11:01:54 +00:00
  567832c6fe
• nit: split v2 wait (#15613)
  jif-oai · 2026-03-24 09:57:19 +00:00
  f9545278e2
• Stabilize macOS CI test timeouts (#15581)

  ## Summary
  - raise the shell snapshot apply_patch helper timeout to avoid macOS CI
  startup races
  - increase the shared MCP app-server test read timeout so slow
  initialize handshakes do not fail command_exec tests spuriously
  
  ## Testing
  - cargo test -p codex-core
  shell_command_snapshot_still_intercepts_apply_patch
  - cargo test -p codex-app-server
  command_exec_tty_implies_streaming_and_reports_pty_output
  
  Co-authored-by: Codex <noreply@openai.com>

  Dylan Hurd · 2026-03-24 09:33:20 +00:00
  79577355c1
• Remove filter from plugins/list result (#15580)

  Show all plugin marketplaces in the /plugins popup by removing the
  `openai-curated` marketplace filter, and update plugin popup
  copy/tests/snapshots to match the new behavior in both TUI codepaths.

  canvrno-oai · 2026-03-23 23:41:01 -07:00
  c850607129
• Move sandbox policy transforms into codex-sandboxing (#15599)

  ## Summary
  - move the pure sandbox policy transform helpers from `codex-core` into
  `codex-sandboxing`
  - move the corresponding unit tests with the extracted implementation
  - update `core` and `app-server` callers to import the moved APIs
  directly, without re-exports or proxy methods
  
  ## Testing
  - cargo test -p codex-sandboxing
  - cargo test -p codex-core sandboxing
  - cargo test -p codex-app-server --lib
  - just fix -p codex-sandboxing
  - just fix -p codex-core
  - just fix -p codex-app-server
  - just fmt
  - just argument-comment-lint

  pakrym-oai · 2026-03-23 22:22:44 -07:00
  9deb8ce3fc
• move imagegen skill into system skills (#15600)

  Add imagegen skill as built-in skill. Source: github.com/openai/skills

  Dominik Kundel · 2026-03-24 05:14:33 +00:00
  a10960e41c
• [codex-cli][app-server] Update self-serve business usage limit copy in error returned (#15478)

  ## Summary
  - update the self-serve business usage-based limit message to direct
  users to their admin for additional credits
  - add a focused unit test for the self_serve_business_usage_based plan
  branch
  
  Added also: 
  
  If you are at a rate limit but you still have credits, codex cli would
  tell you to switch the model. We shouldnt do this if you have credits so
  fixed this.
  
  ## Test
  - launched the source-built CLI and verified the updated message is
  shown for the self-serve business usage-based plan
  
  ![Test
  screenshot](https://raw.githubusercontent.com/openai/codex/5cc3c013ef17ac5c66dfd9395c0d3c4837602231/docs/images/self-serve-business-usage-limit.png)

  dhruvgupta-oai · 2026-03-24 04:41:38 +00:00
  c2410060ea
• Move macOS sandbox builders into codex-sandboxing (#15593)

  ## Summary
  - move macOS permission merging/intersection logic and tests from
  `codex-core` into `codex-sandboxing`
  - move seatbelt policy builders, permissions logic, SBPL assets, and
  their tests into `codex-sandboxing`
  - keep `codex-core` owning only the seatbelt spawn wrapper and switch
  call sites to import the moved APIs directly
  
  ## Notes
  - no re-exports added
  - moved the seatbelt tests with the implementation so internal helpers
  could stay private
  - local verification is still finishing while this PR is open

  pakrym-oai · 2026-03-23 21:26:35 -07:00
  431af0807c
• Extract landlock helpers into codex-sandboxing (#15592)

  ## Summary
  - add a new `codex-sandboxing` crate for sandboxing extraction work
  - move the pure Linux sandbox argv builders and their unit tests out of
  `codex-core`
  - keep `core::landlock` as the spawn wrapper and update direct callers
  to use `codex_sandboxing::landlock`
  
  ## Testing
  - `cargo test -p codex-sandboxing`
  - `cargo test -p codex-core landlock`
  - `cargo test -p codex-cli debug_sandbox`
  - `just argument-comment-lint`
  
  ## Notes
  - this is step 1 of the move plan aimed at minimizing per-PR diffs
  - no re-exports or no-op proxy methods were added

  pakrym-oai · 2026-03-23 20:56:15 -07:00
  2227248cd6
• Add plugin-creator as system skill (#15554)
  alexsong-oai · 2026-03-23 19:08:30 -07:00
  db8bb7236d
• Add fork snapshot modes (#15239)

  ## Summary
  - add `ForkSnapshotMode` to `ThreadManager::fork_thread` so callers can
  request either a committed snapshot or an interrupted snapshot
  - share the model-visible `<turn_aborted>` history marker between the
  live interrupt path and interrupted forks
  - update the small set of direct fork callsites to pass
  `ForkSnapshotMode::Committed`
  
  Note: this enables /btw to work similarly as Esc to interrupt (hopefully
  somewhat in distribution)
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-23 19:05:42 -07:00
  f547b79bd0
• fix: build PATH env var using OsString instead of String (#15360)
  Michael Bolin · 2026-03-23 18:59:04 -07:00
  84fb180eeb
• feat: custom watcher for multi-agent v2 (#15576)

  The new wait tool just returns `Wait timed out.` or `Wait completed.`.
  The actual content is done through the notification watcher

  jif-oai · 2026-03-23 23:27:55 +00:00
  527244910f
• feat: custom watcher for multi-agent v2 (#15570)

  Custom watcher that sends an InterAgentCommunication on end of turn

  jif-oai · 2026-03-23 22:56:17 +00:00
  4605c65308
• [codex] Add rollback context duplication snapshot (#15562)

  ## What changed
  - adds a targeted snapshot test for rollback with contextual diffs in
  `codex_tests.rs`
  - snapshots the exact model-visible request input before the rolled-back
  turn and on the follow-up request after rollback
  - shows the duplicate developer and environment context pair appearing
  again before the follow-up user message
  
  ## Why
  Rollback currently rewinds the reference context baseline without
  rewinding the live session overrides. On the next turn, the same
  contextual diff is emitted again and duplicated in the request sent to
  the model.
  
  ## Impact
  - makes the regression visible in a canonical snapshot test
  - keeps the snapshot on the shared `context_snapshot` path without
  adding new formatting helpers
  - gives a direct repro for future fixes to rollback/context
  reconstruction
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-23 15:36:23 -07:00
  0f34b14b41
• chore(core) Add approvals reviewer to UserTurn (#15426)

  ## Summary
  Adds support for approvals_reviewer to `Op::UserTurn` so we can migrate
  `[CodexMessageProcessor::turn_start]` to use Op::UserTurn
  
  ## Testing
  - [x] Adds quick test for the new field
  
  Co-authored-by: Codex <noreply@openai.com>

  Dylan Hurd · 2026-03-23 15:19:01 -07:00
  67c1c7c054
• feat: use serde to differenciate inter agent communication (#15560)

  Use `serde` to encode the inter agent communication to an assistant
  message and use the decode to see if this is such a message
  
  Note: this assume serde on small pattern is fast enough

  jif-oai · 2026-03-23 22:09:55 +00:00
  191fd9fd16
• [hooks] add non-streaming (non-stdin style) shell-only PreToolUse support (#15211)

  - add `PreToolUse` hook for bash-like tool execution only at first
  - block shell execution before dispatch with deny-only hook behavior
  - introduces common.rs matcher framework for matching when hooks are run
  
  example run:
  
  ```
  › run three parallel echo commands, and the second one should echo "[block-pre-tool-use]" as a test
  
  
  • Running the three echo commands in parallel now and I’ll report the output directly.
  
  • Running PreToolUse hook: name for demo pre tool use hook
  
  • Running PreToolUse hook: name for demo pre tool use hook
  
  • Running PreToolUse hook: name for demo pre tool use hook
  
  PreToolUse hook (completed)
    warning: wizard-tower PreToolUse demo inspected Bash: echo "first parallel echo"
    
  PreToolUse hook (blocked)
    warning: wizard-tower PreToolUse demo blocked a Bash command on purpose.
    feedback: PreToolUse demo blocked the command. Remove [block-pre-tool-use] to continue.
  
  PreToolUse hook (completed)
    warning: wizard-tower PreToolUse demo inspected Bash: echo "third parallel echo"
  
  • Ran echo "first parallel echo"
    └ first parallel echo
  
  • Ran echo "third parallel echo"
    └ third parallel echo
  
  • Three little waves went out in parallel.
  
    1. printed first parallel echo
    2. was blocked before execution because it contained the exact test string [block-pre-tool-use]
    3. printed third parallel echo
  
    There was also an unrelated macOS defaults warning around the successful commands, but the echoes
    themselves worked fine. If you want, I can rerun the second one with a slightly modified string so
    it passes cleanly.
  ```

  Andrei Eternal · 2026-03-23 14:32:59 -07:00
  73bbb07ba8
• feat: new op type for sub-agents communication (#15556)

  Add `InterAgentCommunication` for v2 agent communication

  jif-oai · 2026-03-23 21:09:00 +00:00
  18f1a08bc9
• fix: main tui (#15557)
  jif-oai · 2026-03-23 20:51:07 +00:00
  7eb9e75b86
• Unify realtime stop handling in TUI (#15529)

  ## Summary
  - route /realtime, Ctrl+C, and deleted realtime meters through the same
  realtime stop path
  - keep generic transcription placeholder cleanup free of realtime
  shutdown side effects
  
  ## Testing
  - Ran 
  - Relied on CI for verification; did not run local tests
  
  ---------
  
  Co-authored-by: Codex <noreply@openai.com>

  Ahmed Ibrahim · 2026-03-23 13:47:33 -07:00
  7b92a90612
• feat: support disable skills by name. (#15378)

  Support disabling skills by name, primarily for plugin skills. We can’t
  use the path, since plugin skill paths may change across versions.

  xl-openai · 2026-03-23 12:57:40 -07:00
  9a33e5c0a0
• Thread guardian Responses API errors into denial rationale (#15516)

  ## Summary
  - capture the last guardian `EventMsg::Error` while waiting for review
  completion
  - reuse that error as the denial rationale when the review turn
  completes without an assessment payload
  - add a regression test for the `/responses` HTTP 400 path
  
  ## Testing
  - `just fmt`
  - `cargo test -p codex-core
  guardian_review_surfaces_responses_api_errors_in_rejection_reason`
  - `just argument-comment-lint -p codex-core`
  
  ## Notes
  - `cargo test -p codex-core` still fails on the pre-existing unrelated
  test
  `tools::js_repl::tests::js_repl_imported_local_files_can_access_repl_globals`
  in this environment (`mktemp ... Operation not permitted` while
  downloading `dotslash`)
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-23 12:46:49 -07:00
  332edba78e