2 Commits

• ollama: default to Responses API for built-ins (#8798)

  This is an alternate PR to solving the same problem as
  <https://github.com/openai/codex/pull/8227>.
  
  In this PR, when Ollama is used via `--oss` (or via `model_provider =
  "ollama"`), we default it to use the Responses format. At runtime, we do
  an Ollama version check, and if the version is older than when Responses
  support was added to Ollama, we print out a warning.
  
  Because there's no way of configuring the wire api for a built-in
  provider, we temporarily add a new `oss_provider`/`model_provider`
  called `"ollama-chat"` that will force the chat format.
  
  Once the `"chat"` format is fully removed (see
  <https://github.com/openai/codex/discussions/7782>), `ollama-chat` can
  be removed as well
  
  ---------
  
  Co-authored-by: Eric Traut <etraut@openai.com>
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  Devon Rifkin · 2026-01-13 09:51:41 -08:00
  fe03320791
• feat(tui2): copy tui crate and normalize snapshots (#7833)

  Introduce a full codex-tui source snapshot under the new codex-tui2
  crate so viewport work can be replayed in isolation.
  
  This change copies the entire codex-rs/tui/src tree into
  codex-rs/tui2/src in one atomic step, rather than piecemeal, to keep
  future diffs vs the original viewport bookmark easy to reason about.
  
  The goal is for codex-tui2 to render identically to the existing TUI
  behind the `features.tui2` flag while we gradually port the
  viewport/history commits from the joshka/viewport bookmark onto this
  forked tree.
  
  While on this baseline change, we also ran the codex-tui2 snapshot test
  suite and accepted all insta snapshots for the new crate, so the
  snapshot files now use the codex-tui2 naming scheme and encode the
  unmodified legacy TUI behavior. This keeps later viewport commits
  focused on intentional behavior changes (and their snapshots) rather
  than on mechanical snapshot renames.

  Josh McKinney · 2025-12-10 22:53:46 +00:00
  90f262e9a4