Checkpoints
Rewind a conversation by editing a message, try another answer, and how file checkpoints work.
You can take a conversation back to an earlier point and go a different way. Separately, Murage quietly snapshots a bot's working folder before each turn.
Rewind a conversation
Hover over one of your earlier messages and choose Edit message. Change it and send. The conversation continues from there as a new branch, and the bot follows the new branch, not the old one.
The old branch isn't lost. Use the ‹ › arrows beside the message to move between branches.
You can only edit while the bot isn't working. Stop the turn first if you need to.
Try another answer
Choose Regenerate response on the bot's last reply to get a fresh answer to the same message. The previous answer stays reachable with the ‹ › arrows.
File checkpoints
When a bot works in a folder you chose for it, Murage takes a snapshot of that folder before each turn. Snapshots are kept in Murage's own data folder, separate from any Git repository in your folder, which Murage never touches.
- Ignored files, such as
node_modulesand.env, are never snapshotted. - Checkpoints are a best-effort fallback. If a snapshot fails, the turn carries on without it.
- Restoring a checkpoint isn't available from the app's screens yet.
Rewinding a conversation doesn't undo changes to files. If a bot changed files you care about, keep your own copy or use version control, and turn on backups.