Skip to main content

Edit and autosave agent drafts

Opening an agent editor ensures that the agent has an editable draft. If no draft exists, Wirevox clones the current published version; if the agent has never been published, it clones the agent's initial configuration.

Draft initialization also restores the published snapshot of attached functions and granular integration tools into the editor's working copy.

Continuous autosave​

Voice and Chat editors use a 750 ms debounce after a meaningful configuration change. The header reports Saving, the last successful save time, or Save failed.

Wirevox forces a save before:

  • leaving through the editor's Back control;
  • opening the agent test;
  • publishing;
  • changing active or paused status from the editor.

The autosave hook also attempts a background keepalive save when the page becomes hidden or unloads, and retries dirty state when the browser returns online. A background attempt is best-effort; confirm the saved indicator before closing a critical edit.

Draft content​

The versioned draft contains the system prompt, voice, model, and complete agent configuration. Unknown configuration fields are preserved so an older editor does not erase newer settings.

Agent name, avatar, and operational status are base agent metadata and are changed directly rather than treated as version-history content. Phone assignment and Website Chat deployment configuration are also separate lifecycle resources.

Function and tool attachments are maintained as a working copy and frozen into the version when published. Knowledge selection stored in the agent configuration is versioned with that configuration; the knowledge base's documents remain a separate shared workspace resource.

Unpublished changes​

Wirevox compares the draft with the current published prompt, voice, model, configuration, and published function/tool snapshots. The editor displays an unpublished-changes indicator when they differ.

Saving removes local dirty state but does not remove the unpublished distinction. Only publishing promotes those changes to production.

Save failure​

If the header shows Save failed, do not publish, test, navigate away, or assume the draft is durable. Restore connectivity, make a small controlled change, wait for Saved, and reload the editor to verify the stored value.