Commit & compare versions
Turn a working draft into a version you can point to, then compare a few side by side
A prompt starts out as a draft you’re still editing. Running it once and committing turns that draft into a version, one that sticks around after you move on to the next edit.
Commit a version
This picks up with the support-agent template already open in the editor, either fresh from Create a prompt or one you’re mid-edit on.
Click Run Prompt to produce an output; see Run a prompt for the full walkthrough of messages, models, and variables. Running is also what clears the Draft badge next to the version number, which is the same thing that enables Commit. Until then, hover the disabled button and the tooltip reads, “Please run the prompt before saving and committing”. It also greys out while more than one version is loaded for comparison, and the tooltip still shows that same message.
Click Commit in the editor header. This opens the Commit changes to prompt dialog. Type a message in the Commit message field, something like “Added escalation trigger for refund requests”, since both Commit and Commit and set as a default version stay disabled until you do. Pick Commit to save the version as is, or Commit and set as a default version to save it and also make it the template’s default in the same step.
Once you click Commit, the dialog closes and a snackbar confirms it, something like Commit for <prompt> <version> successful (or ...and set as default if you picked Commit and set as a default version instead). The version now shows up under Commit History, which lists just the versions you’ve committed.
Compare versions
Line up a few versions to see how they differ before you decide which one to promote.
Click More in the editor header, then History. It lists every version, including drafts you haven’t committed yet; Commit History narrows that down to the ones you’ve committed.
Click Select to compare to turn on checkboxes next to each version. The version already open in the editor comes pre-checked and locked, and it counts as one of the three, so you’re picking at most two more.
Click Compare, which appears once you’ve checked at least one version. Each selected version opens in its own panel, showing its messages, its own last saved output, and its own model configuration side by side, often the detail that differs most between versions.
Warning
Three is the hard cap. Once three are checked, the remaining checkboxes go disabled with “Compare limit is upto 3 version only, Deselect other options to select this one”. Deselect one to swap in another.
Promote a version
Comparing tells you which version should be live. Making it live isn’t a commit or compare action, it’s a labelling one: you point the Production label at the version you picked instead of changing the version itself. To do it from your own code, use the SDK & API reference.
Dive deeper
Questions & Discussion