Checkpoints and undo

What you can do

• Go back to a step. "Return the scene to the 'Place the table' step" — the scene becomes what it was right after that step.
• Undo the last change. "Undo the last change" — the scene goes back to how it was before the AI's latest change. Everything changed after it, including your manual edits, goes back too; the AI tells you the point it returned to and which of its steps were undone.
• Undo a return. Changed your mind? "Put it back." This works until you start changing the scene again.
• Save your own checkpoint. Before a bold edit: "save a checkpoint called 'before lighting'". You can return to it later.
• See the history. "Show me the latest steps" — the AI lists them, newest first. In chats that show app panels, the history is also in the Blender Bridge panel.

How it works

• A checkpoint is the whole Blender scene. A return restores the entire scene, not a single property. Renders, exported models and other files on disk stay where they are.
• If the scene is already saved to a file, a return updates its .blend file too; Blender Bridge saves backups first.
• Steps are the AI's work. Your manual edits in Blender don't become separate steps; they become part of the scene before the AI's next step.
• A backup is saved before every return, so you can undo the return until you keep working.
• Recent history is kept. The oldest checkpoints make room for new ones over time.

Use it well

• Try variations boldly. Ask for three lighting options one after another, then go back to the best one.
• Save your own checkpoint before a big rework — "save a checkpoint called 'base done'".
• Save important results as a file. Checkpoints are for working on the scene; a .blend file in your project folder is for what you want to keep: "save the scene".

More on what the AI does in Blender: What AI can do in Blender.

Next step: connect ChatGPT, Claude or Codex to Blender.