Versions & History

Every save is a new immutable version with a commit message. Diff any two, restore an old one, and pin one as active.

Append-only versioning

Prompts work like Git: you never edit a version in place. When you save, PromptVersions creates a new version with the next sequential number and the commit message you provide. Older versions stay exactly as they were, forever.

• Commit messages — describe what changed (“tightened tone”, “added JSON instruction”) so history reads like a changelog.
• One active version — exactly one version is marked is_active at a time; it's the default the editor opens to.
• Diff — select any two versions to see a side-by-side diff of their content and config.
• Restore — restoring an old version doesn't rewind history; it creates a new version at the tip with the old content.

Saving with a commit message

The Save popover asks for a commit message. If you've connected a provider and selected a model, you can also tick “Run regression tests after save” to automatically evaluate the new version in the background — see Evaluation & Metrics.