Undo and Redo

I like to think of my session contexts more as "resources" than "conversations." They're ultimately logs of text, so it's easy to build tools for manipulating them. Just like git makes manipulating code changes super powerful, some agent session management tools can edit session context in ingenious ways.

The /undo command rolls back the last response the model gave you. If OpenCode captured a matching filesystem snapshot, it also restores the files changed by that response!

After running /undo and before submitting another prompt, you can use /redo to restore the conversation and files to the state that you just rolled back from. That said, submitting a new prompt makes the undo permanent, so you can no longer redo it!

OpenCode's snapshot capture requires a Git repository and is on a best-effort basis. /undo can't reverse all side effects of shell commands, e.g., changes to databases or files outside the working repo, effects on running processes, and network operations. So, it's a convenience, but not a replacement for good Git hygiene and backups.

hallucinate(-✅)✨

hallucinate(-1)✨