Use numbered CLI review findings for short follow-up prompts

Open 💬 0 comments Opened Jun 4, 2026 by joshka

Variant

CLI

What feature would you like to see?

CLI review findings should be rendered with user-facing numbers so users can refer to specific findings in short follow-up prompts like fix 1, fix 1,2,7, or explain 3.

Review findings currently appear as unnumbered bullets. This makes the user's next prompt more awkward than it needs to be, especially after a review with several findings.

Each finding should have a stable user-facing number in the rendered CLI review output so the user can refer to it directly. This is primarily a CLI UX affordance for concise follow-up prompts, not an attempt to make the model infer item identity from prose.

Expected CLI output should use numbered list markers:

  1. Finding title
  2. Another finding title
  3. Another finding title

Additional information

Codex was unable to find an existing related issue.

This is mostly a CLI concern. The app likely wants a more explicit UX for common follow-up actions, such as buttons or controls for fix, explain, fix all, and similar actions, rather than relying primarily on the user typing numbered references.

Source notes from local exploration: the structured review formatter appears to hardcode unordered markers in codex-rs/core/src/review_format.rs, and tests currently assert the - ... format in codex-rs/core/tests/suite/review.rs. The general final-answer prompt also biases normal review responses toward unordered bullets, so a complete fix may need both structured review formatting and review-specific prompt guidance.

View original on GitHub ↗