249 Commits

• feat: make sandbox read access configurable with ReadOnlyAccess (#11387)

  `SandboxPolicy::ReadOnly` previously implied broad read access and could
  not express a narrower read surface.
  This change introduces an explicit read-access model so we can support
  user-configurable read restrictions in follow-up work, while preserving
  current behavior today.
  
  It also ensures unsupported backends fail closed for restricted-read
  policies instead of silently granting broader access than intended.
  
  ## What
  
  - Added `ReadOnlyAccess` in protocol with:
    - `Restricted { include_platform_defaults, readable_roots }`
    - `FullAccess`
  - Updated `SandboxPolicy` to carry read-access configuration:
    - `ReadOnly { access: ReadOnlyAccess }`
    - `WorkspaceWrite { ..., read_only_access: ReadOnlyAccess }`
  - Preserved existing behavior by defaulting current construction paths
  to `ReadOnlyAccess::FullAccess`.
  - Threaded the new fields through sandbox policy consumers and call
  sites across `core`, `tui`, `linux-sandbox`, `windows-sandbox`, and
  related tests.
  - Updated Seatbelt policy generation to honor restricted read roots by
  emitting scoped read rules when full read access is not granted.
  - Added fail-closed behavior on Linux and Windows backends when
  restricted read access is requested but not yet implemented there
  (`UnsupportedOperation`).
  - Regenerated app-server protocol schema and TypeScript artifacts,
  including `ReadOnlyAccess`.
  
  ## Compatibility / rollout
  
  - Runtime behavior remains unchanged by default (`FullAccess`).
  - API/schema changes are in place so future config wiring can enable
  restricted read access without another policy-shape migration.

  Michael Bolin · 2026-02-11 18:31:14 -08:00
  abbd74e2be
• Promote Windows Sandbox (#11341)

  1. Move Windows Sandbox NUX to right after trust directory screen
  2. Don't offer read-only as an option in Sandbox NUX.
  Elevated/Legacy/Quit
  3. Don't allow new untrusted directories. It's trust or quit
  4. move experimental sandbox features to `[windows]
  sandbox="elevated|unelevatd"`
  5. Copy tweaks = elevated -> default, non-elevated -> non-admin

  iceweasel-oai · 2026-02-11 11:48:33 -08:00
  87279de434
• Remove test-support feature from codex-core and replace it with explicit test toggles (#11405)

  ## Why
  
  `codex-core` was being built in multiple feature-resolved permutations
  because test-only behavior was modeled as crate features. For a large
  crate, those permutations increase compile cost and reduce cache reuse.
  
  ## Net Change
  
  - Removed the `test-support` crate feature and related feature wiring so
  `codex-core` no longer needs separate feature shapes for test consumers.
  - Standardized cross-crate test-only access behind
  `codex_core::test_support`.
  - External test code now imports helpers from
  `codex_core::test_support`.
  - Underlying implementation hooks are kept internal (`pub(crate)`)
  instead of broadly public.
  
  ## Outcome
  
  - Fewer `codex-core` build permutations.
  - Better incremental cache reuse across test targets.
  - No intended production behavior change.

  Michael Bolin · 2026-02-10 22:44:02 -08:00
  476c1a7160
• tui: queue non-pending rollback trims in app-event order (#11373)

  ## Summary
  
  This PR fixes TUI transcript-sync behavior for
  `EventMsg::ThreadRolledBack` and makes rollback application order
  deterministic.
  
  Previously, rollback handling depended on `pending_rollback`:
  
  - if `pending_rollback` was set (local backtrack), TUI trimmed correctly
  - otherwise, replayed/external rollbacks were either ignored or could be
  applied at the wrong time relative to queued transcript inserts
  
  This change keeps the local backtrack path intact and routes non-pending
  rollbacks through the app event queue so rollback trims are applied in
  FIFO order with transcript cell inserts.
  
  ## What changed
  
  - Added/used `trim_transcript_cells_drop_last_n_user_turns(...)` for
  rollback-by-`num_turns` semantics.
  - Renamed rollback app event:
  - `AppEvent::ApplyReplayedThreadRollback` ->
  `AppEvent::ApplyThreadRollback`
  - Replay path (`ChatWidget`) now emits `ApplyThreadRollback`.
  - Live non-pending rollback path (`App::handle_backtrack_event`) now
  emits `ApplyThreadRollback` instead of trimming immediately.
  - App-level event handler applies `ApplyThreadRollback` after queued
  `InsertHistoryCell` events and schedules redraw only when a trim
  occurred.
  - When a trim occurs with an overlay open, TUI now syncs transcript
  overlay committed cells, clamps backtrack preview selection, and clears
  stale `deferred_history_lines` so closed overlays do not re-append
  rolled-back lines.
  - Clarified inline comments around the `pending_rollback` branch so
  future readers can reason about why there are two paths.
  
  ## Why queueing matters
  
  During resume/replay, transcript cells are populated via queued
  `InsertHistoryCell` app events. If a rollback is applied immediately
  outside that queue, it can run against an incomplete transcript and
  under-trim. Queueing non-pending rollbacks ensures consistent ordering
  and correct final transcript state.
  
  ## Behavior by rollback source
  
  - `pending_rollback = Some(...)` (local backtrack requested by this
  TUI):
    - use `finish_pending_backtrack()` and the stored selection boundary
  - `pending_rollback = None` (replay/external/non-local rollback):
  - enqueue `AppEvent::ApplyThreadRollback { num_turns }` and trim in
  app-event order
  
  ## Tests
  
  Added/updated tests covering ordering and semantics:
  
  -
  `app_backtrack::tests::trim_drop_last_n_user_turns_applies_rollback_semantics`
  - `app_backtrack::tests::trim_drop_last_n_user_turns_allows_overflow`
  - `app::tests::replayed_initial_messages_apply_rollback_in_queue_order`
  -
  `app::tests::live_rollback_during_replay_is_applied_in_app_event_order`
  -
  `app::tests::queued_rollback_syncs_overlay_and_clears_deferred_history`
  - `chatwidget::tests::replayed_thread_rollback_emits_ordered_app_event`
  
  Validation run:
  
  - `just fmt`
  - `cargo test -p codex-tui`

  Charley Cunningham · 2026-02-10 18:53:43 -08:00
  8b46c0ce00
• fix: reduce usage of open_if_present (#11344)
  jif-oai · 2026-02-10 19:25:07 +00:00
  847a6092e6
• [apps] Improve app installation flow. (#11249)

  - [x] Add buttons to start the installation flow and verify installation
  completes.
  - [x] Hard refresh apps list when the /apps view opens.

  Matthew Zeng · 2026-02-10 17:59:43 +00:00
  48e415bdef
• feat: retain NetworkProxy, when appropriate (#11207)

  As of this PR, `SessionServices` retains a
  `Option<StartedNetworkProxy>`, if appropriate.
  
  Now the `network` field on `Config` is `Option<NetworkProxySpec>`
  instead of `Option<NetworkProxy>`.
  
  Over in `Session::new()`, we invoke `NetworkProxySpec::start_proxy()` to
  create the `StartedNetworkProxy`, which is a new struct that retains the
  `NetworkProxy` as well as the `NetworkProxyHandle`. (Note that `Drop` is
  implemented for `NetworkProxyHandle` to ensure the proxies are shutdown
  when it is dropped.)
  
  The `NetworkProxy` from the `StartedNetworkProxy` is threaded through to
  the appropriate places.
  
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/11207).
  * #11285
  * __->__ #11207

  Michael Bolin · 2026-02-10 02:09:23 -08:00
  44ebf4588f
• fix: do not show closed agents in /agent (#11175)
  jif-oai · 2026-02-09 11:25:31 +00:00
  13de744296
• [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
• 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
• add originator to otel (#10826)
  alexsong-oai · 2026-02-06 15:13:56 -08:00
  daeef06bec
• Add analytics for /rename and /fork (#10655)
  pap-openai · 2026-02-05 20:18:29 +00:00
  529b539564
• fix(auth): isolate chatgptAuthTokens concept to auth manager and app-server (#10423)

  So that the rest of the codebase (like TUI) don't need to be concerned
  whether ChatGPT auth was handled by Codex itself or passed in via
  app-server's external auth mode.

  Owen Lin · 2026-02-05 10:46:06 -08:00
  3582b74d01
• feat(tui): add /statusline command for interactive status line configuration (#10546)

  ## Summary
  - Adds a new `/statusline` command to configure TUI footer status line
  - Introduces reusable `MultiSelectPicker` component with keyboard
  navigation, optional ordering and toggle support
  - Implement status line setup modal that persist configuration to
  config.toml
  
    ## Status Line Items
    The following items can be displayed in the status line:
    - **Model**: Current model name (with optional reasoning level)
    - **Context**: Remaining/used context window percentage
    - **Rate Limits**: 5-day and weekly usage limits
    - **Git**: Current branch (with optimized lookups)
    - **Tokens**: Used tokens, input/output token counts
    - **Session**: Session ID (full or shortened prefix)
    - **Paths**: Current directory, project root
    - **Version**: Codex version
  
    ## Features
    - Live preview while configuring status line items
    - Fuzzy search filtering in the picker
    - Intelligent truncation when items don't fit
    - Items gracefully omit when data is unavailable
    - Configuration persists to `config.toml`
    - Validates and warns about invalid status line items
  
    ## Test plan
    - [x] Run `/statusline` and verify picker UI appears
    - [x] Toggle items on/off and verify live preview updates
    - [x] Confirm selection persists after restart
    - [x] Verify truncation behavior with many items selected
    - [x] Test git branch detection in and out of git repos
  
  ---------
  
  Co-authored-by: Josh McKinney <joshka@openai.com>

  Felipe Coury · 2026-02-05 08:50:21 -08:00
  b0e5a6305b
• adding fork information (UI) when forking (#10246)

  - shows `/fork` command that ran in prev session
  - shows `session forked from name (uuid) || uuid (if name is not set)` as an event in new session

  pap-openai · 2026-02-05 13:24:55 +00:00
  b2424cb635
• add none personality option (#10688)

  - add none personality enum value and empty placeholder behavior\n- add
  docs/schema updates and e2e coverage

  Ahmed Ibrahim · 2026-02-04 15:40:33 -08:00
  f9c38f531c
• feat(tui): pace catch-up stream chunking with hysteresis (#10461)

  ## Summary
  - preserve baseline streaming behavior (smooth mode still commits one
  line per 50ms tick)
  - extract adaptive chunking policy and commit-tick orchestration from
  ChatWidget into `streaming/chunking.rs` and `streaming/commit_tick.rs`
  - add hysteresis-based catch-up behavior with bounded batch draining to
  reduce queue lag without bursty single-frame jumps
  - document policy behavior, tuning guidance, and debug flow in rustdoc +
  docs
  
  ## Testing
  - just fmt
  - cargo test -p codex-tui

  Josh McKinney · 2026-02-03 15:01:51 -08:00
  aec58ac29b
• chore: nuke chat/completions API (#10157)
  jif-oai · 2026-02-03 11:31:57 +00:00
  d2394a2494
• emit a separate metric when the user cancels UAT during elevated setup (#10399)

  Currently this shows up as elevated setup failure, which isn't quite
  accurate.

  iceweasel-oai · 2026-02-02 15:31:08 -08:00
  a5066bef78
• Add credits tooltip (#10274)
  pakrym-oai · 2026-02-02 10:06:43 -08:00
  9d976962ec
• chore(config) Rename config setting to personality (#10314)

  ## Summary
  Let's make the setting name consistent with the SlashCommand!
  
  ## Testing
  - [x] Updated tests

  Dylan Hurd · 2026-01-31 19:38:06 -08:00
  a33fa4bfe5
• fix: update file search directory when session CWD changes (#9279)

  ## Summary
  
  Fixes #9041
  
  - Adds update_search_dir() method to FileSearchManager to allow updating
  the search directory after initialization
  - Calls this method when the session CWD changes: new session, resume,
  or fork
  
  ## Problem
  
  The FileSearchManager was created once with the initial search_dir and
  never updated. When a user:
  
  1. Starts Codex in a non-git directory (e.g., /tmp/random)
  2. Resumes or forks a session from a different workspace
  3. The @filename lookup still searched the original directory
  
  This caused no matches to be returned even when files existed in the
  current workspace.
  
  ## Solution
  
  Update FileSearchManager.search_dir whenever the session working
  directory changes:
  - AppEvent::NewSession: Use current config CWD
  - SessionSelection::Resume: Use resumed session CWD
  - SessionSelection::Fork: Use forked session CWD
  
  ## Test plan
  
  - [ ] Start Codex in /tmp/test-dir (non-git)
  - [ ] Resume a session from a project with actual files
  - [ ] Verify @filename returns matches from the resumed session
  directory
  
  ---------
  
  Co-authored-by: Eric Traut <etraut@openai.com>

  Yuvraj Angad Singh · 2026-01-30 14:59:20 -08:00
  13e85b1549
• Fix deploy (#10251)

  Fix
  https://github.com/openai/codex/actions/runs/21527697445/job/62035898666

  Charley Cunningham · 2026-01-30 11:57:13 -08:00
  2457bb3c40
• feat: refactor CodexAuth so invalid state cannot be represented (#10208)

  Previously, `CodexAuth` was defined as follows:
  
  
  https://github.com/openai/codex/blob/d550fbf41afc09d7d7b5ac813aea38de07b2a73f/codex-rs/core/src/auth.rs#L39-L46
  
  But if you looked at its constructors, we had creation for
  `AuthMode::ApiKey` where `storage` was built using a nonsensical path
  (`PathBuf::new()`) and `auth_dot_json` was `None`:
  
  
  https://github.com/openai/codex/blob/d550fbf41afc09d7d7b5ac813aea38de07b2a73f/codex-rs/core/src/auth.rs#L212-L220
  
  By comparison, when `AuthMode::ChatGPT` was used, `api_key` was always
  `None`:
  
  
  https://github.com/openai/codex/blob/d550fbf41afc09d7d7b5ac813aea38de07b2a73f/codex-rs/core/src/auth.rs#L665-L671
  
  https://github.com/openai/codex/pull/10012 took things further because
  it introduced a new `ChatgptAuthTokens` variant to `AuthMode`, which is
  important in when invoking `account/login/start` via the app server, but
  most logic _internal_ to the app server should just reason about two
  `AuthMode` variants: `ApiKey` and `ChatGPT`.
  
  This PR tries to clean things up as follows:
  
  - `LoginAccountParams` and `AuthMode` in `codex-rs/app-server-protocol/`
  both continue to have the `ChatgptAuthTokens` variant, though it is used
  exclusively for the on-the-wire messaging.
  - `codex-rs/core/src/auth.rs` now has its own `AuthMode` enum, which
  only has two variants: `ApiKey` and `ChatGPT`.
  - `CodexAuth` has been changed from a struct to an enum. It is a
  disjoint union where each variant (`ApiKey`, `ChatGpt`, and
  `ChatGptAuthTokens`) have only the associated fields that make sense for
  that variant.
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/10208).
  * #10224
  * __->__ #10208

  Michael Bolin · 2026-01-30 09:33:23 -08:00
  377ab0c77c
• Conversation naming (#8991)

  Session renaming:
  - `/rename my_session`
  - `/rename` without arg and passing an argument in `customViewPrompt`
  - AppExitInfo shows resume hint using the session name if set instead of
  uuid, defaults to uuid if not set
  - Names are stored in `CODEX_HOME/sessions.jsonl`
  
  Session resuming:
  - codex resume <name> lookup for `CODEX_HOME/sessions.jsonl` first entry
  matching the name and resumes the session
  
  ---------
  
  Co-authored-by: jif-oai <jif@openai.com>

  pap-openai · 2026-01-30 10:40:09 +00:00
  1ef5455eb6
• feat(tui): route employee feedback follow-ups to internal link (#10198)

  ## Problem
  OpenAI employees were sent to the public GitHub issue flow after
  `/feedback`, which is the wrong follow-up path internally.
  
  ## Mental model
  After feedback upload completes, we render a follow-up link/message.
  That link should be audience-aware but must not change the upload
  pipeline itself.
  
  ## Non-goals
  - Changing how feedback is captured or uploaded
  - Changing external user behavior
  
  ## Tradeoffs
  We detect employees via the authenticated account email suffix
  (`@openai.com`). If the email is unavailable (e.g., API key auth), we
  default to the external behavior.
  
  ## Architecture
  - Introduce `FeedbackAudience` and thread it from `App` -> `ChatWidget`
  -> `FeedbackNoteView`
  - Gate internal messaging/links on `FeedbackAudience::OpenAiEmployee`
  - Internal follow-up link is now `http://go/codex-feedback-internal`
  - External GitHub URL remains byte-for-byte identical
  
  ## Observability
  No new telemetry; this only changes rendered follow-up instructions.
  
  ## Tests
  - `just fmt`
  - `cargo test -p codex-tui --lib`

  Josh McKinney · 2026-01-30 02:12:46 +00:00
  36f2fe8af9
• [connectors] Support connectors part 2 - slash command and tui (#9728)

  - [x] Support `/apps` slash command to browse the apps in tui.
  - [x] Support inserting apps to prompt using `$`.
  - [x] Lots of simplification/renaming from connectors to apps.

  Matthew Zeng · 2026-01-28 19:51:58 -08:00
  b9cd089d1f
• Added tui.notifications_method config option (#10043)

  This PR adds a new `tui.notifications_method` config option that accepts
  values of "auto", "osc9" and "bel". It defaults to "auto", which
  attempts to auto-detect whether the terminal supports OSC 9 escape
  sequences and falls back to BEL if not.
  
  The PR also removes the inconsistent handling of notifications on
  Windows when WSL was used.

  Eric Traut · 2026-01-28 12:00:32 -08:00
  147e7118e0
• allow elevated sandbox to be enabled without base experimental flag (#10028)

  elevated flag = elevated sandbox
  experimental flag = non-elevated sandbox
  both = elevated

  iceweasel-oai · 2026-01-28 11:38:29 -08:00
  66de985e4e
• file-search: improve file query perf (#9939)

  switch nucleo-matcher for nucleo and use a "file search session" w/ live
  updating query instead of a single hermetic run per query.

  Jeremy Rose · 2026-01-28 10:54:43 -08:00
  b8156706e6
• error code/msg details for failed elevated setup (#9941)
  iceweasel-oai · 2026-01-27 23:06:10 -08:00
  9f79365691
• Clarify external editor env var message (#10030)

  ### Motivation
  - Improve UX by making it explicit that `VISUAL`/`EDITOR` must be set
  before launching Codex, not during a running session.
  
  ### Description
  - Update the external editor error text in `codex-rs/tui/src/app.rs` to:
  `"Cannot open external editor: set $VISUAL or $EDITOR before starting
  Codex."` and run `just fmt` to apply formatting.
  
  ### Testing
  - Ran `just fmt` successfully; attempted `cargo test -p codex-tui` but
  it failed due to network errors when fetching git dependencies (tests
  did not complete).
  
  ------
  [Codex
  Task](https://chatgpt.com/codex/tasks/task_i_6972c2c984948329b1a37d5c5839aff3)

  Josh McKinney · 2026-01-27 13:29:55 -08:00
  3ae966edd8
• remove sandbox globals. (#9797)

  Threads sandbox updates through OverrideTurnContext for active turn
  Passes computed sandbox type into safety/exec

  iceweasel-oai · 2026-01-27 11:04:23 -08:00
  c40ad65bd8
• NIT larger buffer (#9957)
  jif-oai · 2026-01-27 01:26:55 +00:00
  5d13427ef4
• fix: try to fix freezes 2 (#9951)

  Fixes a TUI freeze caused by awaiting `mpsc::Sender::send()` that blocks
  the tokio thread, stopping the consumption runtime and creating a
  deadlock. This could happen if the server was producing enough chunks to
  fill the `mpsc` fast enough. To solve this we try on insert using a
  `try_send()` (not requiring an `await`) and delegate to a tokio task if
  this does not work
  
  This is a temporary solution as it can contain races for delta elements
  and a stronger design should come here

  jif-oai · 2026-01-27 01:02:22 +00:00
  73bd84dee0
• Fix up config disabled err msg (#9916)

  **Before:**
  <img width="745" height="375" alt="image"
  src="https://github.com/user-attachments/assets/d6c23562-b87f-4af9-8642-329aab8e594d"
  />
  
  **After:**
  <img width="1042" height="354" alt="image"
  src="https://github.com/user-attachments/assets/c9a2413c-c945-4c34-8b7e-c6c9b8fbf762"
  />
  
  Two changes:
  1. only display if there is a `config.toml` that is skipped (i.e. if
  there is just `.codex/skills` but no `.codex/config.toml` we do not
  display the error)
  2. clarify the implications and the fix in the error message.

  gt-oai · 2026-01-26 17:49:31 +00:00
  6316e57497
• feat: rebase multi-agent tui on config_snapshot (#9818)
  jif-oai · 2026-01-26 10:18:47 +00:00
  c66662c61b
• feat(tui) /personality (#9718)

  ## Summary
  Adds /personality selector in the TUI, which leverages the new core
  interface in #9644
  
  Notes:
  - We are doing some of our own state management for model_info loading
  here, but not sure if that's ideal. open to opinions on simpler
  approach, but would like to avoid blocking on a larger refactor
  - Right now, the `/personality` selector just hides when the model
  doesn't support it. we can update this behavior down the line
  
  ## Testing
  - [x] Tested locally
  - [x] Added snapshot tests

  Dylan Hurd · 2026-01-25 21:59:42 -08:00
  031bafd1fb
• Use collaboration mode masks without mutating base settings (#9806)

  Keep an unmasked base collaboration mode and apply the active mask on
  demand. Simplify the TUI mask helpers and update tests/docs to match the
  mask contract.

  Ahmed Ibrahim · 2026-01-25 07:35:31 +00:00
  58450ba2a1
• Ask for cwd choice when resuming session from different cwd (#9731)

  # Summary
  - Fix resume/fork config rebuild so cwd changes inside the TUI produce a
  fully rebuilt Config (trust/approval/sandbox) instead of mutating only
  the cwd.
  - Preserve `--add-dir` behavior across resume/fork by normalizing
  relative roots to absolute paths once (based on the original cwd).
  - Prefer latest `TurnContext.cwd` for resume/fork prompts but fall back
  to `SessionMeta.cwd` if the latest cwd no longer exists.
  - Align resume/fork selection handling and ensure UI config matches the
  resumed thread config.
  - Fix Windows test TOML path escaping in trust-level test.
  
  # Details
  - Rebuild Config via `ConfigBuilder` when resuming into a different cwd;
  carry forward runtime approval/sandbox overrides.
  - Add `normalize_harness_overrides_for_cwd` to resolve relative
  `additional_writable_roots` against the initial cwd before reuse.
  - Guard `read_session_cwd` with filesystem existence check for the
  latest `TurnContext.cwd`.
  - Update naming/flow around cwd comparison and prompt selection.
  
  <img width="603" height="150" alt="Screenshot 2026-01-23 at 5 42 13 PM"
  src="https://github.com/user-attachments/assets/d1897386-bb28-4e8a-98cf-187fdebbecb0"
  />
  
  And proof the model understands the new cwd:
  
  <img width="828" height="353" alt="Screenshot 2026-01-22 at 5 36 45 PM"
  src="https://github.com/user-attachments/assets/12aed8ca-dec3-4b64-8dae-c6b8cff78387"
  />

  Charley Cunningham · 2026-01-24 21:57:19 -08:00
  18acec09df
• feat: ephemeral threads (#9765)

  Add ephemeral threads capabilities. Only exposed through the
  `app-server` v2
  
  The idea is to disable the rollout recorder for those threads.

  jif-oai · 2026-01-24 14:57:40 +00:00
  83775f4df1
• Chore: remove mode from header (#9792)
  Ahmed Ibrahim · 2026-01-23 22:38:17 +00:00
  1167465bf6
• Print warning if we skip config loading (#9611)

  https://github.com/openai/codex/pull/9533 silently ignored config if
  untrusted. Instead, we still load it but disable it. Maybe we shouldn't
  try to parse it either...
  
  <img width="939" height="515" alt="Screenshot 2026-01-21 at 14 56 38"
  src="https://github.com/user-attachments/assets/e753cc22-dd99-4242-8ffe-7589e85bef66"
  />

  gt-oai · 2026-01-23 20:06:37 +00:00
  7938c170d9
• Persist text element ranges and attached images across history/resume (#9116)

  **Summary**
  - Backtrack selection now rehydrates `text_elements` and
  `local_image_paths` from the chosen user history cell so Esc‑Esc history
  edits preserve image placeholders and attachments.
  - Composer prefill uses the preserved elements/attachments in both `tui`
  and `tui2`.
  - Extended backtrack selection tests to cover image placeholder elements
  and local image paths.
  
  **Changes**
  - `tui/src/app_backtrack.rs`: Backtrack selection now carries text
  elements + local image paths; composer prefill uses them (removes TODO).
  - `tui2/src/app_backtrack.rs`: Same as above.
  - `tui/src/app.rs`: Updated backtrack test to assert restored
  elements/paths.
  - `tui2/src/app.rs`: Same test updates.
  
  ### The original scope of this PR (threading text elements and image
  attachments through the codex harness thoroughly/persistently) was
  broken into the following PRs other than this one:
  
  The diff of this PR was reduced by changing types in a starter PR:
  https://github.com/openai/codex/pull/9235
  
  Then text element metadata was added to protocol, app server, and core
  in this PR: https://github.com/openai/codex/pull/9331
  
  Then the end-to-end flow was completed by wiring TUI/TUI2 input,
  history, and restore behavior in
  https://github.com/openai/codex/pull/9393
  
  Prompt expansion was supported in this PR:
  https://github.com/openai/codex/pull/9518
  
  TextElement optional placeholder field was protected in
  https://github.com/openai/codex/pull/9545

  charley-oai · 2026-01-23 10:18:19 -08:00
  935d88b455
• feat: tui beta for collab (#9690)

  https://github.com/user-attachments/assets/1ca07e7a-3d82-40da-a5b0-8ab2eef0bb69

  jif-oai · 2026-01-23 13:57:59 +01:00
  f30f39b28b
• TUI: prompt to implement plan and switch to Execute (#9712)

  ## Summary
  - Replace the plan‑implementation prompt with a standard selection
  popup.
  - “Yes” submits a user turn in Execute via a dedicated app event to
  preserve normal transcript behavior.
  - “No” simply dismisses the popup.
  
  <img width="977" height="433" alt="Screenshot 2026-01-22 at 2 00 54 PM"
  src="https://github.com/user-attachments/assets/91fad06f-7b7a-4cd8-9051-f28a19b750b2"
  />
  
  ## Changes
  - Add a plan‑implementation popup using `SelectionViewParams`.
  - Add `SubmitUserMessageWithMode` so “Yes” routes through
  `submit_user_message` (ensures user history + separator state).
  - Track `saw_plan_update_this_turn` so the prompt appears even when only
  `update_plan` is emitted.
  - Suppress the plan popup on replayed turns, when messages are queued,
  or when a rate‑limit prompt is pending.
  - Add `execute_mode` helper for collaboration modes.
  - Add tests for replay/queued/rate‑limit guards and plan update without
  final message.
  - Add snapshots for both the default and “No”‑selected popup states.

  charley-oai · 2026-01-23 00:25:50 +00:00
  0e79d239ed
• feat(core) update Personality on turn (#9644)

  ## Summary
  Support updating Personality mid-Thread via UserTurn/OverwriteTurn. This
  is explicitly unused by the clients so far, to simplify PRs - app-server
  and tui implementations will be follow-ups.
  
  ## Testing
  - [x] added integration tests

  Dylan Hurd · 2026-01-22 12:04:23 -08:00
  8b3521ee77
• feat(tui) /permissions flow (#9561)

  ## Summary
  Adds the `/permissions` command, with a (usually) shorter set of
  permissions. `/approvals` still exists, for backwards compatibility.
  
  <img width="863" height="309" alt="Screenshot 2026-01-20 at 4 12 51 PM"
  src="https://github.com/user-attachments/assets/c49b5ba5-bc47-46dd-9067-e1a5670328fe"
  />
  
  
  ## Testing
  - [x] updated unit tests
  - [x] Tested locally

  Dylan Hurd · 2026-01-21 21:38:46 -08:00
  038b78c915
• Add UI for skill enable/disable. (#9627)

  "/skill" will now allow you to enable/disable skills:
  <img width="658" height="199" alt="image"
  src="https://github.com/user-attachments/assets/bf8994c8-d6c1-462f-8bbb-f1ee9241caa4"
  />

  xl-openai · 2026-01-21 18:21:12 -08:00
  577ba3a4ca
• define/emit some metrics for windows sandbox setup (#9573)

  This should give us visibility into how users are using the elevated
  sandbox nux flow, and the timing of the elevated setup.

  iceweasel-oai · 2026-01-21 11:07:26 -08:00
  f81dd128a2