Add intraline diff highlighting to Codex review.

Open 💬 2 comments Opened May 26, 2026 by liuchongxiao

What version of the Codex App are you using (From “About Codex” dialog)?

codex

What subscription do you have?

plus

What platform is your computer?

windows macos

What issue are you seeing?

Feature request: Add intraline diff highlighting to Codex review.

Current behavior:
Codex shows changed lines in the diff, but when a long prose line is edited, the whole line appears changed. If only one word, number, or phrase was modified, it is hard to identify the exact edit.

Requested behavior:
Keep the normal line-level diff view, but also highlight the changed words, numbers, or phrases inside each changed line. This should work like intraline diff highlighting in GitHub, VS Code, or other code review tools.

Generic example:
Original: The system achieved a score of 0.80 in the final test.
New: The system achieved a score of 0.85 in the final test.

The diff should show the full line for context, but highlight only 0.80 as removed and 0.85 as added.

This is especially useful for LaTeX, Markdown, documentation, and other prose-heavy files where paragraphs are often stored as long lines.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019e6400-57e7-7ea2-8e32-9e6abc95da43

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

jparta · 2 months ago

This would be a great improvement.
Reviewing code changes in the CLI is much more sluggish than it needs to be due to the lack of a word-level diff. Viewing the changes in an IDE or using git diff doesn't work if the agent made additional changes without a commit in between.

Scenario:

  1. changeset \#1
  2. user reviews changes, gives notes
  3. changeset \#2

Because there was no commit between the changesets, the quality of the tool output which shows the diffs is very important.

anywaypridyrok · 2 months ago

Disclosure: I’m building DiffReceipt, a small tool around AI-code review evidence.

+1 to intraline highlighting. For review, the problem is often not just “show me the changed file”, but “show me the actual decision-relevant change.”

In long prose/config lines, whole-line diffs make the review trail noisy. A receipt/review view could combine:

  • intraline diff
  • changed-file summary
  • task/scope
  • checks run
  • human-review status

That would make AI-generated changes easier to inspect without forcing reviewers to reconstruct the intent from raw diffs.