Skip to main content

Versioning & drafts

Power user & admin

Every agent has a draft you're editing and a published version that users see. The toolbar's Unsaved badge tells you which is which.

Prerequisites​

  • Edit access to an agent, either as its creator or via org-level permissions.

The lifecycle​

  1. Draft. When you open an agent for editing (agent card → drawer → ⋮ → Edit agent), the top toolbar shows an Unsaved badge (it appears as soon as edit mode opens) alongside a save icon, Test, Publish, and a ⋯ menu (Duplicate / Share / Version history / Delete). The draft is yours, and not visible to other users yet. The save icon stores the draft without publishing.

  2. Test. Click Test in the toolbar. You chat with the draft (not the published version), so you can validate changes before exposing them.

  3. Publish. Click Publish (labelled Publish Agent when creating a new one). The Unsaved badge clears, a new entry is added to the agent's version history, and other users see your changes the next time they open a chat with this agent.

Version history & rollback​

Every publish, including the first, adds a version to the agent's history. To browse it, open the agent for editing and pick ⋯ → Version history. A Version History panel slides in on the right, one row per version ("Version 2 · <author> · 1 minute ago"). Each row's ⋯ menu has a single action: Restore.

Practices that save you grief​

  • Publish small. Ship one change at a time. If you change instructions, the model, and tools all at once, you won't know what broke when a regression appears.
  • Test before publish. Always use the Test button on a representative prompt set first.
  • Document the change. Use the agent's description field (max 750 characters on the Settings tab) to note what's new or different.
  • Coordinate co-owners. If multiple admins can edit, agree on who publishes and when. A draft saved with the save icon is stored server-side (the agent gets its /agents/<id>/edit URL immediately, even before first publish) and survives reloads; unsaved changes exist only in your current session.

Tips & gotchas​

tip

If a publish accidentally breaks the agent for users, the fastest fix is ⋯ → Version history → Restore on the last known-good version. Don't try to live-debug in production.

Heads up

There is no autosave: leaving the editor with the Unsaved badge showing prompts "Discard this edited agent?" and discarding loses the changes. Clicking the save icon flips the badge to Saved and persists the draft server-side, so it will still be there after a reload. Publish or save before stepping away.

AgentsCreate your first agentFull walkthrough including the publish step.AgentsShare & discoverWho sees a newly published agent and how to control it.EvaluationEvaluation overviewCatch regressions across versions with automated evals.