You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AI: zed removes all AI changes when editing a message with no checkpoints consideration #39997
If you edit a message all AI changes will be lost, initially I though this is a design decision,
But know I noticed that if lets say you send 5 messages and with each message there was changes, and you edit the 5th one
I would expect that only the changes between the 4th and 5th messages will be removed, but instead all changes are removed
I'm not sure whats a good solution for this, maybe add a checkpoint after each user prompt but that might break workflows that expected that all their changes are reversible, I guess the best way would be to be able to reverse each change individually and the changes are stacked on each other, so u can undo 5th change 4th change , undoing 1st change should also undo the changes on top of it
The current workaround is to remember to use "Keep all" but in practice its not always obvious that you want to keep the changes yet
The way checkpoints work in RooCode and Copilot is way better than Zed; you can go back to specific points.
At the very least, before reverting the checkpoints; Zed would show you a snippet of your prompts and the work that will be undone, like:
"You are about to roll back changes from:
Make me a great app
Fix the UI add more buttons
etc etc "
or better yet; have a revertible check point after every change like Roo and Copilot
Zed development moves fast and a significant number of bugs become outdated. If you can reproduce this bug on the latest stable Zed, please let us know by leaving a comment with the Zed version, it helps us focus on the right issues. If the bug doesn't appear for you anymore, feel free to close the issue yourself; otherwise, the bot will close it in a couple of weeks. But even after it's closed by the bot, you can leave a comment with the version where the bug is reproducible and we'll reopen the issue. (This bot will only ask about this issue once) Thanks!
This issue was closed due to inactivity. If you're still experiencing this problem, please leave a comment with your Zed version so that we can reopen the issue.
Activity
ConradIrwin commentedon Oct 16, 2025
The way checkpointing works is definitely something we want to revisit as we work on the panel, as you say, it's not super obvious how...
somtooo commentedon Nov 6, 2025
same thing has happened to me. thanks for digging into the issue. i just started making sure i commit often but now i know what happened. bless
fileports-code commentedon Mar 28, 2026
The way checkpoints work in RooCode and Copilot is way better than Zed; you can go back to specific points.
At the very least, before reverting the checkpoints; Zed would show you a snippet of your prompts and the work that will be undone, like:
"You are about to roll back changes from:
or better yet; have a revertible check point after every change like Roo and Copilot
github-actions commentedon Jul 3, 2026
Zed development moves fast and a significant number of bugs become outdated. If you can reproduce this bug on the latest stable Zed, please let us know by leaving a comment with the Zed version, it helps us focus on the right issues. If the bug doesn't appear for you anymore, feel free to close the issue yourself; otherwise, the bot will close it in a couple of weeks. But even after it's closed by the bot, you can leave a comment with the version where the bug is reproducible and we'll reopen the issue. (This bot will only ask about this issue once) Thanks!
github-actions commentedon Jul 31, 2026
This issue was closed due to inactivity. If you're still experiencing this problem, please leave a comment with your Zed version so that we can reopen the issue.