Regression Bug Report: Plan Mode Rich Patch View Missing

Open 💬 1 comment Opened Mar 4, 2026 by michaeltufar

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

0.4.79

What subscription do you have?

Plus

What platform is your computer?

VSC on Win11, Working with CODEX locally and also "Remote -SSH" on Linux

What issue are you seeing?

Regression Bug Report: Plan Mode Rich Patch View Missing

Summary

Since March 4, 2026 (Europe/Berlin), Plan mode no longer shows the per-file visual patch/compare UI during manual approval flow.
Instead, only plain Markdown/unified diff text is shown.

Actual Behavior

Only plain diff code blocks / text diffs are shown.
The visual per-file patch renderer is missing in the approval flow.

Regression Window

  • Worked until: March 3, 2026 ~23:30 (Europe/Berlin)
  • Broken from: March 4, 2026
  • No local VS Code update was installed between these times.

Environment

  • OS: Windows, Win11
  • Editor: VS Code, 1.108.2
  • Agent: Codex integration, 0.4.79
  • Same behaviour on lokal Win11 workspaces and "Remote - SSH" connected Linux remotes.

Request

Please confirm:

  1. Whether this is a known regression or feature-flag rollout effect.
  2. How to re-enable the prior per-file rich patch renderer.
  3. Whether any temporary setting/workaround exists.

What steps can reproduce the bug?

Reproduction Steps

  1. Create a small test file (e.g. 5 lines).
  2. In Plan mode, request one-line change with manual approval.
  3. Ask for preview and approve with yes.
  4. Observe that no rich per-file patch card appears; only plain diff text is rendered.

What is the expected behavior?

Expected Behavior

In Plan mode, for each touched file, render the rich inline patch block (similar to “Edited file” compare view) so manual approval can be done visually per file.

Additional information

Impact

This removes the previously reliable visual review UX for per-file approvals and makes change verification slower/error-prone.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗