264 Commits

• Reuse ChatComposer in request_user_input overlay (#9892)

  Reuse the shared chat composer for notes and freeform answers in
  request_user_input.
  
  - Build the overlay composer with ChatComposerConfig::plain_text.
  - Wire paste-burst flushing + menu surface sizing through the bottom
  pane.

  Ahmed Ibrahim · 2026-01-26 17:21:41 -08:00
  394b967432
• Add composer config and shared menu surface helpers (#9891)

  Centralize built-in slash-command gating and extract shared menu-surface
  helpers.
  
  - Add bottom_pane::slash_commands and reuse it from composer + command
  popup.
  - Introduce ChatComposerConfig + shared menu surface rendering without
  changing default behavior.

  Ahmed Ibrahim · 2026-01-26 23:16:29 +00:00
  a8f195828b
• Aligned feature stage names with public feature maturity stages (#9929)

  We've recently standardized a [feature maturity
  model](https://developers.openai.com/codex/feature-maturity) that we're
  using in our docs and support forums to communicate expectations to
  users. This PR updates the internal stage names and descriptions to
  match.
  
  This change involves a simple internal rename and updates to a few
  user-visible strings. No functional change.

  Eric Traut · 2026-01-26 11:43:36 -08:00
  b77bf4d36d
• Feat: add isOther to question returned by request user input tool (#9890)

  ### Summary
  Add `isOther` to question object from request_user_input tool input and
  remove `other` option from the tool prompt to better handle tool input.

  Shijie Rao · 2026-01-26 09:52:38 -08:00
  3ba702c5b6
• 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
• Prevent backspace from removing a text element when the cursor is at the element’s left edge (#9630)

  **Summary**
  - Prevent backspace from removing a text element when the cursor is at
  the element’s left edge.
  - Instead just delete the char before the placeholder (moving it to the
  left).

  Charley Cunningham · 2026-01-24 10:41:39 -08:00
  279c9534a1
• Have a coding mode and only show coding and plan (#9802)
  Ahmed Ibrahim · 2026-01-23 19:28:49 -08:00
  b3127e2eeb
• 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
• Hide mode cycle hint while a task is running (#9730)

  ## Summary
  - hide the “(shift+tab to cycle)” suffix on the collaboration mode label
  while a task is running
  - keep the cycle hint visible when idle
  - add a snapshot to cover the running-task label state

  charley-oai · 2026-01-22 18:32:06 -08:00
  02fced28a4
• Modes label below textarea (#9645)

  # Summary
  - Add a collaboration mode indicator rendered at the bottom-right of the
  TUI composer footer.
  - Style modes per design (Plan in #D72EE1, Execute matching dim context
  style, Pair Programming using the same cyan as text elements).
  - Add shared “(shift+tab to cycle)” hint text for all mode labels and
  align the indicator with the left footer margin.
  
  NOTE: currently this is hidden if the Collaboration Modes feature flag
  is disabled, or in Custom mode. Maybe we should show it in Custom mode
  too? I'll leave that out of this PR though
  
  # UI
  - Mode indicator appears below the textarea, bottom-right of the footer
  line.
  - Includes “(shift+tab to cycle)” and keeps right padding aligned to the
  left footer indent.
  
  <img width="983" height="200" alt="Screenshot 2026-01-21 at 7 17 54 PM"
  src="https://github.com/user-attachments/assets/d1c5e4ed-7d7b-4f6c-9e71-bc3cf6400e0e"
  />
  
  <img width="980" height="200" alt="Screenshot 2026-01-21 at 7 18 53 PM"
  src="https://github.com/user-attachments/assets/d22ff0da-a406-4930-85c5-affb2234e84b"
  />
  
  <img width="979" height="201" alt="Screenshot 2026-01-21 at 7 19 12 PM"
  src="https://github.com/user-attachments/assets/862cb17f-0495-46fa-9b01-a4a9f29b52d5"
  />

  charley-oai · 2026-01-22 17:31:11 +00:00
  4210fb9e6c
• 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
• feat(tui): retire the tui2 experiment (#9640)

  ## Summary
  - Retire the experimental TUI2 implementation and its feature flag.
  - Remove TUI2-only config/schema/docs so the CLI stays on the
  terminal-native path.
  - Keep docs aligned with the legacy TUI while we focus on redraw-based
  improvements.
  
  ## Customer impact
  - Retires the TUI2 experiment and keeps Codex on the proven
  terminal-native UI while we invest in redraw-based improvements to the
  existing experience.
  
  ## Migration / compatibility
  - If you previously set tui2-related options in config.toml, they are
  now ignored and Codex continues using the existing terminal-native TUI
  (no action required).
  
  ## Context
  - What worked: a transcript-owned viewport delivered excellent resize
  rewrap and high-fidelity copy (especially for code).
  - Why stop: making that experience feel fully native across the
  environment matrix (terminal emulator, OS, input modality, multiplexer,
  font/theme, alt-screen behavior) creates a combinatorial explosion of
  edge cases.
  - What next: we are focusing on redraw-based improvements to the
  existing terminal-native TUI so scrolling, selection, and copy remain
  native while resize/redraw correctness improves.
  
  ## Testing
  - just write-config-schema
  - just fmt
  - cargo clippy --fix --all-features --tests --allow-dirty --allow-no-vcs
  -p codex-core
  - cargo clippy --fix --all-features --tests --allow-dirty --allow-no-vcs
  -p codex-cli
  - cargo check
  - cargo test -p codex-core
  - cargo test -p codex-cli

  Josh McKinney · 2026-01-22 01:02:29 +00:00
  a489b64cb5
• Reduce burst testing flake (#9549)

  ## Summary
  
  - make paste-burst tests deterministic by injecting explicit timestamps
  instead of relying on wall clock timing
  - add time-aware helpers for input/submission paths so tests can drive
  the burst heuristic precisely
  - update burst-related tests to flush using computed timeouts while
  preserving behavior assertions
  - increase timeout slack in
  shell_tools_start_before_response_completed_when_stream_delayed to
  reduce flakiness

  charley-oai · 2026-01-21 16:42:31 -08:00
  41e38856f6
• feat: better sorting of shell commands (#9629)

  This PR changes the way we sort slash command by going in this order:
  1. Exact match
  2. Prefix
  3. Fuzzy
  
  As a result, we you type `/ps` the default command is not `/approvals`

  jif-oai · 2026-01-21 23:03:01 +00:00
  5dad1b956e
• Chore: update plan mode output in prompt (#9592)

  ### Summary
  * Update plan prompt output
  * Update requestUserInput response to be a single key value pair
  `answer: String`.

  Shijie Rao · 2026-01-21 14:12:18 -08:00
  3fcb40245e
• fix going up and down on questions after writing notes (#9596)
  Ahmed Ibrahim · 2026-01-21 09:37:37 +00:00
  6e9a31def1
• Add request-user-input overlay (#9585)

  - Add request-user-input overlay and routing in the TUI

  Ahmed Ibrahim · 2026-01-21 00:19:35 -08:00
  5f55ed666b
• Prompt Expansion: Preserve Text Elements (#9518)

  Summary
  - Preserve `text_elements` through custom prompt argument parsing and
  expansion (named and numeric placeholders).
  - Translate text element ranges through Shlex parsing using sentinel
  substitution, and rehydrate text + element ranges per arg.
  - Drop image attachments when their placeholder does not survive prompt
  expansion, keeping attachments consistent with rendered elements.
  - Mirror changes in TUI2 and expand tests for prompt parsing/expansion
  edge cases.
  
  Tests
  - placeholders with spaces as single tokens (positional + key=value,
  quoted + unquoted),
    - prompt expansion with image placeholders,
    - large paste + image arg combinations,
    - unused image arg dropped after expansion.

  charley-oai · 2026-01-20 18:30:20 -08:00
  531748a080
• queue only when task is working (#9558)
  Ahmed Ibrahim · 2026-01-20 15:24:45 -08:00
  fbd8afad81
• Improve UI spacing for queued messages (#9162)

  Despite good spacing between queued messages and assistant message text:
  <img width="462" height="322" alt="Screenshot 2026-01-12 at 4 54 50 PM"
  src="https://github.com/user-attachments/assets/e8b46252-0b33-40d2-b431-cb73b9a3bd2e"
  />
  
  Codex has confusing spacing between queued messages and shimmering
  status text (making the queued message seem like a sub-item of the
  shimmering status text)
  <img width="615" height="217" alt="Screenshot 2026-01-12 at 4 54 18 PM"
  src="https://github.com/user-attachments/assets/ee5e6095-8fe9-4863-88d2-10472cab8bd6"
  />
  
  This PR changes the spacing between the queued message(s) and shimmering
  status text to make it less confusing:
  <img width="440" height="240" alt="Screenshot 2026-01-13 at 11 20 36 AM"
  src="https://github.com/user-attachments/assets/02dcc690-cbe9-4943-87de-c7300ef51120"
  />
  
  While working on the status/queued spacing change, we noticed two
  paste‑burst tests were timing‑sensitive and could fail
  on slower CI. We added a small test‑only helper to keep the paste‑burst
  state active and refreshed during these tests. This
  removes dependence on tight timing and makes the tests deterministic
  without affecting runtime behavior.

  charley-oai · 2026-01-20 14:54:49 -08:00
  64678f895a
• Add total (non-partial) TextElement placeholder accessors (#9545)

  ## Summary
  - Make `TextElement` placeholders private and add a text-backed accessor
  to avoid assuming `Some`.
  - Since they are optional in the protocol, we want to make sure any
  accessors properly handle the None case (getting the placeholder using
  the byte range in the text)
  - Preserve placeholders during protocol/app-server conversions using the
  accessor fallback.
  - Update TUI composer/remap logic and tests to use the new
  constructor/accessor.

  charley-oai · 2026-01-20 14:04:11 -08:00
  be9e55c5fc
• Persist text elements through TUI input and history (#9393)

  Continuation of breaking up this PR
  https://github.com/openai/codex/pull/9116
  
  ## Summary
  - Thread user text element ranges through TUI/TUI2 input, submission,
  queueing, and history so placeholders survive resume/edit flows.
  - Preserve local image attachments alongside text elements and rehydrate
  placeholders when restoring drafts.
  - Keep model-facing content shapes clean by attaching UI metadata only
  to user input/events (no API content changes).
  
  ## Key Changes
  - TUI/TUI2 composer now captures text element ranges, trims them with
  text edits, and restores them when submission is suppressed.
  - User history cells render styled spans for text elements and keep
  local image paths for future rehydration.
  - Initial chat widget bootstraps accept empty `initial_text_elements` to
  keep initialization uniform.
  - Protocol/core helpers updated to tolerate the new InputText field
  shape without changing payloads sent to the API.

  charley-oai · 2026-01-19 23:49:34 -08:00
  eb90e20c0b
• tui: avoid Esc interrupt when skill popup active (#9451)

  Fixes #9450
  
  ## What
  - When a task is running and the skills autocomplete popup is open,
  `Esc` now dismisses the popup instead of sending `Op::Interrupt`.
  - `Esc` still interrupts a running task when no popup is active.
  
  ## Tests
  - `cargo test -p codex-tui`
  
  ---------
  
  Co-authored-by: prateek <199982+prateek@users.noreply.github.com>

  prateek-oai · 2026-01-19 12:52:04 -08:00
  0c0c5aeddc
• TUI: collaboration mode UX + always submit UserTurn when enabled (#9461)

  - Adds experimental collaboration modes UX in TUI: Plan / Pair
  Programming / Execute.
  - Gated behind `Feature::CollaborationModes`; existing behavior remains
  unchanged when disabled.
  - Selection UX:
  - `Shift+Tab` cycles modes while idle (no task running, no modal/popup).
  - `/collab` cycles; `/collab <plan|pair|pp|execute|exec>` sets
  explicitly.
  - Footer flash after changes + shortcut overlay shows `Shift+Tab` “to
  change mode”.
    - `/status` shows “Collaboration mode”.
  - Submission semantics:
  - When enabled: every submit uses `Op::UserTurn` and always includes
  `collaboration_mode: Some(...)` (default Pair Programming).
    - Removes the one-shot “pending collaboration mode” behavior.
  - Implementation:
  - New `tui/src/collaboration_modes.rs` (selection enum/cycle, `/collab`
  parsing, resolve to `CollaborationMode`, footer flash line).
  - Fallback: `resolve_mode_or_fallback` synthesizes a `CollaborationMode`
  when presets are missing (uses current model + reasoning effort; no
  `developer_instructions`) to avoid core falling back to `Custom`.
    - TODO: migrate TUI to use `Op::UserTurn`.

  Ahmed Ibrahim · 2026-01-19 09:32:04 -08:00
  bf430ad9fe
• Preserve slash command order in search (#9425)

  Keep slash popup search results in presentation order for built-ins and
  prompts.

  Ahmed Ibrahim · 2026-01-17 19:46:07 -08:00
  aeaff26451
• Support SKILL.toml file. (#9125)

  We’re introducing a new SKILL.toml to hold skill metadata so Codex can
  deliver a richer Skills experience.
  
  Initial focus is the interface block:
  ```
  [interface]
  display_name = "Optional user-facing name"
  short_description = "Optional user-facing description"
  icon_small = "./assets/small-400px.png"
  icon_large = "./assets/large-logo.svg"
  brand_color = "#3B82F6"
  default_prompt = "Optional surrounding prompt to use the skill with"
  ```
  
  All fields are exposed via the app server API.
  display_name and short_description are consumed by the TUI.

  xl-openai · 2026-01-15 11:20:04 -08:00
  42fa4c237f
• Revert recent styling change for input prompt placeholder text (#9307)

  A recent change in commit ccba737d26 modified the styling of the
  placeholder text (e.g. "Implement {feature}") in the input box of the
  CLI, changing it from non-italic to italic. I think this was likely
  unintentional. It results in a bad display appearance on some terminal
  emulators, and several users have complained about it.
  
  This change switches back to non-italic styling, restoring the older
  behavior.
  
  It addresses #9262

  Eric Traut · 2026-01-15 10:58:12 -08:00
  5f10548772
• fix(tui): disable double-press quit shortcut (#9220)

  Disables the default Ctrl+C/Ctrl+D double-press quit UX (keeps the code
  path behind a const) while we rethink the quit/interrupt flow.
  
  Tests:
  - just fmt
  - cargo clippy --fix --all-features --tests --allow-dirty --allow-no-vcs
  -p codex-tui
  - cargo test -p codex-tui --lib

  Josh McKinney · 2026-01-14 20:28:18 +00:00
  27da8a68d3
• fix(tui2): align Steer submit keys (#9218)

  - Remove legacy Ctrl+K queuing in tui2; Tab is the queue key.
  - Make Enter queue when Steer is disabled and submit immediately when
  Steer is enabled.
  - Add Steer keybinding docs on both tui and tui2 chat composers.

  Josh McKinney · 2026-01-14 19:35:55 +00:00
  0471ddbe74
• tui: double-press Ctrl+C/Ctrl+D to quit (#8936)

  ## Problem
  
  Codex’s TUI quit behavior has historically been easy to trigger
  accidentally and hard to reason
  about.
  
  - `Ctrl+C`/`Ctrl+D` could terminate the UI immediately, which is a
  common key to press while trying
    to dismiss a modal, cancel a command, or recover from a stuck state.
  - “Quit” and “shutdown” were not consistently separated, so some exit
  paths could bypass the
    shutdown/cleanup work that should run before the process terminates.
  
  This PR makes quitting both safer (harder to do by accident) and more
  uniform across quit
  gestures, while keeping the shutdown-first semantics explicit.
  
  ## Mental model
  
  After this change, the system treats quitting as a UI request that is
  coordinated by the app
  layer.
  
  - The UI requests exit via `AppEvent::Exit(ExitMode)`.
  - `ExitMode::ShutdownFirst` is the normal user path: the app triggers
  `Op::Shutdown`, continues
  rendering while shutdown runs, and only ends the UI loop once shutdown
  has completed.
  - `ExitMode::Immediate` exists as an escape hatch (and as the
  post-shutdown “now actually exit”
  signal); it bypasses cleanup and should not be the default for
  user-triggered quits.
  
  User-facing quit gestures are intentionally “two-step” for safety:
  
  - `Ctrl+C` and `Ctrl+D` no longer exit immediately.
  - The first press arms a 1-second window and shows a footer hint (“ctrl
  + <key> again to quit”).
  - Pressing the same key again within the window requests a
  shutdown-first quit; otherwise the
    hint expires and the next press starts a fresh window.
  
  Key routing remains modal-first:
  
  - A modal/popup gets first chance to consume `Ctrl+C`.
  - If a modal handles `Ctrl+C`, any armed quit shortcut is cleared so
  dismissing a modal cannot
    prime a subsequent `Ctrl+C` to quit.
  - `Ctrl+D` only participates in quitting when the composer is empty and
  no modal/popup is active.
  
  The design doc `docs/exit-confirmation-prompt-design.md` captures the
  intended routing and the
  invariants the UI should maintain.
  
  ## Non-goals
  
  - This does not attempt to redesign modal UX or make modals uniformly
  dismissible via `Ctrl+C`.
  It only ensures modals get priority and that quit arming does not leak
  across modal handling.
  - This does not introduce a persistent confirmation prompt/menu for
  quitting; the goal is to keep
    the exit gesture lightweight and consistent.
  - This does not change the semantics of core shutdown itself; it changes
  how the UI requests and
    sequences it.
  
  ## Tradeoffs
  
  - Quitting via `Ctrl+C`/`Ctrl+D` now requires a deliberate second
  keypress, which adds friction for
    users who relied on the old “instant quit” behavior.
  - The UI now maintains a small time-bounded state machine for the armed
  shortcut, which increases
    complexity and introduces timing-dependent behavior.
  
  This design was chosen over alternatives (a modal confirmation prompt or
  a long-lived “are you
  sure” state) because it provides an explicit safety barrier while
  keeping the flow fast and
  keyboard-native.
  
  ## Architecture
  
  - `ChatWidget` owns the quit-shortcut state machine and decides when a
  quit gesture is allowed
    (idle vs cancellable work, composer state, etc.).
  - `BottomPane` owns rendering and local input routing for modals/popups.
  It is responsible for
  consuming cancellation keys when a view is active and for
  showing/expiring the footer hint.
  - `App` owns shutdown sequencing: translating
  `AppEvent::Exit(ShutdownFirst)` into `Op::Shutdown`
    and only terminating the UI loop when exit is safe.
  
  This keeps “what should happen” decisions (quit vs interrupt vs ignore)
  in the chat/widget layer,
  while keeping “how it looks and which view gets the key” in the
  bottom-pane layer.
  
  ## Observability
  
  You can tell this is working by running the TUIs and exercising the quit
  gestures:
  
  - While idle: pressing `Ctrl+C` (or `Ctrl+D` with an empty composer and
  no modal) shows a footer
  hint for ~1 second; pressing again within that window exits via
  shutdown-first.
  - While streaming/tools/review are active: `Ctrl+C` interrupts work
  rather than quitting.
  - With a modal/popup open: `Ctrl+C` dismisses/handles the modal (if it
  chooses to) and does not
  arm a quit shortcut; a subsequent quick `Ctrl+C` should not quit unless
  the user re-arms it.
  
  Failure modes are visible as:
  
  - Quits that happen immediately (no hint window) from `Ctrl+C`/`Ctrl+D`.
  - Quits that occur while a modal is open and consuming `Ctrl+C`.
  - UI termination before shutdown completes (cleanup skipped).
  
  ## Tests
  
  - Updated/added unit and snapshot coverage in `codex-tui` and
  `codex-tui2` to validate:
    - The quit hint appears and expires on the expected key.
  - Double-press within the window triggers a shutdown-first quit request.
  - Modal-first routing prevents quit bypass and clears any armed shortcut
  when a modal consumes
      `Ctrl+C`.
  
  These tests focus on the UI-level invariants and rendered output; they
  do not attempt to validate
  real terminal key-repeat timing or end-to-end process shutdown behavior.
  
  ---
  Screenshot:
  <img width="912" height="740" alt="Screenshot 2026-01-13 at 1 05 28 PM"
  src="https://github.com/user-attachments/assets/18f3d22e-2557-47f2-a369-ae7a9531f29f"
  />

  Josh McKinney · 2026-01-14 17:42:52 +00:00
  4283a7432b
• fix(tui): harden paste-burst state transitions (#9124)

  User-facing symptom: On terminals that deliver pastes as rapid
  KeyCode::Char/Enter streams (notably Windows), paste-burst transient
  state
  can leak into the next input. Users can see Enter insert a newline when
  they meant to submit, or see characters appear late / handled through
  the
  wrong path.
  
  System problem: PasteBurst is time-based. Clearing only the
  classification window (e.g. via clear_window_after_non_char()) can erase
  last_plain_char_time without emitting buffered text. If a buffer is
  still
  non-empty after that, flush_if_due() no longer has a timeout clock to
  flush against, so the buffer can get "stuck" until another plain char
  arrives.
  
  This was surfaced while adding deterministic regression tests for
  paste-burst behavior.
  
  Fix: when disabling burst detection, defuse any in-flight burst state:
  flush held/buffered text through handle_paste() (so it follows normal
  paste integration), then clear timing and Enter suppression.
  
  Document the rationale inline and update docs/tui-chat-composer.md so
  "disable_paste_burst" matches the actual behavior.

  Josh McKinney · 2026-01-14 01:42:21 +00:00
  ce49e92848
• Allow close skill popup with esc. (#9165)

  <img width="398" height="133" alt="image"
  src="https://github.com/user-attachments/assets/3084e793-ce5b-4f92-ad60-4c73e65c21c5"
  />
  <img width="242" height="86" alt="image"
  src="https://github.com/user-attachments/assets/57dd5587-0aea-4a55-91b8-273702939cb2"
  />
  
  You can now esc to quit the skill popup and submit the input as it is.

  xl-openai · 2026-01-13 15:02:44 -08:00
  89403c5e11
• test(tui): add deterministic paste-burst tests (#9121)

  Replace the old timing-dependent non-ASCII paste test with deterministic
  coverage by forcing an active `PasteBurst` and asserting the exact flush
  payload.
  
  Add focused unit tests for `PasteBurst` transitions, and add short
  "Behavior:" rustdoc notes on chat composer tests to make the state
  machine contracts explicit.

  Josh McKinney · 2026-01-13 21:55:44 +00:00
  141d2b5022
• fix(tui): document paste-burst state machine (#9020)

  Add a narrative doc and inline rustdoc explaining how `ChatComposer`
  and `PasteBurst` compose into a single state machine on terminals that
  lack reliable bracketed paste (notably Windows).
  
  This documents the key states, invariants, and integration points
  (`handle_input_basic`, `handle_non_ascii_char`, tick-driven flush) so
  future changes are easier to reason about.

  Josh McKinney · 2026-01-13 11:48:31 -08:00
  58e8f75b27
• Show tab queue hint in footer (#9138)

  - show the Tab queue hint in the footer when a task is running with
  Steer enabled
  - drop the history queue hint and add footer snapshots

  Ahmed Ibrahim · 2026-01-13 00:32:53 -08:00
  17ab5f6a52
• Send message by default mid turn. queue messages by tab (#9077)

  https://github.com/user-attachments/assets/03838730-4ddc-44df-a2c7-cb8ecda78660

  Ahmed Ibrahim · 2026-01-12 23:06:35 -08:00
  cbca43d57a
• Add some tests for image attachments (#9080)

  Some extra tests for https://github.com/openai/codex/pull/8950

  charley-oai · 2026-01-12 13:41:50 -08:00
  d7cdcfc302
• Label attached images so agent can understand in-message labels (#8950)

  Agent wouldn't "see" attached images and would instead try to use the
  view_file tool:
  <img width="1516" height="504" alt="image"
  src="https://github.com/user-attachments/assets/68a705bb-f962-4fc1-9087-e932a6859b12"
  />
  
  In this PR, we wrap image content items in XML tags with the name of
  each image (now just a numbered name like `[Image #1]`), so that the
  model can understand inline image references (based on name). We also
  put the image content items above the user message which the model seems
  to prefer (maybe it's more used to definitions being before references).
  
  We also tweak the view_file tool description which seemed to help a bit
  
  Results on a simple eval set of images:
  
  Before
  <img width="980" height="310" alt="image"
  src="https://github.com/user-attachments/assets/ba838651-2565-4684-a12e-81a36641bf86"
  />
  
  After
  <img width="918" height="322" alt="image"
  src="https://github.com/user-attachments/assets/10a81951-7ee6-415e-a27e-e7a3fd0aee6f"
  />
  
  ```json
  [
    {
      "id": "single_describe",
      "prompt": "Describe the attached image in one sentence.",
      "images": ["image_a.png"]
    },
    {
      "id": "single_color",
      "prompt": "What is the dominant color in the image? Answer with a single color word.",
      "images": ["image_b.png"]
    },
    {
      "id": "orientation_check",
      "prompt": "Is the image portrait or landscape? Answer in one sentence.",
      "images": ["image_c.png"]
    },
    {
      "id": "detail_request",
      "prompt": "Look closely at the image and call out any small details you notice.",
      "images": ["image_d.png"]
    },
    {
      "id": "two_images_compare",
      "prompt": "I attached two images. Are they the same or different? Briefly explain.",
      "images": ["image_a.png", "image_b.png"]
    },
    {
      "id": "two_images_captions",
      "prompt": "Provide a short caption for each image (Image 1, Image 2).",
      "images": ["image_c.png", "image_d.png"]
    },
    {
      "id": "multi_image_rank",
      "prompt": "Rank the attached images from most colorful to least colorful.",
      "images": ["image_a.png", "image_b.png", "image_c.png"]
    },
    {
      "id": "multi_image_choice",
      "prompt": "Which image looks more vibrant? Answer with 'Image 1' or 'Image 2'.",
      "images": ["image_b.png", "image_d.png"]
    }
  ]
  ```

  charley-oai · 2026-01-09 21:33:45 -08:00
  6709ad8975
• Add config to disable /feedback (#8909)

  Some enterprises do not want their users to be able to `/feedback`.
  
  <img width="395" height="325" alt="image"
  src="https://github.com/user-attachments/assets/2dae9c0b-20c3-4a15-bcd3-0187857ebbd8"
  />
  
  Adds to `config.toml`:
  
  ```toml
  [feedback]
  enabled = false
  ```
  
  I've deliberately decided to:
  1. leave other references to `/feedback` (e.g. in the interrupt message,
  tips of the day) unchanged. I think we should continue to promote the
  feature even if it is not usable currently.
  2. leave the `/feedback` menu item selectable and display an error
  saying it's disabled, rather than remove the menu item (which I believe
  would raise more questions).
  
  but happy to discuss these.
  
  This will be followed by a change to requirements.toml that admins can
  use to force the value of feedback.enabled.

  gt-oai · 2026-01-09 16:33:48 +00:00
  5b5a5b92b5
• Elevated sandbox NUX (#8789)

  Elevated Sandbox NUX:
  
  * prompt for elevated sandbox setup when agent mode is selected (via
  /approvals or at startup)
  * prompt for degraded sandbox if elevated setup is declined or fails
  * introduce /elevate-sandbox command to upgrade from degraded
  experience.

  iceweasel-oai · 2026-01-08 16:23:06 -08:00
  6372ba9d5f
• add tooltip hint for shell commands (!) (#8926)

  I didn't know this existed because its not listed in the hints.

  Felipe Petroski Such · 2026-01-08 19:31:20 +00:00
  5bc3e325a6
• fix: windows can now paste non-ascii multiline text (#8774)

  ## Summary
  This PR builds _heavily_ on the work from @occurrent in #8021 - I've
  only added a small fix, added additional tests, and propagated the
  changes to tui2.
  
  From the original PR:
  
  > On Windows, Codex relies on PasteBurst for paste detection because
  bracketed paste is not reliably available via crossterm.
  > 
  > When pasted content starts with non-ASCII characters, input is routed
  through handle_non_ascii_char, which bypasses the normal paste burst
  logic. This change extends the paste burst window for that path, which
  should ensure that Enter is correctly grouped as part of the paste.
  
  
  ## Testing
  - [x] tested locally cross-platform
  - [x] added regression tests
  
  ---------
  
  Co-authored-by: occur <occurring@outlook.com>

  Dylan Hurd · 2026-01-07 23:21:49 -08:00
  0f8bb4579b
• add ability to disable input temporarily in the TUI. (#8876)

  We will disable input while the elevated sandbox setup is running.

  iceweasel-oai · 2026-01-07 20:56:48 -08:00
  ccba737d26
• add footer note to TUI (#8867)

  This will be used by the elevated sandbox NUX to give a hint on how to
  run the elevated sandbox when in the non-elevated mode.

  iceweasel-oai · 2026-01-07 16:44:28 -08:00
  357e4c902b
• fix: implement 'Allow this session' for apply_patch approvals (#8451)

  **Summary**
  This PR makes “ApprovalDecision::AcceptForSession / don’t ask again this
  session” actually work for `apply_patch` approvals by caching approvals
  based on absolute file paths in codex-core, properly wiring it through
  app-server v2, and exposing the choice in both TUI and TUI2.
  - This brings `apply_patch` calls to be at feature-parity with general
  shell commands, which also have a "Yes, and don't ask again" option.
  - This also fixes VSCE's "Allow this session" button to actually work.
  
  While we're at it, also split the app-server v2 protocol's
  `ApprovalDecision` enum so execpolicy amendments are only available for
  command execution approvals.
  
  **Key changes**
  - Core: per-session patch approval allowlist keyed by absolute file
  paths
  - Handles multi-file patches and renames/moves by recording both source
  and destination paths for `Update { move_path: Some(...) }`.
  - Extend the `Approvable` trait and `ApplyPatchRuntime` to work with
  multiple keys, because an `apply_patch` tool call can modify multiple
  files. For a request to be auto-approved, we will need to check that all
  file paths have been approved previously.
  - App-server v2: honor AcceptForSession for file changes
  - File-change approval responses now map AcceptForSession to
  ReviewDecision::ApprovedForSession (no longer downgraded to plain
  Approved).
  - Replace `ApprovalDecision` with two enums:
  `CommandExecutionApprovalDecision` and `FileChangeApprovalDecision`
  - TUI / TUI2: expose “don’t ask again for these files this session”
  - Patch approval overlays now include a third option (“Yes, and don’t
  ask again for these files this session (s)”).
      - Snapshot updates for the approval modal.
  
  **Tests added/updated**
  - Core:
  - Integration test that proves ApprovedForSession on a patch skips the
  next patch prompt for the same file
  - App-server:
  - v2 integration test verifying
  FileChangeApprovalDecision::AcceptForSession works properly
  
  **User-visible behavior**
  - When the user approves a patch “for session”, future patches touching
  only those previously approved file(s) will no longer prompt gain during
  that session (both via app-server v2 and TUI/TUI2).
  
  **Manual testing**
  Tested both TUI and TUI2 - see screenshots below.
  
  TUI:
  <img width="1082" height="355" alt="image"
  src="https://github.com/user-attachments/assets/adcf45ad-d428-498d-92fc-1a0a420878d9"
  />
  
  
  TUI2:
  <img width="1089" height="438" alt="image"
  src="https://github.com/user-attachments/assets/dd768b1a-2f5f-4bd6-98fd-e52c1d3abd9e"
  />

  Owen Lin · 2026-01-07 20:11:12 +00:00
  66450f0445
• chore: rename unified exec sessions (#8822)

  Renaming done by Codex

  jif-oai · 2026-01-07 16:12:47 +00:00
  4cef89a122
• fix: handle /review arguments in TUI (#8823)

  Handle /review <instructions> in the TUI and TUI2 by routing it as a
  custom review command instead of plain text, wiring command dispatch and
  adding composer coverage so typing /review text starts a review directly
  rather than posting a message. User impact: /review with arguments now
  kicks off the review flow, previously it would just forward as a plain
  command and not actually start a review.

  Thibault Sottiaux · 2026-01-07 13:14:55 +00:00
  124a09e577
• fix: truncate long approval prefixes when rendering (#8734)

  Fixes inscrutable multiline approval requests:
  <img width="686" height="844" alt="image"
  src="https://github.com/user-attachments/assets/cf9493dc-79e6-4168-8020-0ef0fe676d5e"
  />

  Thibault Sottiaux · 2026-01-06 15:17:01 -08:00
  8b4d27dfcd
• suppress popups while browsing input history (#8772)
  xl-openai · 2026-01-06 11:13:21 -08:00
  4ce9d0aa7b
• [tui] add optional details to TUI status header (#8293)

  ### What
  
  Add optional `details` field to TUI's status indicator header. `details`
  is shown under the header with text wrapping and a max height of 3
  lines.
  
  Duplicated changes to `tui2`.
  
  ### Why
  
  Groundwork for displaying error details under `Reconnecting...` for
  clarity with retryable errors.
  
  Basic examples
  <img width="1012" height="326" alt="image"
  src="https://github.com/user-attachments/assets/dd751ceb-b179-4fb2-8fd1-e4784d6366fb"
  />
  
  <img width="1526" height="358" alt="image"
  src="https://github.com/user-attachments/assets/bbe466fc-faff-4a78-af7f-3073ccdd8e34"
  />
  
  Truncation example
  <img width="936" height="189" alt="image"
  src="https://github.com/user-attachments/assets/f3f1b5dd-9050-438b-bb07-bd833c03e889"
  />
  
  ### Tests
  Tested locally, added tests for truncation.

  sayan-oai · 2025-12-23 12:40:40 -08:00
  53eb2e9f27