Checkpoints
Rewind a conversation by editing a message, try another answer, and how file checkpoints work.
Rewind a conversation
Step 1
Stop the turn if the bot is working
You can only edit while the bot isn't working. Stop the turn first if you need to.
You're done when: the bot is idle.
Step 2
Edit an earlier message
Hover over one of your earlier messages and choose Edit message. Change it and send.
You're done when: your changed message is sent.
Step 3
Move between branches
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're done when: you can switch between the old and the new branch.
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. Files such as
node_modulesand.envare never snapshotted. - Best effort. Checkpoints are a best-effort fallback. If a snapshot fails, the turn carries on without it.
- No restore screen yet. Restoring a checkpoint isn't available from the app's screens yet.