Versions and rollback

Versioning gives a run or deployment a stable definition of the system it used.

Tree versions

A tree version is an immutable snapshot of its structure and executable configuration. Create versions at meaningful checkpoints, such as before a provider change, prompt release, or deployment.

Use comparison and diff views to review structural, prompt, connector, and policy changes. Rollback restores earlier state by creating a new current state; it does not rewrite the historical record.

Prompt block history

Prompt blocks also keep their own edit history. Each change records role, timestamp, and before/after content. This supports a narrow rollback when only one instruction changed.

Runs and exports

Record the version used for important runs. Tree and project exports can be pinned to an existing version so a runtime bundle does not silently include unreviewed later edits.

curl -H "X-Orchetree-Role: developer" \
  "http://localhost:8000/api/v1/export/tree/1?pin_version=4" \
  --output tree-v4.bundle.json

Imported trees receive an initial version snapshot, giving the destination a known rollback point.

See Roles and governance, Runs and traces, and MCP and bundles.