51 Commits

• fix(tui): reflow scrollback on terminal resize (#18575)

  Fixes multiple scrollback and terminal resize issues: #5538, #5576,
  #8352, #12223, #16165, and #15380.
  
  ## Why
  
  Codex writes finalized transcript output into terminal scrollback after
  wrapping it for the current viewport width. A later terminal resize
  could leave that scrollback shaped for the old width, so wider windows
  kept narrow output and narrower windows could show stale wrapping
  artifacts until enough new output replaced the visible area.
  
  This is also the foundation PR for responsive markdown tables. Table
  rendering needs finalized transcript content to be width-sensitive after
  insertion, not only while content is first streaming. Markdown table
  rendering itself stays in #18576.
  
  ## Stack
  
  - PR1: resize backlog reflow and interrupt cleanup
  - #18576: markdown table support
  
  ## What Changed
  
  - Rebuild source-backed transcript history when the terminal width
  changes. `terminal_resize_reflow` is introduced through the experimental
  feature system, but is enabled by default for this rollout so we can
  validate behavior across real terminals.
  - Preserve assistant and plan stream source so finalized streaming
  output can participate in resize reflow after consolidation.
  - Debounce resize work, but force a final source-backed reflow when a
  resize happened during active or unconsolidated streaming output.
  - Clear stale pending history lines on resize so old-width wrapped
  output is not emitted just before rebuilt scrollback.
  - Bound replay work with `[tui.terminal_resize_reflow].max_rows`:
  omitted uses terminal-specific defaults, `0` keeps all rendered rows,
  and a positive value sets an explicit cap. The cap applies both while
  initially replaying a resumed transcript into scrollback and when
  rebuilding scrollback after terminal resize.
  - Consolidate interrupted assistant streams before cleanup, then clear
  pending stream output and active-tail state consistently.
  - Move resize reflow and thread event buffering helpers out of `app.rs`
  into dedicated TUI modules.
  - Add focused coverage for resize reflow, feature-gated behavior,
  streaming source preservation, interrupted output cleanup,
  unicode-neutral text, terminal-specific row caps, and composer/layout
  stability.
  
  ## Runtime Bounds
  
  Resize reflow keeps only the most recent rendered rows when a row cap is
  active. The default is `auto`, which maps to the detected terminal's
  default scrollback size where Codex can identify it: VS Code `1000`,
  Windows Terminal `9001`, WezTerm `3500`, and Alacritty `10000`.
  Terminals without a dedicated mapping use the conservative fallback of
  `1000` rows. Users can override this with `[tui.terminal_resize_reflow]
  max_rows = N`, or set `max_rows = 0` to disable row limiting.
  
  ## Validation
  
  - `just fmt`
  - `git diff --check`
  - `cargo test --manifest-path codex-rs/Cargo.toml -p codex-tui reflow`
  - `cargo test --manifest-path codex-rs/Cargo.toml -p codex-tui
  transcript_reflow`
  - `just fix -p codex-tui`
  - PR CI in progress on the squashed branch

  Felipe Coury · 2026-04-25 22:00:32 -03:00
  5591912f0b
• Support multiple cwd filters for thread list (#18502)

  ## Summary
  
  - Teach app-server `thread/list` to accept either a single `cwd` or an
  array of cwd filters, returning threads whose recorded session cwd
  matches any requested path
  - Add `useStateDbOnly` as an explicit opt-in fast path for callers that
  want to answer `thread/list` from SQLite without scanning JSONL rollout
  files
  - Preserve backwards compatibility: by default, `thread/list` still
  scans JSONL rollouts and repairs SQLite state
  - Wire the new cwd array and SQLite-only options through app-server,
  local/remote thread-store, rollout listing, generated TypeScript/schema
  fixtures, proto output, and docs
  
  ## Test Plan
  
  - `cargo test -p codex-app-server-protocol`
  - `cargo test -p codex-rollout`
  - `cargo test -p codex-thread-store`
  - `cargo test -p codex-app-server thread_list`
  - `just fmt`
  - `just fix -p codex-app-server-protocol -p codex-rollout -p
  codex-thread-store -p codex-app-server`
  - `cargo build -p codex-cli --bin codex`

  acrognale-oai · 2026-04-22 06:10:09 -04:00
  4f8c58f737
• Remove simple TUI legacy_core reexports (#18631)

  ## Problem
  The TUI still imported path utilities and config-loader symbols through
  app-server-client's legacy_core facade even though those APIs already
  exist in utility/config crates. This is part of our ongoing effort to
  whittle away at these old dependencies.
  
  ## Solution
  Rewire imports to avoid the TUI directly importing from the core crate
  and instead import from common lower-level crates. This PR doesn't
  include any functional changes; it's just a simple rewiring.

  Eric Traut · 2026-04-20 10:48:27 -07:00
  164b6a0c78
• Use app server thread names in TUI picker (#18633)

  ## Problem
  
  The TUI resume/fork picker was backfilling thread names from local
  rollout indexes. This was left over from before the TUI was moved to the
  app server. It should be using app-server APIs because the TUI might be
  connected to a remote connection.
  
  This bug wasn't (yet) reported by a user. I found it by asking Codex to
  review places in the TUI code where it was still directly accessing the
  CODEX_HOME directory rather than going through app-server APIs.
  
  ## Solution
  
  The resume picker and session lookups should use app-server thread APIs
  only. Remove legacy rollout name/list backfills, and avoid local name
  reads in fork history.
  
  ## Testing
  
  I manually tested `codex resume` and `codex resume --all` to look for
  functional or performance regressions in the resume picker.

  Eric Traut · 2026-04-20 08:16:24 -07:00
  43a69c50eb
• TUI: remove simple legacy_core re-exports (#18605)

  ## Summary
  
  The TUI still imported several symbols through the transitional
  app-server-client `legacy_core` facade even though those symbols are
  already owned by smaller crates. This PR narrows that facade by rewiring
  those imports directly to their owner crates.
  
  ## Changes
  
  No functional changes, just import rewiring. This is part of our ongoing
  effort to whittle away at the `legacy_core` namespace, which represents
  all of the remaining symbols that the TUI imports from the core.

  Eric Traut · 2026-04-19 22:39:53 -07:00
  87fc21ff60
• Add sorting/backwardsCursor to thread/list and new thread/turns/list api (#17305)

  To improve performance of UI loads from the app, add two main
  improvements:
  1. The `thread/list` api now gets a `sortDirection` request field and a
  `backwardsCursor` to the response, which lets you paginate forwards and
  backwards from a window. This lets you fetch the first few items to
  display immediately while you paginate to fill in history, then can
  paginate "backwards" on future loads to catch up with any changes since
  the last UI load without a full reload of the entire data set.
  2. Added a new `thread/turns/list` api which also has sortDirection and
  backwardsCursor for the same behavior as `thread/list`, allowing you the
  same small-fetch for immediate display followed by background fill-in
  and resync catchup.

  David de Regt · 2026-04-17 11:49:02 -07:00
  eaf78e43f2
• Support Ctrl+P/Ctrl+N in resume picker (#18267)

  Fixes #18179.
  
  ## Why
  The fullscreen `/resume` picker accepted Up/Down navigation but ignored
  Ctrl+P/Ctrl+N, which made it inconsistent with other TUI selection flows
  such as `ListSelectionView`-backed pickers and composer navigation.
  
  ## What Changed
  Updated `codex-rs/tui/src/resume_picker.rs` so the resume picker treats
  Ctrl+P/Ctrl+N as aliases for Up/Down, including the raw `^P`/`^N`
  control-character events some terminals emit without a CONTROL modifier.

  Eric Traut · 2026-04-17 08:38:47 -07:00
  c3ecb557d3
• Spread AbsolutePathBuf (#17792)

  Mechanical change to promote absolute paths through code.

  pakrym-oai · 2026-04-14 14:26:10 -07:00
  dd1321d11b
• Fix thread/list cwd filtering for Windows verbatim paths (#17414)

  Addresses #17302
  
  Problem: `thread/list` compared cwd filters with raw path equality, so
  `resume --last` could miss Windows sessions when the saved cwd used a
  verbatim path form and the current cwd did not.
  
  Solution: Normalize cwd comparisons through the existing path comparison
  utilities before falling back to direct equality, and add Windows
  regression coverage for verbatim paths. I made this a general utility
  function and replaced all of the duplicated instance of it across the
  code base.

  Eric Traut · 2026-04-10 23:08:02 -07:00
  e9e7ef3d36
• TUI: enforce core boundary (#17399)

  Problem: The TUI still depended on `codex-core` directly in a number of
  places, and we had no enforcement from keeping this problem from getting
  worse.
  
  Solution: Route TUI core access through
  `codex-app-server-client::legacy_core`, add CI enforcement for that
  boundary, and re-export this legacy bridge inside the TUI as
  `crate::legacy_core` so the remaining call sites stay readable. There is
  no functional change in this PR — just changes to import targets.
  
  Over time, we can whittle away at the remaining symbols in this legacy
  namespace with the eventual goal of removing them all. In the meantime,
  this linter rule will prevent us from inadvertently importing new
  symbols from core.

  Eric Traut · 2026-04-10 20:25:31 -07:00
  66e13efd9c
• Fix resume picker timestamp labels and stability (#16822)

  Problem: The resume picker used awkward "Created at" and "Updated at"
  headers, and its relative timestamps changed while navigating because
  they were recomputed on each redraw.
  
  Solution: Rename the headers to "Created" and "Updated", and anchor
  relative timestamp formatting to the picker load time so the displayed
  ages stay stable while browsing.

  Eric Traut · 2026-04-06 08:51:13 -07:00
  4294031a93
• Add remote --cd forwarding for app-server sessions (#16700)

  Addresses #16124
  
  Problem: `codex --remote --cd <path>` canonicalized the path locally and
  then omitted it from remote thread lifecycle requests, so remote-only
  working directories failed or were ignored.
  
  Solution: Keep remote startup on the local cwd, forward explicit `--cd`
  values verbatim to `thread/start`, `thread/resume`, and `thread/fork`,
  and cover the behavior with `codex-tui` tests.
  
  Testing: I manually tested `--remote --cd` with both absolute and
  relative paths and validated correct behavior.
  
  
  ---
  
  Update based on code review feedback:
  
  Problem: Remote `--cd` was forwarded to `thread/resume` and
  `thread/fork`, but not to `thread/list` lookups, so `--resume --last`
  and picker flows could select a session from the wrong cwd; relative cwd
  filters also failed against stored absolute paths.
  
  Solution: Apply explicit remote `--cd` to `thread/list` lookups for
  `--last` and picker flows, normalize relative cwd filters on the
  app-server before exact matching, and document/test the behavior.

  Eric Traut · 2026-04-03 11:26:45 -07:00
  0ab8eda375
• Fix fork source display in /status (expose forked_from_id in app server) (#16596)

  Addresses #16560
  
  Problem: `/status` stopped showing the source thread id in forked TUI
  sessions after the app-server migration.
  
  Solution: Carry fork source ids through app-server v2 thread data and
  the TUI session adapter, and update TUI fixtures so `/status` matches
  the old TUI behavior.

  Eric Traut · 2026-04-02 14:05:29 -07:00
  9bb7f0a694
• Fix resume picker stale thread names (#16601)

  Addresses #16562
  
  Problem: Resume picker could keep a stale backend-provided thread title
  instead of the latest name from session_index.jsonl.
  
  Solution: Always backfill/override picker row names from local
  session_index.jsonl and cover stale-name replacement with a regression
  test.

  Eric Traut · 2026-04-02 14:22:57 -06:00
  c0f2fed67e
• Fix resume picker initial loading state (#16591)

  Addresses #16514
  
  Problem: Resume picker could show “No sessions yet” before the initial
  session fetch finished.
  
  Solution: Render a loading message while the first page is pending, and
  keep the empty state for truly empty results.

  Eric Traut · 2026-04-02 14:02:52 -06:00
  cb8dc18a64
• Rename tui_app_server to tui (#16104)

  This is a follow-up to https://github.com/openai/codex/pull/15922. That
  previous PR deleted the old `tui` directory and left the new
  `tui_app_server` directory in place. This PR renames `tui_app_server` to
  `tui` and fixes up all references.

  Eric Traut · 2026-03-28 11:23:07 -06:00
  61429a6c10
• Remove the legacy TUI split (#15922)

  This is the part 1 of 2 PRs that will delete the `tui` /
  `tui_app_server` split. This part simply deletes the existing `tui`
  directory and marks the `tui_app_server` feature flag as removed. I left
  the `tui_app_server` feature flag in place for now so its presence
  doesn't result in an error. It is simply ignored.
  
  Part 2 will rename the `tui_app_server` directory `tui`. I did this as
  two parts to reduce visible code churn.

  Eric Traut · 2026-03-27 22:56:44 +00:00
  d65deec617
• Add non-interactive resume filter option (#15339)

  ## Summary
  - add `codex resume --include-non-interactive` to include
  non-interactive sessions in the picker and `--last`
  - keep current-provider and cwd filtering behavior unchanged
  - replace the picker API boolean with a `SessionSourceFilter` enum to
  avoid a boolean trap
  
  ## Tests
  - `cargo test -p codex-cli`
  - `cargo test -p codex-tui`
  - `just fmt`
  - `just fix -p codex-cli`
  - `just fix -p codex-tui`

  Jeremy Rose · 2026-03-25 11:05:07 -07:00
  6b10e186c4
• feat: support product-scoped plugins. (#15041)

  1. Added SessionSource::Custom(String) and --session-source.
    2. Enforced plugin and skill products by session_source.
    3. Applied the same filtering to curated background refresh.

  xl-openai · 2026-03-19 00:46:15 -07:00
  db5781a088
• Apply argument comment lint across codex-rs (#14652)

  ## Why
  
  Once the repo-local lint exists, `codex-rs` needs to follow the
  checked-in convention and CI needs to keep it from drifting. This commit
  applies the fallback `/*param*/` style consistently across existing
  positional literal call sites without changing those APIs.
  
  The longer-term preference is still to avoid APIs that require comments
  by choosing clearer parameter types and call shapes. This PR is
  intentionally the mechanical follow-through for the places where the
  existing signatures stay in place.
  
  After rebasing onto newer `main`, the rollout also had to cover newly
  introduced `tui_app_server` call sites. That made it clear the first cut
  of the CI job was too expensive for the common path: it was spending
  almost as much time installing `cargo-dylint` and re-testing the lint
  crate as a representative test job spends running product tests. The CI
  update keeps the full workspace enforcement but trims that extra
  overhead from ordinary `codex-rs` PRs.
  
  ## What changed
  
  - keep a dedicated `argument_comment_lint` job in `rust-ci`
  - mechanically annotate remaining opaque positional literals across
  `codex-rs` with exact `/*param*/` comments, including the rebased
  `tui_app_server` call sites that now fall under the lint
  - keep the checked-in style aligned with the lint policy by using
  `/*param*/` and leaving string and char literals uncommented
  - cache `cargo-dylint`, `dylint-link`, and the relevant Cargo
  registry/git metadata in the lint job
  - split changed-path detection so the lint crate's own `cargo test` step
  runs only when `tools/argument-comment-lint/*` or `rust-ci.yml` changes
  - continue to run the repo wrapper over the `codex-rs` workspace, so
  product-code enforcement is unchanged
  
  Most of the code changes in this commit are intentionally mechanical
  comment rewrites or insertions driven by the lint itself.
  
  ## Verification
  
  - `./tools/argument-comment-lint/run.sh --workspace`
  - `cargo test -p codex-tui-app-server -p codex-tui`
  - parsed `.github/workflows/rust-ci.yml` locally with PyYAML
  
  ---
  
  * -> #14652
  * #14651

  Michael Bolin · 2026-03-16 16:48:15 -07:00
  b77fe8fefe
• tui: sort resume picker by last updated time (#13654)

  ## Summary
  - default the resume picker sort key to UpdatedAt instead of CreatedAt
  - keep Tab sort toggling behavior and update the test expectation for
  the new default
  
  ## Testing
  - just fmt
  - cargo test -p codex-tui
  
  Co-authored-by: Codex <noreply@openai.com>

  Charley Cunningham · 2026-03-05 18:23:44 -08:00
  56420da857
• tui: use thread_id for resume/fork cwd resolution (#12727)

  ## Summary
  - make resume/fork targets explicit and typed as `SessionTarget { path,
  thread_id }` (non-optional `thread_id`)
  - resolve `thread_id` centrally via `resolve_session_thread_id(...)`:
  - use CLI input directly when it is a UUID (`--resume <uuid>` / `--fork
  <uuid>`)
  - otherwise read `thread_id` from rollout `SessionMeta` for path-based
  selections (picker, `--resume-last`, name-based resume/fork)
  - use `thread_id` to read cwd from SQLite first during resume/fork cwd
  resolution
  - keep rollout fallback for cwd resolution when SQLite is unavailable or
  does not return thread metadata (`TurnContext` tail, then `SessionMeta`)
  - keep the resume picker open when a selected row has unreadable session
  metadata, and show an inline recoverable error instead of aborting the
  TUI
  
  ## Why
  This removes ad-hoc rollout filename parsing and makes resume/fork
  target identity explicit. The resume/fork cwd check can use indexed
  SQLite lookup by `thread_id` in the common path, while preserving
  rollout-based fallback behavior. It also keeps malformed legacy rows
  recoverable in the picker instead of letting a selection failure unwind
  the app.
  
  ## Notes
  - minimal TUI-only change; no schema/protocol changes
  - includes TUI test coverage for SQLite cwd precedence when `thread_id`
  is available
  - includes TUI regression coverage for picker inline error rendering /
  non-fatal unreadable session rows
  
  ## Codex author
  `codex resume 019c9205-7f8b-7173-a2a2-f082d4df3de3`

  Charley Cunningham · 2026-02-26 12:52:31 -08:00
  c1afb8815a
• feat: add search term to thread list (#12578)

  Add `searchTerm` to `thread/list` that will search for a match in the
  titles (the condition being `searchTerm` $$\in$$ `title`)

  jif-oai · 2026-02-25 09:59:41 +00:00
  f46b767b7e
• feat: add nick name to sub-agents (#12320)

  Adding random nick name to sub-agents. Used for UX
  
  At the same time, also storing and wiring the role of the sub-agent

  jif-oai · 2026-02-20 14:39:49 +00:00
  0f9eed3a6f
• fix: reduce usage of open_if_present (#11344)
  jif-oai · 2026-02-10 19:25:07 +00:00
  847a6092e6
• fix(tui): fix resume_picker_orders_by_updated_at test (#10769)

  I think this was due to https://github.com/openai/codex/issues/10752
  landing and not rebased on top of
  9ee746afd6

  Owen Lin · 2026-02-05 18:03:10 +00:00
  5c0fd62ff1
• feat(tui): add sortable resume picker with created/updated timestamp toggle (#10752)

  ## Summary
  
  - Add sorting support to the resume session picker with Tab key toggle
  - Sessions can now be sorted by either creation time or last updated
  time
  - Display the current sort mode in the picker header
  - Default to sorting by creation time (most recent first)
  
  ## Changes
  
  - Add `sort_key` field to `PickerState` to track current sort order
  - Pass sort key to `RolloutRecorder::list_threads()` for proper backend
  sorting
  - Add Tab key handler to toggle between `CreatedAt` and `UpdatedAt`
  sorting
  - Show current sort mode ("Created at" / "Updated at") in header
  - Add "Tab to toggle sort" keyboard hint
  - Intelligently hide secondary date column when terminal is narrow
  - Reload session list when sort order changes
  
  ## Test plan
  
  - [x] Unit tests for sort key toggle functionality
  - [x] Snapshot tests updated for new header format
  - [x] Test that Tab key triggers reload with new sort key
  - [x] Test column visibility adapts to narrow terminals

  Felipe Coury · 2026-02-05 09:08:31 -08:00
  22545bf206
• Leverage state DB metadata for thread summaries (#10621)

  Summary:
  - read conversation summaries and cwd info from the state DB when
  possible so we no longer rely on rollout files for metadata and avoid
  extra I/O
  - persist CLI version in thread metadata, surface it through summary
  builders, and add the necessary DB migration hooks
  - simplify thread listing by using enriched state DB data directly
  rather than reading rollout heads
  
  Testing:
  - Not run (not requested)

  jif-oai · 2026-02-05 16:39:11 +00:00
  9ee746afd6
• Session picker shows thread_name if set (#10340)

  - shows names of threads in the ResumePicker used by `/resume` and
  `codex resume` if set, default to preview (previous behaviour) if none
  - adds a `find_thread_names_by_ids` that maps names to IDs in
  `codex-rs/core/src/rollout/session_index.rs`. It reads sequentially in
  normal (instead of reverse order in `codex resume <name>`) the index
  mapping file. This function is called from a list of session (default
  page is 25, pages loaded depends of height of terminal), for which most
  of them will always have at least one session unnamed and require the
  whole file to be read therefore. Could be better and sqlite integration
  will make this better
  - those reads won't be needed when leveraging sqlite
   
  
  Opened questions:
  - We could rename the TUI "Conversation" column to "Name" or "Thread"
  that would feel more accurate. Could be a fast-follow if we implement
  auto-naming as it'll always be a name instead?

  pap-openai · 2026-02-02 08:13:17 +00:00
  1644cbfc6d
• chore(instructions) Remove unread SessionMeta.instructions field (#9423)

  ### Description
  - Remove the now-unused `instructions` field from the session metadata
  to simplify SessionMeta and stop propagating transient instruction text
  through the rollout recorder API. This was only saving
  user_instructions, and was never being read.
  - Stop passing user instructions into the rollout writer at session
  creation so the rollout header only contains canonical session metadata.
  
  ### Testing
  
  - Ran `just fmt` which completed successfully.
  - Ran `just fix -p codex-protocol`, `just fix -p codex-core`, `just fix
  -p codex-app-server`, `just fix -p codex-tui`, and `just fix -p
  codex-tui2` which completed (Clippy fixes applied) as part of
  verification.
  - Ran `cargo test -p codex-protocol` which passed (28 tests).
  - Ran `cargo test -p codex-core` which showed failures in a small set of
  tests (not caused by the protocol type change directly):
  `default_client::tests::test_create_client_sets_default_headers`,
  several `models_manager::manager::tests::refresh_available_models_*`,
  and `shell_snapshot::tests::linux_sh_snapshot_includes_sections` (these
  tests failed in this CI run).
  - Ran `cargo test -p codex-app-server` which reported several failing
  integration tests (including
  `suite::codex_message_processor_flow::test_codex_jsonrpc_conversation_flow`,
  `suite::output_schema::send_user_turn_*`, and
  `suite::user_agent::get_user_agent_returns_current_codex_user_agent`).
  - `cargo test -p codex-tui` and `cargo test -p codex-tui2` were
  attempted but aborted due to disk space exhaustion (`No space left on
  device`).
  
  ------
  [Codex
  Task](https://chatgpt.com/codex/tasks/task_i_696bd8ce632483228d298cf07c7eb41c)

  Dylan Hurd · 2026-01-17 16:02:28 -08:00
  80d7a5d7fe
• feat(app-server, core): return threads by created_at or updated_at (#9247)

  Add support for returning threads by either `created_at` OR `updated_at`
  descending. Previously core always returned threads ordered by
  `created_at`.
  
  This PR:
  - updates core to be able to list threads by `updated_at` OR
  `created_at` descending based on what the caller wants
  - also update `thread/list` in app-server to expose this (default to
  `created_at` if not specified)
  
  All existing codepaths (app-server, TUI) still default to `created_at`,
  so no behavior change is expected with this PR.
  
  **Implementation**
  To sort by `updated_at` is a bit nontrivial (whereas `created_at` is
  easy due to the way we structure the folders and filenames on disk,
  which are all based on `created_at`).
  
  The most naive way to do this without introducing a cache file or sqlite
  DB (which we have to implement/maintain) is to scan files in reverse
  `created_at` order on disk, and look at the file's mtime (last modified
  timestamp according to the filesystem) until we reach `MAX_SCAN_FILES`
  (currently set to 10,000). Then, we can return the most recent N
  threads.
  
  Based on some quick and dirty benchmarking on my machine with ~1000
  rollout files, calling `thread/list` with limit 50, the `updated_at`
  path is slower as expected due to all the I/O:
  - updated-at: average 103.10 ms
  - created-at: average 41.10 ms
  
  Those absolute numbers aren't a big deal IMO, but we can certainly
  optimize this in a followup if needed by introducing more state stored
  on disk.
  
  **Caveat**
  There's also a limitation in that any files older than `MAX_SCAN_FILES`
  will be excluded, which means if a user continues a REALLY old thread,
  it's possible to not be included. In practice that should not be too big
  of an issue.
  
  If a user makes...
  - 1000 rollouts/day → threads older than 10 days won't show up
  - 100 rollouts/day → ~100 days
  
  If this becomes a problem for some reason, even more motivation to
  implement an updated_at cache.

  Owen Lin · 2026-01-16 20:58:55 +00:00
  f1653dd4d3
• feat: wire fork to codex cli (#8994)

  ## Summary
  - add `codex fork` subcommand and `/fork` slash command mirroring resume
  - extend session picker to support fork/resume actions with dynamic
  labels in tui/tui2
  - wire fork selection flow through tui bootstraps and add fork-related
  tests

  Anton Panasenko · 2026-01-12 10:09:11 -08:00
  4223948cf5
• chore: unify conversation with thread name (#8830)

  Done and verified by Codex + refactor feature of RustRover

  jif-oai · 2026-01-07 17:04:53 +00:00
  116059c3a0
• chore: migrate from Config::load_from_base_config_with_overrides to ConfigBuilder (#8276)

  https://github.com/openai/codex/pull/8235 introduced `ConfigBuilder` and
  this PR updates all call non-test call sites to use it instead of
  `Config::load_from_base_config_with_overrides()`.
  
  This is important because `load_from_base_config_with_overrides()` uses
  an empty `ConfigRequirements`, which is a reasonable default for testing
  so the tests are not influenced by the settings on the host. This method
  is now guarded by `#[cfg(test)]` so it cannot be used by business logic.
  
  Because `ConfigBuilder::build()` is `async`, many of the test methods
  had to be migrated to be `async`, as well. On the bright side, this made
  it possible to eliminate a bunch of `block_on_future()` stuff.

  Michael Bolin · 2025-12-18 16:12:52 -08:00
  3d4ced3ff5
• Fixed resume matching to respect case insensitivity when using WSL mount points (#8000)

  This fixes #7995

  Eric Traut · 2025-12-16 16:27:38 -08:00
  42b8f28ee8
• add slash resume (#7302)

  `codex resume` isn't that discoverable. Adding it to the slash commands
  can help

  Ahmed Ibrahim · 2025-12-03 11:25:44 -08:00
  2ad980abf4
• improve resume performance (#7303)

  Reading the tail can be costly if we have a very big rollout item. we
  can just read the file metadata

  Ahmed Ibrahim · 2025-12-02 16:39:40 -08:00
  1ef1fe67ec
• tui: add branch to 'codex resume', filter by cwd (#6232)

  By default, show only sessions that shared a cwd with the current cwd.
  `--all` shows all sessions in all cwds. Also, show the branch name from
  the rollout metadata.
  
  <img width="1091" height="638" alt="Screenshot 2025-11-04 at 3 30 47 PM"
  src="https://github.com/user-attachments/assets/aae90308-6115-455f-aff7-22da5f1d9681"
  />

  Jeremy Rose · 2025-11-19 00:47:37 +00:00
  526eb3ff82
• Update user instruction message format (#6010)
  pakrym-oai · 2025-10-30 18:44:02 -07:00
  2371d771cc
• feat: annotate conversations with model_provider for filtering (#5658)

  Because conversations that use the Responses API can have encrypted
  reasoning messages, trying to resume a conversation with a different
  provider could lead to confusing "failed to decrypt" errors. (This is
  reproducible by starting a conversation using ChatGPT login and resuming
  it as a conversation that uses OpenAI models via Azure.)
  
  This changes `ListConversationsParams` to take a `model_providers:
  Option<Vec<String>>` and adds `model_provider` on each
  `ConversationSummary` it returns so these cases can be disambiguated.
  
  Note this ended up making changes to
  `codex-rs/core/src/rollout/tests.rs` because it had a number of cases
  where it expected `Some` for the value of `next_cursor`, but the list of
  rollouts was complete, so according to this docstring:
  
  
  https://github.com/openai/codex/blob/bcd64c7e7231d6316a2377d1525a0fa74f21b783/codex-rs/app-server-protocol/src/protocol.rs#L334-L337
  
  If there are no more items to return, then `next_cursor` should be
  `None`. This PR updates that logic.
  
  
  
  
  
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/5658).
  * #5803
  * #5793
  * __->__ #5658

  Michael Bolin · 2025-10-27 02:03:30 -07:00
  5907422d65
• Add new thread items and rewire event parsing to use them (#5418)

  1. Adds AgentMessage,  Reasoning,  WebSearch items.
  2. Switches the ResponseItem parsing to use new items and then also emit
  3. Removes user-item kind and filters out "special" (environment) user
  items when returning to clients.

  pakrym-oai · 2025-10-22 10:14:50 -07:00
  3c90728a29
• revert /name for now (#4978)

  There was a regression where we'd read entire rollout contents if there
  was no /name present.

  dedrisian-oai · 2025-10-08 17:13:49 -07:00
  4300236681
• feat: Set chat name (#4974)

  Set chat name with `/name` so they appear in the codex resume page:
  
  
  https://github.com/user-attachments/assets/c0252bba-3a53-44c7-a740-f4690a3ad405

  dedrisian-oai · 2025-10-08 16:35:35 -07:00
  ec238a2c39
• Separate interactive and non-interactive sessions (#4612)

  Do not show exec session in VSCode/TUI selector.

  pakrym-oai · 2025-10-02 13:06:21 -07:00
  4c566d484a
• normalize key hints (#4586)

  render key hints the same everywhere.
  
  
  
  | Before | After |
  |--------|-------|
  | <img width="816" height="172" alt="Screenshot 2025-10-01 at 5 15 42
  PM"
  src="https://github.com/user-attachments/assets/f88d5db4-04bb-4e89-b571-568222c41e4b"
  /> | <img width="672" height="137" alt="Screenshot 2025-10-01 at 5 13 56
  PM"
  src="https://github.com/user-attachments/assets/1fee6a71-f313-4620-8d9a-10766dc4e195"
  /> |
  | <img width="816" height="172" alt="Screenshot 2025-10-01 at 5 17 01
  PM"
  src="https://github.com/user-attachments/assets/5170ab35-88b7-4131-b485-ecebea9f0835"
  /> | <img width="816" height="174" alt="Screenshot 2025-10-01 at 5 14 24
  PM"
  src="https://github.com/user-attachments/assets/6b6bc64c-25b9-4824-b2d7-56f60370870a"
  /> |
  | <img width="816" height="172" alt="Screenshot 2025-10-01 at 5 17 29
  PM"
  src="https://github.com/user-attachments/assets/2313b36a-e0a8-4cd2-82be-7d0fe7793c19"
  /> | <img width="816" height="134" alt="Screenshot 2025-10-01 at 5 14 37
  PM"
  src="https://github.com/user-attachments/assets/e18934e8-8e9d-4f46-9809-39c8cb6ee893"
  /> |
  | <img width="816" height="172" alt="Screenshot 2025-10-01 at 5 17 40
  PM"
  src="https://github.com/user-attachments/assets/0cc69e4e-8cce-420a-b3e4-be75a7e2c8f5"
  /> | <img width="816" height="134" alt="Screenshot 2025-10-01 at 5 14 56
  PM"
  src="https://github.com/user-attachments/assets/329a5121-ae4a-4829-86e5-4c813543770c"
  /> |

  Jeremy Rose · 2025-10-02 18:34:47 +00:00
  ec98445abf
• Add Updated at time in resume picker (#4468)

  <img width="639" height="281" alt="image"
  src="https://github.com/user-attachments/assets/92b2ad2b-9e18-4485-9b8d-d7056eb98651"
  />

  Ahmed Ibrahim · 2025-10-01 10:40:43 -07:00
  d78d0764aa
• [Core]: add tail in the rollout data (#4461)

  This will help us show the conversation tail and last updated timestamp.

  Ahmed Ibrahim · 2025-09-29 14:32:26 -07:00
  16057e76b0
• pageless session list (#3194)
  Jeremy Rose · 2025-09-24 13:44:48 -07:00
  42847baaf7
• Introduce rollout items (#3380)

  This PR introduces Rollout items. This enable us to rollout eventmsgs
  and session meta.
  
  This is mostly #3214 with rebase on main

  Ahmed Ibrahim · 2025-09-09 23:52:33 +00:00
  43809a454e
• Generate more typescript types and return conversation id with ConversationSummary (#3219)

  This PR does multiple things that are necessary for conversation resume
  to work from the extension. I wanted to make sure everything worked so
  these changes wound up in one PR:
  1. Generate more ts types
  2. Resume rollout history files rather than create a new one every time
  it is resumed so you don't see a duplicate conversation in history for
  every resume. Chatted with @aibrahim-oai to verify this
  3. Return conversation_id in conversation summaries
  4. [Cleanup] Use serde and strong types for a lot of the rollout file
  parsing

  Gabriel Peal · 2025-09-08 17:54:47 -04:00
  5eaaf307e1