1397 Commits

• [apps] Add thread_id param to optionally load thread config for apps feature check. (#11279)

  - [x] Add thread_id param to optionally load thread config for apps
  feature check

  Matthew Zeng · 2026-02-09 23:10:26 -08:00
  005e040f97
• Disable dynamic model refresh for custom model providers (#11239)

  The dynamic model refresh feature (`https://api.openai.com/v1/models`
  endpoint) is currently gated on a runtime check for an auth method other
  than API Key. It should be gated on a check specifically for ChatGPT
  Auth because some custom model providers (e.g. for local models) use no
  auth mechanism. A call to `self.auth_manager.auth_mode()` will return
  `None` in this case.
  
  Addresses #11213

  Eric Traut · 2026-02-09 21:36:09 -08:00
  bb974c78de
• fix(app-server): for external auth, replace id_token with chatgpt_acc… (#11240)

  …ount_id and chatgpt_plan_type
  
  ### Summary
  Following up on external auth mode which was introduced here:
  https://github.com/openai/codex/pull/10012
  
  Turns out some clients have a differently shaped ID token and don't have
  a chosen workspace (aka chatgpt_account_id) encoded in their ID token.
  So, let's replace `id_token` param with `chatgpt_account_id` and
  `chatgpt_plan_type` (optional) when initializing the external ChatGPT
  auth mode (`account/login/start` with `chatgptAuthTokens`).
  
  The client was able to test end-to-end with a Codex build from this
  branch and verified it worked!

  Owen Lin · 2026-02-09 20:48:58 -08:00
  53741013ab
• chore: change ConfigState so it no longer depends on a single config.toml file for reloading (#11262)

  If anything, it should depend on `ConfigLayerStack`.
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/11262).
  * #11207
  * __->__ #11262

  Michael Bolin · 2026-02-09 19:26:39 -08:00
  862ab63071
• Revert "Revert "Update models.json"" (#11256)

  Reverts openai/codex#11255

  Ahmed Ibrahim · 2026-02-09 19:22:41 -08:00
  d1df3bd63b
• Remove offline fallback for models (#11238)

  # External (non-OpenAI) Pull Request Requirements
  
  Before opening this Pull Request, please read the dedicated
  "Contributing" markdown file or your PR may be closed:
  https://github.com/openai/codex/blob/main/docs/contributing.md
  
  If your PR conforms to our contribution guidelines, replace this text
  with a detailed and high quality description of your changes.
  
  Include a link to a bug report or enhancement request.

  Ahmed Ibrahim · 2026-02-09 16:58:54 -08:00
  a1abd53b6a
• fix(feature) UnderDevelopment feature must be off (#11242)

  ## Summary
  1. Bump RemoteModels to Stable
  2. Assert that all UnderDevelopment features are off by default
  
  ## Testing
  - [x] Added unit test

  Dylan Hurd · 2026-02-09 15:14:15 -08:00
  d65f09b913
• Use longest remote model prefix matching (#11228)

  Match model metadata by longest matching remote slug prefix before local
  fallback.
  
  - Update `get_model_info` to prefer the most specific remote slug prefix
  for the requested model.
  - Add an integration test to assert `gpt-5.3-codex-test` resolves to
  `gpt-5.3-codex` over `gpt-5.3`.

  Ahmed Ibrahim · 2026-02-09 15:05:56 -08:00
  481145e959
• [apps] Add gated instructions for Apps. (#10924)

  - [x] Add gated instructions for Apps.

  Matthew Zeng · 2026-02-09 14:48:09 -08:00
  d90df4761b
• feat: tie shell snapshot to cwd (#11231)

  Fix for this: https://github.com/openai/codex/issues/11223
  
  Basically we tie the shell snapshot to a `cwd` to handle `cwd`-based env
  setups

  jif-oai · 2026-02-09 22:14:39 +00:00
  ffd4bd345c
• feat: use a notify instead of grace to close ue process (#11219)
  jif-oai · 2026-02-09 22:14:33 +00:00
  c2ca51273f
• skill-creator: Remove invalid reference. (#10960)

  Remove references to two files that do not exist.

  xl-openai · 2026-02-09 13:37:27 -08:00
  cca13fb03a
• feat: extend skills/list to support additional roots. (#10835)

  Add an optional perCwdExtraUserRoots

  xl-openai · 2026-02-09 13:30:38 -08:00
  a33ee46e3b
• state: add memory consolidation lock primitives (#11199)

  ## Summary
  - add a migration for memory_consolidation_locks
  - add acquire/release lock primitives to codex-state runtime
  - add core/state_db wrappers and cwd normalization for memory queries
  and lock keys
  
  ## Testing
  - cargo test -p codex-state memory_consolidation_lock_
  - cargo test -p codex-core --lib state_db::

  jif-oai · 2026-02-09 21:04:20 +00:00
  74ecd6e3b2
• feat: search_tool (#10657)

  **Why We Did This**
  - The goal is to reduce MCP tool context pollution by not exposing the
  full MCP tool list up front
  - It forces an explicit discovery step (`search_tool_bm25`) so the model
  narrows tool scope before making MCP calls, which helps relevance and
  lowers prompt/tool clutter.
  
  **What It Changed**
  - Added a new experimental feature flag `search_tool` in
  `core/src/features.rs:90` and `core/src/features.rs:430`.
  - Added config/schema support for that flag in
  `core/config.schema.json:214` and `core/config.schema.json:1235`.
  - Added BM25 dependency (`bm25`) in `Cargo.toml:129` and
  `core/Cargo.toml:23`.
  - Added new tool handler `search_tool_bm25` in
  `core/src/tools/handlers/search_tool_bm25.rs:18`.
  - Registered the handler and tool spec in
  `core/src/tools/handlers/mod.rs:11` and `core/src/tools/spec.rs:780` and
  `core/src/tools/spec.rs:1344`.
  - Extended `ToolsConfig` to carry `search_tool` enablement in
  `core/src/tools/spec.rs:32` and `core/src/tools/spec.rs:56`.
  - Injected dedicated developer instructions for tool-discovery workflow
  in `core/src/codex.rs:483` and `core/src/codex.rs:1976`, using
  `core/templates/search_tool/developer_instructions.md:1`.
  - Added session state to store one-shot selected MCP tools in
  `core/src/state/session.rs:27` and `core/src/state/session.rs:131`.
  - Added filtering so when feature is enabled, only selected MCP tools
  are exposed on the next request (then consumed) in
  `core/src/codex.rs:3800` and `core/src/codex.rs:3843`.
  - Added E2E suite coverage for
  enablement/instructions/hide-until-search/one-turn-selection in
  `core/tests/suite/search_tool.rs:72`,
  `core/tests/suite/search_tool.rs:109`,
  `core/tests/suite/search_tool.rs:147`, and
  `core/tests/suite/search_tool.rs:218`.
  - Refactored test helper utilities to support config-driven tool
  collection in `core/tests/suite/tools.rs:281`.
  
  **Net Behavioral Effect**
  - With `search_tool` **off**: existing MCP behavior (tools exposed
  normally).
  - With `search_tool` **on**: MCP tools start hidden, model must call
  `search_tool_bm25`, and only returned `selected_tools` are available for
  the next model call.

  Anton Panasenko · 2026-02-09 12:53:50 -08:00
  becc3a0424
• core: add focused diagnostics for remote compaction overflows (#11133)

  ## Summary
  - add targeted remote-compaction failure diagnostics in compact_remote
  logging
  - log the specific values needed to explain overflow timing:
    - last_api_response_total_tokens
    - estimated_tokens_of_items_added_since_last_successful_api_response
    - estimated_bytes_of_items_added_since_last_successful_api_response
    - failing_compaction_request_body_bytes
  - simplify breakdown naming and remove
  last_api_response_total_bytes_estimate (it was an approximation and not
  useful for debugging)
  
  ## Why
  When compaction fails with context_length_exceeded, we need concrete,
  low-ambiguity numbers that map directly to:
  1) what the API most recently reported, and
  2) what local history added since then.
  
  This keeps the failure logs actionable without adding broad, noisy
  metrics.
  
  ## Testing
  - just fmt
  - cargo test -p codex-core

  Charley Cunningham · 2026-02-09 12:42:20 -08:00
  9450cd9ce5
• Revert "chore: enable sub agents" (#11230)

  Reverts openai/codex#11173

  jif-oai · 2026-02-09 20:22:38 +00:00
  c2bfd1e473
• Move warmup to the task level (#11216)

  Instead of storing a special connection on the client level make the
  regular task responsible for establishing a normal client session and
  open a connection on it.
  
  Then when the turn is started we pass in a pre-established session.

  pakrym-oai · 2026-02-09 10:57:52 -08:00
  ccd17374cb
• Fixed bug in file watcher that results in spurious skills update events and large log files (#11217)

  On some platforms, the "notify" file watcher library emits events for
  file opens and reads, not just file modifications or deletes. The
  previous implementation didn't take this into account.
  
  Furthermore, the `tracing.info!` call that I previously added was
  emitting a lot of logs. I had assumed incorrectly that `info` level
  logging was disabled by default, but it's apparently enabled for this
  crate. This is resulting in large logs (hundreds of MB) for some users.

  Eric Traut · 2026-02-09 10:33:57 -08:00
  9346d321d2
• tools: remove get_memory tool and tests (#11198)

  Drop this memory tool as the design changed

  jif-oai · 2026-02-09 17:47:36 +00:00
  cfce286459
• core: account for all post-response items in auto-compact token checks (#11132)

  ## Summary
  - change compaction pre-check accounting to include all items added
  after the last model-generated item, not only trailing codex-generated
  outputs
  - use that boundary consistently in get_total_token_usage() and
  get_total_token_usage_breakdown()
  - update history tests to cover user/tool-output items after the last
  model item
  
  ## Why
  last_token_usage.total_tokens is API-reported for the last successful
  model response. After that point, local history may gain additional
  items (user messages, injected context, tool outputs). Compaction
  triggering must account for all of those items to avoid late compaction
  attempts that can overflow context.
  
  ## Testing
  - just fmt
  - cargo test -p codex-core

  Charley Cunningham · 2026-02-09 08:34:38 -08:00
  0883e5d3e5
• Load requirements on windows (#10770)

  We support requirements on Unix, loading from
  `/etc/codex/requirements.toml`. On MacOS, we also support MDM.
  
  Now, on Windows, we'll load requirements from
  `%ProgramData%\OpenAI\Codex\requirements.toml`

  gt-oai · 2026-02-09 16:05:38 +00:00
  9fe925b15a
• chore: enable sub agents (#11173)
  jif-oai · 2026-02-09 11:25:37 +00:00
  284c03ceab
• chore: enable shell snapshot (#11172)
  jif-oai · 2026-02-09 11:23:59 +00:00
  753821c90f
• feat: do not close unified exec processes across turns (#10799)

  With this PR we do not close the unified exec processes (i.e. background
  terminals) at the end of a turn unless:
  * The user interrupt the turn
  * The user decide to clean the processes through `app-server` or
  `/clean`
  
  I made sure that `codex exec` correctly kill all the processes

  jif-oai · 2026-02-09 10:27:46 +00:00
  6cf61725d0
• feat: include NetworkConfig through ExecParams (#11105)

  This PR adds the following field to `Config`:
  
  ```rust
  pub network: Option<NetworkProxy>,
  ```
  
  Though for the moment, it will always be initialized as `None` (this
  will be addressed in a subsequent PR).
  
  This PR does the work to thread `network` through to `execute_exec_env()`, `process_exec_tool_call()`, and `UnifiedExecRuntime.run()` to ensure it is available whenever we span a process.

  Michael Bolin · 2026-02-09 03:32:17 +00:00
  383b45279e
• chore: reverse the codex-network-proxy -> codex-core dependency (#11121)
  Michael Bolin · 2026-02-08 17:03:24 -08:00
  ff74aaae21
• [apps] Improve app loading. (#10994)

  There are two concepts of apps that we load in the harness:
  
  - Directory apps, which is all the apps that the user can install.
  - Accessible apps, which is what the user actually installed and can be
  $ inserted and be used by the model. These are extracted from the tools
  that are loaded through the gateway MCP.
  
  Previously we wait for both sets of apps before returning the full apps
  list. Which causes many issues because accessible apps won't be
  available to the UI or the model if directory apps aren't loaded or
  failed to load.
  
  In this PR we are separating them so that accessible apps can be loaded
  separately and are instantly available to be shown in the UI and to be
  provided in model context. We also added an app-server event so that
  clients can subscribe to also get accessible apps without being blocked
  on the full app list.
  
  - [x] Separate accessible apps and directory apps loading.
  - [x] `app/list` request will also emit `app/list/updated` notifications
  that app-server clients can subscribe. Which allows clients to get
  accessible apps list to render in the $ menu without being blocked by
  directory apps.
  - [x] Cache both accessible and directory apps with 1 hour TTL to avoid
  reloading them when creating new threads.
  - [x] TUI improvements to redraw $ menu and /apps menu when app list is
  updated.

  Matthew Zeng · 2026-02-08 15:24:56 -08:00
  45b7763c3f
• feat: include [experimental_network] in <environment_context> (#11044)

  If `NetworkConstraints` is set, then include the relevant settings on `<environment_context>`. Example:
  
  ```xml
  <environment_context>
    <cwd>/repo</cwd>
    <shell>bash</shell>
    <network enabled="true">
      <allowed>api.example.com</allowed>
      <allowed>*.openai.com</allowed>
      <denied>blocked.example.com</denied>
    </network>
  </environment_context>
  ```

  Michael Bolin · 2026-02-08 15:16:50 -08:00
  181b721ba5
• Upgrade rmcp to 0.14 (#10718)

  - [x] Upgrade rmcp to 0.14

  Matthew Zeng · 2026-02-08 15:07:53 -08:00
  9f1009540b
• Gate view_image tool by model input_modalities (#11051)

  - Plumb input modalities from model catalog through the openai model
  protocol. Default to text and image.
  - Conditionally add the view_image tool only if input modalities support
  image.

  Tom · 2026-02-08 10:45:26 -08:00
  409ec76fbc
• Defer persistence of rollout file (#11028)

  - Defer rollout persistence for fresh threads (`InitialHistory::New`):
  keep rollout events in memory and only materialize rollout file + state
  DB row on first `EventMsg::UserMessage`.
  - Keep precomputed rollout path available before materialization.
  - Change `thread/start` to build thread response from live config
  snapshot and optional precomputed path.
  - Improve pre-materialization behavior in app-server/TUI: clearer
  invalid-request errors for file-backed ops and a friendlier `/fork` “not
  ready yet” UX.
  - Update tests to match deferred semantics across
  start/read/archive/unarchive/fork/resume/review flows.
  - Improved resilience of user_shell test, which should be unrelated to
  this change but must be affected by timing changes
  
  For Reviewers:
  * The primary change is in recorder.rs
  * Most of the other changes were to fix up broken assumptions in
  existing tests
  
  Testing:
  * Manually tested CLI
  * Exercised app server paths by manually running IDE Extension with
  rebuilt CLI binary
  * Only user-visible change is that `/fork` in TUI generates visible
  error if used prior to first turn

  Eric Traut · 2026-02-07 23:05:03 -08:00
  b3de6c7f2b
• Fallback to HTTP on UPGRADE_REQUIRED (#10824)

  Allow the server to trigger a connection downgrade in case the protocol
  changes in incompatible ways.

  pakrym-oai · 2026-02-08 05:06:33 +00:00
  6d08298f4e
• Simplify pre-connect (#11040)
  pakrym-oai · 2026-02-07 15:52:03 -08:00
  8fe5066bcc
• feat(core): add network constraints schema to requirements.toml (#10958)

  ## Summary
  
  Add `requirements.toml` schema support for admin-defined network
  constraints in the requirements layer
  
  example config:
  
  ```
  [experimental_network]
  enabled = true
  allowed_domains = ["api.openai.com"]
  denied_domains = ["example.com"]
  ```

  viyatb-oai · 2026-02-07 19:48:24 +00:00
  739908a12c
• Bootstrap shell commands via user shell snapshot (#10909)

  Summary
  - wrap `shell -lc` executions that use a snapshot with the session shell
  so the saved environment is sourced before delegating to the original
  shell
  - escape single quotes in the generated wrapper and add tests covering
  Bash/Zsh/sh session bootstrapping
  
  Testing
  - Not run (not requested)

  jif-oai · 2026-02-07 17:36:44 +01:00
  83c74125bc
• Add resume_agent collab tool (#10903)

  Summary
  - add the new resume_agent collab tool path through core, protocol, and
  the app server API, including the resume events
  - update the schema/TypeScript definitions plus docs so resume_agent
  appears in generated artifacts and README
  - note that resumed agents rehydrate rollout history without overwriting
  their base instructions
  
  Testing
  - Not run (not requested)

  jif-oai · 2026-02-07 17:31:45 +01:00
  62605fa471
• fix: normalize line endings when reading file on Windows (#10988)

  I did not wait for CI on https://github.com/openai/codex/pull/10980
  because it was blocking an alpha release, but apparently it broken the
  Windows build.

  Michael Bolin · 2026-02-06 23:49:19 -08:00
  4cd0c42a28
• fix: use expected line ending in codex-rs/core/config.schema.json (#10977)

  Fixes a line ending that was altered in https://github.com/openai/codex/pull/10861.
  
  This is breaking the release due to:
  
  https://github.com/openai/codex/blob/a118494323a46c2e7181fb7b0a7c19178fba6578/.github/workflows/rust-release.yml#L54-L55
  
  This PR updates the test to check for this so we should catch it in CI (or when running tests locally):
  
  https://github.com/openai/codex/blob/a118494323a46c2e7181fb7b0a7c19178fba6578/codex-rs/core/src/config/schema.rs#L105-L131

  Michael Bolin · 2026-02-06 22:30:57 -08:00
  18bb25557c
• feat: add support for allowed_web_search_modes in requirements.toml (#10964)

  This PR makes it possible to disable live web search via an enterprise
  config even if the user is running in `--yolo` mode (though cached web
  search will still be available). To do this, create
  `/etc/codex/requirements.toml` as follows:
  
  ```toml
  # "live" is not allowed; "disabled" is allowed even though not listed explicitly.
  allowed_web_search_modes = ["cached"]
  ```
  
  Or set `requirements_toml_base64` MDM as explained on
  https://developers.openai.com/codex/security/#locations.
  
  ### Why
  - Enforce admin/MDM/`requirements.toml` constraints on web-search
  behavior, independent of user config and per-turn sandbox defaults.
  - Ensure per-turn config resolution and review-mode overrides never
  crash when constraints are present.
  
  ### What
  - Add `allowed_web_search_modes` to requirements parsing and surface it
  in app-server v2 `ConfigRequirements` (`allowedWebSearchModes`), with
  fixtures updated.
  - Define a requirements allowlist type (`WebSearchModeRequirement`) and
  normalize semantics:
    - `disabled` is always implicitly allowed (even if not listed).
    - An empty list is treated as `["disabled"]`.
  - Make `Config.web_search_mode` a `Constrained<WebSearchMode>` and apply
  requirements via `ConstrainedWithSource<WebSearchMode>`.
  - Update per-turn resolution (`resolve_web_search_mode_for_turn`) to:
  - Prefer `Live → Cached → Disabled` when
  `SandboxPolicy::DangerFullAccess` is active (subject to requirements),
  unless the user preference is explicitly `Disabled`.
  - Otherwise, honor the user’s preferred mode, falling back to an allowed
  mode when necessary.
  - Update TUI `/debug-config` and app-server mapping to display
  normalized `allowed_web_search_modes` (including implicit `disabled`).
  - Fix web-search integration tests to assert cached behavior under
  `SandboxPolicy::ReadOnly` (since `DangerFullAccess` legitimately prefers
  `live` when allowed).

  Michael Bolin · 2026-02-07 05:55:15 +00:00
  a118494323
• fix(tui): conditionally restore status indicator using message phase (#10947)

  TLDR: use new message phase field emitted by preamble-supported models
  to determine whether an AgentMessage is mid-turn commentary. if so,
  restore the status indicator afterwards to indicate the turn has not
  completed.
  
  ### Problem
  `commit_tick` hides the status indicator while streaming assistant text.
  For preamble-capable models, that text can be commentary mid-turn, so
  hiding was correct during streaming but restore timing mattered:
  - restoring too aggressively caused jitter/flashing
  - not restoring caused indicator to stay hidden before subsequent work
  (tool calls, web search, etc.)
  
  ### Fix
  - Add optional `phase` to `AgentMessageItem` and propagate it from
  `ResponseItem::Message`
  - Keep indicator hidden during streamed commit ticks, restore only when:
    - assistant item completes as `phase=commentary`, and
    - stream queues are idle + task is still running.
  - Treat `phase=None` as final-answer behavior (no restore) to keep
  existing behavior for non-preamble models
  
  ### Tests
  Add/update tests for:
  - no idle-tick restore without commentary completion
  - commentary completion restoring status before tool begin
  - snapshot coverage for preamble/status behavior
  
  ---------
  
  Co-authored-by: Josh McKinney <joshka@openai.com>

  sayan-oai · 2026-02-07 02:39:52 +00:00
  5d2702f6b8
• TUI/Core: preserve duplicate skill/app mention selection across submit + resume (#10855)

  ## What changed
  
  - In `codex-rs/core/src/skills/injection.rs`, we now honor explicit
  `UserInput::Skill { name, path }` first, then fall back to text mentions
  only when safe.
  - In `codex-rs/tui/src/bottom_pane/chat_composer.rs`, mention selection
  is now token-bound (selected mention is tied to the specific inserted
  `$token`), and we snapshot bindings at submit time so selection is not
  lost.
  - In `codex-rs/tui/src/chatwidget.rs` and
  `codex-rs/tui/src/bottom_pane/mod.rs`, submit/queue paths now consume
  the submit-time mention snapshot (instead of rereading cleared composer
  state).
  - In `codex-rs/tui/src/mention_codec.rs` and
  `codex-rs/tui/src/bottom_pane/chat_composer_history.rs`, history now
  round-trips mention targets so resume restores the same selected
  duplicate.
  - In `codex-rs/tui/src/bottom_pane/skill_popup.rs` and
  `codex-rs/tui/src/bottom_pane/chat_composer.rs`, duplicate labels are
  normalized to `[Repo]` / `[App]`, app rows no longer show `Connected -`,
  and description space is a bit wider.
  
  <img width="550" height="163" alt="Screenshot 2026-02-05 at 9 56 56 PM"
  src="https://github.com/user-attachments/assets/346a7eb2-a342-4a49-aec8-68dfec0c7d89"
  />
  <img width="550" height="163" alt="Screenshot 2026-02-05 at 9 57 09 PM"
  src="https://github.com/user-attachments/assets/5e04d9af-cccf-4932-98b3-c37183e445ed"
  />
  
  
  ## Before vs now
  
  - Before: selecting a duplicate could still submit the default/repo
  match, and resume could lose which duplicate was originally selected.
  - Now: the exact selected target (skill path or app id) is preserved
  through submit, queue/restore, and resume.
  
  ## Manual test
  
  1. Build and run this branch locally:
     - `cd /Users/daniels/code/codex/codex-rs`
     - `cargo build -p codex-cli --bin codex`
     - `./target/debug/codex`
  2. Open mention picker with `$` and pick a duplicate entry (not the
  first one).
  3. Confirm duplicate UI:
     - repo duplicate rows show `[Repo]`
     - app duplicate rows show `[App]`
     - app description does **not** start with `Connected -`
  4. Submit the prompt, then press Up to restore draft and submit again.  
     Expected: it keeps the same selected duplicate target.
  5. Use `/resume` to reopen the session and send again.  
  Expected: restored mention still resolves to the same duplicate target.

  daniel-oai · 2026-02-06 15:59:00 -08:00
  84bce2b8e6
• add originator to otel (#10826)
  alexsong-oai · 2026-02-06 15:13:56 -08:00
  daeef06bec
• Support alternative websocket API (#10861)

  **Test plan**
  
  ```
  cargo build -p codex-cli && RUST_LOG='codex_api::endpoint::responses_websocket=trace,codex_core::client=debug,codex_core::codex=debug' \
    ./target/debug/codex \
      --enable responses_websockets_v2 \
      --profile byok \
      --full-auto
  ```

  Brian Yu · 2026-02-06 14:40:50 -08:00
  1fbf5ed06f
• Treat compaction failure as failure state (#10927)

  - Return compaction errors from local and remote compaction flows.\n-
  Stop turns/tasks when auto-compaction fails instead of continuing
  execution.

  Ahmed Ibrahim · 2026-02-06 13:51:46 -08:00
  ba8b5d9018
• core: refresh developer instructions after compaction replacement history (#10574)

  ## Summary
  
  When replaying compacted history (especially `replacement_history` from
  remote compaction), we should not keep stale developer messages from
  older session state. This PR trims developer-
  role messages from compacted replacement history and reinjects fresh
  developer instructions derived from current turn/session state.
  
  This aligns compaction replay behavior with the intended "fresh
  instructions after summary" model.
  
  ## Problem
  
  Compaction replay had two paths:
  
  - `Compacted { replacement_history: None }`: rebuilt with fresh initial
  context
  - `Compacted { replacement_history: Some(...) }`: previously used raw
  replacement history as-is
  
  The second path could carry stale developer instructions
  (permissions/personality/collab-mode guidance) across session changes.
  
  ## What Changed
  
  ### 1) Added helper to refresh compacted developer instructions
  
  - **File:** `codex-rs/core/src/compact.rs`
  - **Function:** `refresh_compacted_developer_instructions(...)`
  
  Behavior:
  - remove all `ResponseItem::Message { role: "developer", .. }` from
  compacted history
  - append fresh developer messages from current
  `build_initial_context(...)`
  
  ### 2) Applied helper in remote compaction flow
  
  - **File:** `codex-rs/core/src/compact_remote.rs`
  - After receiving compact endpoint output, refresh developer
  instructions before replacing history and persisting
  `replacement_history`.
  
  ### 3) Applied helper while reconstructing history from rollout
  
  - **File:** `codex-rs/core/src/codex.rs`
  - In `reconstruct_history_from_rollout(...)`, when processing
  `Compacted` entries with `replacement_history`, refresh developer
  instructions instead of directly replacing with raw history.
  
  ## Non-Goals / Follow-up
  
  This PR does **not** address the existing first-turn-after-resume
  double-injection behavior.
  A follow-up PR will handle resume-time dedup/idempotence separately.
  
  If you want, I can also give you a shorter “squash-merge friendly”
  version of the description.
  
  ## Codex author
  `codex fork 019c25e6-706e-75d1-9198-688ec00a8256`

  Charley Cunningham · 2026-02-06 12:25:08 -08:00
  143daadb31
• core: preconnect Responses websocket for first turn (#10698)

  ## Problem
  The first user turn can pay websocket handshake latency even when a
  session has already started. We want to reduce that initial delay while
  preserving turn semantics and avoiding any prompt send during startup.
  
  Reviewer feedback also called out duplicated connect/setup paths and
  unnecessary preconnect state complexity.
  
  ## Mental model
  `ModelClient` owns session-scoped transport state. During session
  startup, it can opportunistically warm one websocket handshake slot. A
  turn-scoped `ModelClientSession` adopts that slot once if available,
  restores captured sticky turn-state, and otherwise opens a websocket
  through the same shared connect path.
  
  If startup preconnect is still in flight, first turn setup awaits that
  task and treats it as the first connection attempt for the turn.
  
  Preconnect is handshake-only. The first `response.create` is still sent
  only when a turn starts.
  
  ## Non-goals
  This change does not make preconnect required for correctness and does
  not change prompt/turn payload semantics. It also does not expand
  fallback behavior beyond clearing preconnect state when fallback
  activates.
  
  ## Tradeoffs
  The implementation prioritizes simpler ownership and shared connection
  code over header-match gating for reuse. The single-slot cache keeps
  lifecycle straightforward but only benefits the immediate next turn.
  
  Awaiting in-flight preconnect has the same app-level connect-timeout
  semantics as existing websocket connect behavior (no new timeout class
  introduced by this PR).
  
  ## Architecture
  `core/src/client.rs`:
  - Added session-level preconnect lifecycle state (`Idle` / `InFlight` /
  `Ready`) carrying one warmed websocket plus optional captured
  turn-state.
  - Added `pre_establish_connection()` startup warmup and `preconnect()`
  handshake-only setup.
  - Deduped auth/provider resolution into `current_client_setup()` and
  websocket handshake wiring into `connect_websocket()` /
  `build_websocket_headers()`.
  - Updated turn websocket path to adopt preconnect first, await in-flight
  preconnect when present, then create a new websocket only when needed.
  - Ensured fallback activation clears warmed preconnect state.
  - Added documentation for lifecycle, ownership, sticky-routing
  invariants, and timeout semantics.
  
  `core/src/codex.rs`:
  - Session startup invokes `model_client.pre_establish_connection(...)`.
  - Turn metadata resolution uses the shared timeout helper.
  
  `core/src/turn_metadata.rs`:
  - Centralized shared timeout helper used by both turn-time metadata
  resolution and startup preconnect metadata building.
  
  `core/tests/common/responses.rs` + websocket test suites:
  - Added deterministic handshake waiting helper (`wait_for_handshakes`)
  with bounded polling.
  - Added startup preconnect and in-flight preconnect reuse coverage.
  - Fallback expectations now assert exactly two websocket attempts in
  covered scenarios (startup preconnect + turn attempt before fallback
  sticks).
  
  ## Observability
  Preconnect remains best-effort and non-fatal. Existing
  websocket/fallback telemetry remains in place, and debug logs now make
  preconnect-await behavior and preconnect failures easier to reason
  about.
  
  ## Tests
  Validated with:
  1. `just fmt`
  2. `cargo test -p codex-core websocket_preconnect -- --nocapture`
  3. `cargo test -p codex-core websocket_fallback -- --nocapture`
  4. `cargo test -p codex-core
  websocket_first_turn_waits_for_inflight_preconnect -- --nocapture`

  Josh McKinney · 2026-02-06 19:08:24 +00:00
  e416e578bb
• Add app configs to config.toml (#10822)

  Adds app configs to config.toml + tests

  canvrno-oai · 2026-02-06 10:29:08 -08:00
  36c16e0c58
• Removed "exec_policy" feature flag (#10851)

  This is no longer needed because it's on by default

  Eric Traut · 2026-02-06 08:59:47 -08:00
  4521a6e852
• Handle required MCP startup failures across components (#10902)

  Summary
  - add a `required` flag for MCP servers everywhere config/CLI data is
  touched so mandatory helpers can be round-tripped
  - have `codex exec` and `codex app-server` thread start/resume fail fast
  when required MCPs fail to initialize

  jif-oai · 2026-02-06 17:14:37 +01:00
  aab61934af