Bring back the “View changes / Undo” toolbar removed after v0.4.5

Resolved 💬 4 comments Opened Oct 1, 2025 by rippleSK Closed Nov 5, 2025

What version of the VS Code extension are you using?

0.4.15

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 22.6.0 arm64 arm

What steps can reproduce the bug?

Dear Codex team,

In Codex VS Code extension v0.4.5, after edits were applied there was a very useful toolbar right above the chat window with two buttons:

  • View changes → opened a Git-style diff to inspect Codex’s proposed modifications.
  • Undo → reverted the change in a single click.

This feature disappeared in later versions (≥0.4.6). The current workflow relies on standard editor undo (Cmd+Z / Ctrl+Z) or Git diffs, but that is not equivalent:

  • The contextual diff was immediate and specific to Codex’s last edit (not mixed in with other edits).
  • The one-click Undo was safer and faster than manually undoing or navigating Git history.
  • For quick iteration and debugging, this was an essential part of the workflow.

Could you please bring this feature back, or at least make it available via a setting/toggle in the extension?

Many of us found it invaluable for trust, transparency, and productivity when working with AI-driven edits.

Thank you

What is the expected behavior?

Codex makes changes
Reports in the chat window
2 buttons are present just above the chat window.
One says « Undo » to undo changes made by Codex. This one is optional as we could Cmd/Ctrl+z the changes.
The other button is « View changes »: this opens a tab with a diff view specific to before after the current changes made by Codex. Very very useful, no immediate alternative. VS code source control is not a solid alternative for uncommitted code. This feature let us precisely verify whatever Codex is doing. Priceless. Please bring it back

What do you see instead?

No « Undo » or « View changes » button

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗