unity-workflow

Use history_undo with a steps parameter for multi-step undo, or workflow_undo_task to revert an entire recorded task by its taskId. For conversation-level rollback, call workflow_session_undo with the session ID.

Call workflow_task_start first, then workflow_snapshot_object with the object name or instanceId before running modification skills like component_set_property. The snapshot lets workflow_undo_task restore the previous state later.

Yes, the workflow history is persistent, so recorded tasks and sessions survive Editor restarts. You can list them with workflow_list or workflow_session_list and undo specific tasks by ID at any time.

editor_undo handles a single immediate undo step, while workflow_session_undo reverts all changes grouped under a recorded session. Use history_undo with steps for multi-step undo within the current history stack.

Snapshot-related skills require an active task started with workflow_task_start. However, workflow_undo_task itself works on already-saved tasks listed by workflow_list, so verify the taskId exists in the persistent history first.

Creation operations like gameobject_create, component_add, prefab_instantiate, material_create, and ui_create_* are auto-tracked when a session or task is active. Modification operations trigger automatic snapshots of target objects before changes when possible.