DocsStay in control
Stay in control
Each chat's approval setting decides what the agent may do without asking you. Whatever it does, you see it, Undo takes one change back, and a snapshot takes back a whole request.
Approvals: the three settings#
The shield button in the message box shows the chat's setting. Click it to choose another. The button and the menu word the settings a little differently:
| Button reads | Menu row | What it means |
|---|---|---|
| Approve for me | Auto · bounded edits | The default. Edits made with Angelo's own checked tools apply on their own once Angelo has checked them against your scene: objects, materials, modifiers, animation, sculpt passes and the like. |
| Ask for approval | Ask before changes | Every change to your scene waits on a card for you to approve it. |
| Read only | Read only | The agent can look at your scene and talk about it. Every change is refused. |
A change you make while the agent works applies to what comes next.
What always asks#
Even in Auto, these show a card and wait for you:
- Python scripts, with their exact code (unless you turn on Always allow scripts, below).
- Writing or deleting files with the agent's file tools.
- Image and 3D generation and Generation Flow runs, which spend your API credits.
- Renders, bakes and exports the agent starts for you.
- Importing from or saving to your team's library, and importing a generated 3D model into your scene.
- Switching the workspace mode, or asking a model on another account to help.
Approval cards#
A card that waits for you says Needs your approval, what kind of action it is, and Uses API credits when it costs money. Approve runs it; Decline refuses it. For a script, the button reads Review & approve and first shows you the code.
Some bigger changes are built on a copy of your scene first and shown as a preview: Preview · not applied, with how many things it adds, changes and removes. Nothing in your scene changes until you click Accept, which asks you to confirm you reviewed it and applies it as one Undo step. Discard throws the copy away.
Scripts and Always allow scripts#
When Angelo's own tools can't do something, the agent may write a Python script. Scripts can reach your files, the network and other apps, so each one asks and shows its code.
Always allow scripts lets scripts run without asking, in chats set to Auto only: Ask still asks and Read only still refuses. Turn it on from a script's approval card or in Preferences ▸ AI Providers ▸ Agent permissions; only Preferences turns it off. A script that touches your preferences or Angelo itself still asks. Scripts sent by an outside app (Claude Code and Codex) always show their code.
A script that is already running can't be stopped halfway; Stop cancels what comes after it.
Undo#
Each change the agent applies is its own step in Blender's Undo history, named Apply Approved Blender Change. A request that makes several changes makes several steps, so you can step back through them. Accepting a preview is one step, and so is adding a base mesh (Start from a base mesh).
Undo covers your scene. It doesn't take back files the agent wrote, what a script did outside Blender, or unsaved pixel edits in images; for those, see what a snapshot covers below.
Restore a snapshot#
By default Angelo saves a private copy of your scene before it sends each request. If the copy can't be saved, the request doesn't start. Each of your messages then shows Restore snapshot.
- Stop any chat that is working (restoring needs every chat idle).
- Click Restore snapshot under the message. The dialog says what will happen; confirm with Restore snapshot.
- Angelo first saves a safety snapshot of the scene as it is now, then opens the recovered scene as a working copy. Your original .blend file is not overwritten: use File ▸ Save As to keep the result.
The chat's history stays. Files the agent wrote with its file tools since then are put back too; renders, bakes and exports stay where they are. Until you Save As, saving goes to the recovered copy, not your original file. To go back on a restore, click Undo restore in the chat's note about it.
What a snapshot can't bring back
- What a Python script did outside your scene, exports you made, or anything sent over the network.
- Pixel edits in images that were unsaved when the snapshot was taken. Before you restore, Angelo names such images; save them first to keep the edits.
- Your preferences, which live outside the scene.
Snapshot Settings#
Open the chat's title menu at the top of the chat and choose Snapshot Settings.
| Setting | What it does |
|---|---|
| Every Request (default) | A snapshot before every request, so every message can be restored. |
| Before First Approved Edit | A snapshot just before a request's first change instead. Requests that only look get none, and the snapshot includes edits you made after sending. |
| Storage limit | 2 GB by default; 0 means no limit. Parts of the scene that didn't change are stored once, so this usually holds many restore points. |
| Maximum snapshots, maximum age | Unlimited by default. |
When a limit is reached the oldest restore points go first; the snapshot of a running request and safety snapshots are kept. A removed point keeps a greyed-out Restore link. The agent can't change these settings.
Stop#
While Angelo works, the send button is a square Stop. Stop cancels whatever is still queued; nothing waiting is applied, and changes already applied stay and can be undone. Work built on a copy stops between steps and is never applied. Esc doesn't stop a request; it closes menus.
Settings your organization manages#
Your IT department can lock some of this, for example require Ask for every chat or turn Always allow scripts off. A locked setting says Turned off by your organization, and AI Providers lists what is managed. Your own choice comes back if the policy is lifted. See Teams.