editor_corecredits each transaction to a person or an agent; an agent's are pending until accepted or reverted. Reverts are selective: any transaction can go, as long as no later one touched the same things (footprints of object properties, component fields, and what was created or destroyed, children and components included). The reverted transaction leaves the undo history, so the rest still undoes cleanly.- Permission levels: open, review (default), approve destructive, approve all. Edits that need approval are proposals: nothing changes until a person approves; rejected ones never apply.
- The MCP server serves a review panel on localhost (token in the link, host checked): the agent's presence (client name, last tool, mode, scene), each transaction's changes in words, Accept/Revert/Approve/Reject, Accept all, and the permission level. Panel requests run on the main thread between tool calls through the server's task channel. The agent reads outcomes with
review_status. - An e2e test drives the panel over HTTP: revert under a later edit, a destroy waiting for approval, a refused action.
- Next: saving back to
.unity, FBX meshes and sub-assets by file ID, ScriptableObjects,.asmdefassemblies, MCP resources and theexectool.
Phase 4 · Slice 4 ·