Exaro StudioApprovals & undo
Other tools let an agent change your project and then tell you what it did. Exaro Studio shows you first, waits, and applies the change as one transaction you can undo.
The lifecycle of a change
Of the 287 tools in the build, 72 are read-only and run immediately — searches, inspections, log tails, screenshots. The other 215 mutate the project, and every one of them takes this path:
- Preview. The tool computes what would change without touching any state, and writes a plain-language summary of it.
- Queue. The entry appears in
Window → Exaro Studio MCPwith that summary, the raw arguments, and a warning if the operation cannot be undone. - Block. The calling agent waits. Nothing has happened to your project yet.
- Apply. On approval the change runs inside a single Unreal transaction — one entry in
Edit → Undo History, oneCtrl+Zfrom gone.
Your options on each entry
- Approve — apply this one call.
- Always allow — apply it and stop asking about this tool in this project. Good for the noisy safe ones (
ex_asset_save,ex_blueprint_compile). Listed under “Always allowed”, revocable at any time. - Reject — the agent is told no, with your reason, and continues from there.
- Approve all / Reject all — for when an agent queues a burst of related calls and you have read enough.
The point of “Always allow” is fatigue. An approval queue you click through without reading is worse than none, because it feels like review. Allowlist the boring tools so the entries you do read are the ones that matter.
Irreversible operations
Some changes cannot be wrapped in a transaction: writing an asset to disk, deleting a package, editing a .cpp file. Those entries carry an explicit “This action cannot be undone (no Ctrl+Z)” marker before you approve, not after.
Auto-approve (YOLO)
The panel has an Auto-approve everything toggle, and the MCP server honours HS_MCP_AUTO_APPROVE=1 for scripted runs. Both skip review entirely, including non-undoable writes and deletes. Enabling the toggle asks you to confirm.
EditorPerProjectUserSettings.ini, so it survives an editor restart. If you turned it on to run a batch, turn it back off — check the panel before you assume approvals are live.Why this is the whole product
Tool count is commodity; Epic ships hundreds in 5.8. What is not commodity is being able to point an agent at a project you have shipped work into and not lose an afternoon to a confident, wrong refactor. Preview, approve, undo. That is the bet. See how that compares →