Repository navigation
[FEATURE] Undo message only - keep file changes (like Claude Code) #7963
Description
Feature Request
Add an option to undo/remove AI messages from conversation history while preserving file changes.
Current Behavior
The /undo command reverts both:
- The conversation message
- The file changes made by AI
There's no way to keep the file changes while cleaning up the conversation history.
Requested Behavior
Add a new command or option like:
/undo --keep-filesor/undo -k/forget(removes message only)- Or a separate UI button for "Remove message, keep changes"
Use Cases
-
Conversation cleanup: After AI makes correct changes through multiple back-and-forth messages, I want to clean up the messy conversation history while keeping the final working code.
-
Context management: Long conversations eat up context window. Being able to remove old messages while keeping their file changes helps manage context efficiently.
-
Iterative development: AI made changes across 5 messages. The code is good now, but I don't need all that conversation history cluttering my session.
Prior Art
Claude Code has this feature - you can undo messages while preserving file changes. It's extremely useful for keeping conversations clean without losing work.
Environment
- OS: Windows 11
- OpenCode version: Latest
Related Issues
/undocommand only rolls back AI conversation message, not the associated file changes #5474 (opposite problem - wants file changes to also revert)- [FEATURE]: I want to be able to edit the context to delete messages #7712 (edit context to delete messages)
- Feature Request: Add
redoableparameter to control permanent message deletion after revert #4681 (redoable parameter for revert)
Activity
github-actions commentedon Jan 12, 2026
This issue might be a duplicate of existing issues. Please check:
/undocommand only rolls back AI conversation message, not the associated file changes #5474:/undocommand only rolls back AI conversation message, not the associated file changes (opposite problem - wants file changes to also revert)redoableparameter to control permanent message deletion after revert #4681: Feature request to addredoableparameter to control permanent message deletion after revertThese issues discuss related functionality around managing conversation history and file changes. Feel free to ignore if your specific use case differs from these.
IgorWarzocha commentedon Jan 31, 2026
@SYRS-AI you're looking for
in your global opencode.json
kanaka commentedon Feb 19, 2026
I would like this functionality too. Sometimes I want to revert file changes but most of the time I want to only revert to a previous prompt (without reverting the files too). I use this all the time for managing the context window:
For example, I would like to see another option in this dialog such as "Revert undo message but keep file changes":
Note, there is also a bug in that dialog in that if you have snapshots disabled, the current option is misleading because it will not in fact revert files changes too.
github-actions commentedon Apr 21, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
phazei commentedon Apr 27, 2026
This is still an issue
stcrd commentedon Apr 28, 2026
would be a great feature, keep the changes, clean the chat, win-win
franciscorubin commentedon Aug 12, 2026
This is the most basic feature...
qzhhhi commentedon Aug 14, 2026
This is A FUCKING BASIC FEATUREEEE
LuisBalsa commentedon Sep 11, 2026
Hi! I'd like to +1 this feature request. Like many others here, I frequently need to revert conversation messages without losing the file changes made by the agent.
Use case: After the AI makes correct code changes through several back-and-forth messages, I want to clean up the conversation history to free context window, while keeping the working code intact. Currently,
/undoreverts both messages and files, which forces me to either keep a cluttered conversation or lose my work.What I've tried: PR #16447 implemented this with a
modeparameter ("conversation"vs"conversation_and_code"), but it was closed by the bot after 60 days of inactivity. The feature and the approach looked solid.Suggestion: Could this be reconsidered for a future release? Even a simple flag like
/undo --keep-fileswould be a great start. This is a standard feature in Claude Code and significantly improves the development workflow.Thanks for considering!