Drafts and saved versions

Your draft is the editable working copy of a prompt. It belongs to you, while saved versions belong to the organization. Editing your draft does not change another member's draft, a saved version, or the production label.

Save a version

For a new prompt, complete the initial baseline to create version 1. After setup, edit messages or generation settings in your draft, review the changes, and save a new version. The resulting snapshot is immutable and receives a version number.

Use a saved version for a repeatable comparison. It identifies the prompt configuration, while the evaluation records the dataset and results used in that run. The prompt's shared dataset can change independently of the saved version.

View or replace a draft

Opening a saved version lets you inspect it without losing your working draft. To use an older version as a starting point, explicitly replace the draft with that content, review the replacement, and save a new version when ready. This creates a new snapshot rather than rewriting the old one.

Discarding or resetting a draft removes your unsaved changes. Review the confirmation before proceeding, especially if you have edited the same draft through both the dashboard and a CLI or assistant.

Resolve concurrent edits

Draft writes carry a revision. If two tabs or clients update the same personal draft, a stale write conflicts rather than silently replacing the newer content. Read the latest draft, compare it with your intended change, and submit an intentional update using the current revision.

A version save also checks the draft revision, so the saved snapshot is the draft you reviewed. Do not respond to a conflict by automatically fetching a revision and saving unknown content.

Saving a later version does not release it. Continue with comparison and label publication.