Skip to main content

Publish and manage agent versions

Publishing promotes the current draft into an immutable production snapshot. It does not automatically make a paused agent active.

Publish a draft​

  1. Wait for the editor to show a successful save.
  2. Test the draft through the channel-appropriate editor test.
  3. Select Publish.
  4. Optionally enter Version Name and Version Note.
  5. Select Publish Version.

Before publishing, the editor flushes the latest changes. The server then validates the configuration schema and current architecture/provider compatibility. For Chat Agents, it also rejects an attached voice-only Call Transfer function.

Atomic publication​

The publish operation performs one database transaction-like RPC flow:

  1. Load the active draft.
  2. Snapshot current agent functions and granular integration tools into its configuration.
  3. Mark the draft published and record its publish time, optional name, and note.
  4. Mark the previously published version archived.
  5. Update the agent's published-version pointer and denormalized runtime fields.
  6. Clear the draft pointer.

When the editor refreshes after publication, it creates a new working draft from the new published version. This is why the editor remains editable immediately after a successful publish.

Version history​

Version History lists published and archived versions newest first. Working drafts do not appear. A version includes the prompt, model, voice, full configuration, and the function/tool snapshots captured when it was published.

Meaningful names and notes make operational review easier. Describe the outcome and risk, such as Added appointment rescheduling or Changed primary model after latency test.

Restore is not an instant rollback​

Selecting Restore creates a new draft copied from the chosen historical version and restores its function/tool snapshots into the working copy. Production continues using the currently published version.

Test the restored draft, then publish it to make that configuration live. The resulting publication receives a new version number; Wirevox does not move the production pointer backward without a new publish.

Discard unpublished changes​

The editor's discard action creates a fresh draft from the current published version. It also reconciles working function/tool attachments to the published snapshots. Confirm before discarding because uncommitted draft changes are not available in Version History.