Versions and publishing

Every agent has a published version — what members see — and a draft — what you're editing. Publishing snapshots the draft into a new version; the history is permanent.

Draft auto-save

Every edit — instructions, tool changes, identity changes on custom agents — writes to the draft. The editor header shows the current draft version number. The save uses optimistic concurrency: if someone else publishes between your edits, your save is rejected and you'll be prompted to refresh.

Publishing

Publish opens a confirmation dialog that summarizes what changed. Confirm, and the draft becomes a new published version — the version number increments. Members and triggers immediately switch to the new version.

Version history

Version history opens a dialog listing every published version with the publisher, timestamp, and a preview. Select a version to compare it side-by-side with the current draft or another version.

Restoring

Restore as draft copies an earlier version into the current draft without publishing. Restore and publish copies the version into the draft and immediately publishes it as a new version. Restore never overwrites history — the restored content becomes a new version.

Reset to default (catalog only)

Catalog agents have a Reset to default action. It wipes all customizations — instructions overlay, tool selections, and model overrides — and restores Opisense's default configuration for that catalog slug. The action is logged in the activity log and is reversible by restoring the previous version.

Revert to version 1 (custom only)

Custom agents don't have a "default" — they have a version 1 (the initial publish). Revert to version 1 restores the agent to its earliest published state.

The activity log

Every draft save, publish, restore, and reset is recorded with actor and timestamp. The activity log slides out from the top-right corner of the editor.

What's next?