[TUI][Warp] view_image succeeds but no inline image is rendered

What version of Codex CLI is running?

codex-cli 0.144.4

A newer 0.145.0 release is available, but its release notes do not list terminal image preview support and the general tracking issue remains open.

What subscription do you have?

ChatGPT subscription; the exact tier is not reported by Codex CLI diagnostics.

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Darwin 27.0.0 arm64 arm (macOS 27.0, build 26A5388g)

What terminal emulator and version are you using?

Warp v0.2026.07.22.09.01.preview_01

No tmux or zellij. Relevant environment:

TERM=xterm-256color
TERM_PROGRAM=WarpTerminal
TERM_PROGRAM_VERSION=v0.2026.07.22.09.01.preview_01

Codex doctor report

Sanitized to omit local paths and repository metadata:

{
  "overallStatus": "ok",
  "codexVersion": "0.144.4",
  "model": "gpt-5.6-sol",
  "modelProvider": "openai",
  "platform": "macos-aarch64",
  "installMethod": "npm",
  "terminal": "Warp",
  "terminalVersion": "v0.2026.07.22.09.01.preview_01",
  "colorterm": "truecolor",
  "term": "xterm-256color",
  "multiplexer": "none",
  "latestVersionReportedByDoctor": "0.145.0"
}

What issue are you seeing?

When the agent calls the built-in view_image tool for a local JPEG in the Codex TUI running inside Warp, the tool call succeeds and the model receives the image, but the user sees no inline image preview.

The TUI only shows the Viewed Image tool activity. There is no visible image, fallback file path, or action to open the image externally. No error is reported.

What steps can reproduce the bug?

1. Open Warp on macOS.
2. Run codex to start the interactive TUI.
3. Place a JPEG on disk, for example /tmp/example.jpeg.
4. Prompt Codex: Display /tmp/example.jpeg.
5. Let the agent call view_image.
6. Observe that the tool call completes and the model can inspect the image, but Warp shows only Viewed Image and no image preview.

This was reproduced multiple times with different JPEG files in the same interactive session.

What is the expected behavior?

Because Warp supports the Kitty Image Protocol on macOS and Linux, Codex TUI should render a terminal-native image preview when view_image succeeds.

If inline rendering is intentionally unavailable, the TUI should at least show the resolved file path and provide a clear fallback such as an external-open action.

Warp documents Kitty Image Protocol support in its changelog entry for 2025-03-26: https://docs.warp.dev/changelog

Additional information

Related to #29451, which tracks inline image artifacts in the Codex TUI generally. This report provides a concrete Warp compatibility reproduction where a supported terminal graphics protocol is available but view_image output is still invisible to the user.

The model-side image input works correctly; the missing part is user-visible TUI rendering.