Working with your assistant

Your assistant edits the same map you have open in Dungeondraft, while you watch. This page covers how to share it, how to take back what you don’t want, and how your work gets saved.

You, your assistant, and any other assistant connected at the same time all edit one map. Anything you move or delete by hand is real to your assistant only once it looks again. It is instructed to re-read the map before telling you what is on it, rather than answering from memory; if a description sounds out of date, ask it to check the map again before you rely on it.

To stop your assistant changing the map, tick Pause AI edits in Settings → MCP Bridge. Every edit is refused until you untick it; your assistant can still look at the map, and tells you it is paused. The pause lasts until you untick it or restart Dungeondraft.

The bridge keeps its own history of your assistant’s edits, up to 1,000 steps, separate from Dungeondraft’s own Ctrl+Z. Ctrl+Z does not undo what your assistant did, and your assistant’s undo does not touch your hand edits.

• Ask your assistant to undo, and it reverses its latest step. A step is one whole request to Dungeondraft: a room, a batch of placed objects, a scatter or a furnishing pass is undone as a unit. Undo always takes the newest step; it cannot reach past it to an older one.
• Ask it to redo, and it puts back the last step it undid.
• Without asking, click Undo the assistant’s last step in the MCP Bridge panel.

Some changes are outside this history and cannot be undone this way, such as resizing or cropping the map. Your assistant tells you when that applies. Save copies of maps that matter.

Before a bigger request, such as a room, a set piece or a lighting pass, your assistant can set a checkpoint. If you don’t like the result, ask it to roll back to that checkpoint: every edit it made since then is undone in one go, and it tells you what was and was not reversed.

A rollback undoes only steps made in this conversation. If another conversation or another assistant edited the map after the checkpoint, the rollback is refused and nothing changes, so it never undoes someone else’s work. It is also refused once the checkpoint is older than the history can reach; when that is getting close, your assistant is warned and should save. You can ask it which checkpoints it has open.

Your assistant saves when you ask, and is instructed to save after each stage of a build, since saving is how work survives a crash. It can save over the map you have open, or as a new file in the save folder. It will not overwrite some other existing map unless you have asked it to replace that file. A map that has never been saved needs a file name, so give it one; otherwise Dungeondraft opens a Save As dialog that holds the assistant up until you close it.

While Dungeondraft is writing a file, it drops any edits made in the meantime. So a save waits until Dungeondraft reports it has finished writing that file, and while a save is under way the bridge refuses edits rather than lose them. Dungeondraft’s own automatic backups count too: an edit that arrives during one is refused with a note to try again in a moment, and your assistant retries.

If a save does not confirm in time, it is probably still running. Your assistant waits for it rather than saving again. If Dungeondraft cannot save at all for the rest of the session, your assistant stops building and tells you, because restarting is the only fix and loses unsaved work.

Your assistant takes screenshots to check its work. It receives each image, but your AI app may not show it to you, or folds it inside the tool call. Ask to see it, and your assistant gives you the path of the saved file, which you can open. Screenshots are kept in the output folder, the newest 20 by default; set how many in the MCP Bridge panel, or click Open output folder there.

For a clean picture of the whole map without Dungeondraft’s interface, ask for an export instead of a screenshot.