Xorin documentation

Safety, verification, and change review

Xorin combines plan review, structured tool validation, persistent checkpoints, and post-change verification. These controls reduce risk but do not remove the need for source control and project testing.

Use Plan mode before a large change

Plan mode creates a reviewable checklist before mutating tools run. You can disable steps, edit or reorder them, add instructions, answer required questions, execute the approved version, or cancel it.

The approved plan becomes the execution record; Xorin does not silently rewrite it after approval.

Verified Plan progress

A Plan step advances only when Xorin receives evidence that matches the approved action and target. A read-only inspection cannot complete a mutation step, an unrelated result cannot complete a verification step, and multiple required outcomes can be checked before a step is marked complete.

When a model requests several tool actions together, Xorin preserves and runs them sequentially. If a required action fails or cannot be verified, the Plan remains incomplete and identifies the failed action instead of presenting the request as successful.

Pending checkpoints

Before a supported mutation runs, Xorin snapshots the affected project state. The checkpoint is designed to survive script-triggered domain reloads and Editor restarts.

A checkpoint remains active until you keep or undo it. Follow-up requests made before that decision accumulate in the same checkpoint. The Changes applied section shows:

Auto-keep

Enable Auto-keep in the composer to keep the active checkpoint after a normally completed request when every change succeeded. Each change is judged by its latest attempt, so a failure that a retry fixed does not block it. A cancellation, request error, or a change that still failed falls back to manual review. Auto-keep was called Auto-approve before Xorin 2.2.0; your setting carries over.

Ask before deleting

Before Xorin deletes an object, component, asset, tag, or layer that the current request did not create, it shows a card listing what will be removed, including parents and children. Choose Delete or Keep. Your answer applies for the rest of the request, and the card closes after 10 minutes without an answer.

Xorin also checks for an unsaved scene before a change that needs it saved, refuses scene edits while Play Mode is starting, and stops an editor script that is still running after 30 seconds, then says what was undone.

Workflows

For larger tasks, Xorin can run many reads and edits together as one workflow instead of one step at a time. A workflow appears as a single card in chat. Workflow edits use the same checkpoint, so Keep changes and Undo changes cover them like any other change. Pressing Stop ends a running workflow and shows what it did.

Work activity and results

While a request runs, a Working line shows the current step, why Xorin is still working (for example, a retry or a script repair), the cost so far, and the time taken. Repeated actions of the same kind are grouped into one row. Enable Show detailed work activity in Settings to expose a collapsed execution record for successful turns. Failures, interruptions, and recovery information remain available without this setting.

When a request finishes, the answer says what changed and what was not tested, and a Scene line lists objects the request added or removed. A checklist shows each part of what you asked for; if some parts were not done, Finish the rest fills the message box with them for you to send.

Stop and spend limit

Press Stop to end a request at any time. Xorin exits Play Mode if it started it, shows what the request cost, and records what the stopped request changed, so asking again does not repeat finished work. A request pauses when it has spent $5; choose Continue to allow another $5, or Stop. Stopping at the spend limit or turn limit applies scripts that are waiting to be applied; if any are not kept, the chat history says so and the script row reads not applied.

Each request-owned task also provides Report. Reporting a task does not cancel, continue, retry, keep, or undo it. See Report a task.

Verification layers

Checkpoint boundaries
  • Keep and Undo operate on the whole active checkpoint, which may contain changes from multiple requests. There is no per-file keep/undo control.
  • Checkpoint creation preserves unsaved scene contents in a sidecar without rewriting the currently open scene file or clearing its dirty marker. Undo changes restores the captured baseline to disk and may reopen the scene clean.
  • External files, provider-side jobs, and changes made outside tracked project paths may not be reversible.
  • Keep the project in source control and commit or stash important work before a broad request.