TUI composer: selected file paths should render and delete as atomic elements

Open 💬 0 comments Opened May 21, 2026 by yamamel

What version of Codex CLI is running?

codex-cli 0.132.0

What subscription do you have?

plus

Which model were you using?

gpt-5.4-mini

What platform is your computer?

Darwin 25.5.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Ghostty + zellij

Codex doctor report

What issue are you seeing?

When using @ file search in the TUI composer, selecting a file inserts the path as plain text. It looks the same as normal input, and deleting it does not behave like a single atomic token.

What steps can reproduce the bug?

  1. Open the TUI composer.
  2. Type @ and select a file from the file search popup.
  3. Observe the inserted path.
  4. Try deleting the inserted path.

What is the expected behavior?

Selected file paths should be rendered with a distinct style, and deleting them should remove the whole path as one unit, similar to other atomic composer elements.

Additional information

This seems like a UI bug in the composer path insertion flow. The path should likely be inserted as an atomic text element so it can render distinctly and delete cleanly as a whole.

View original on GitHub ↗