Prompt versioning: every edit leaves a restore point
Prompt versioning is keeping a history of how a prompt changed, so an edit that made results worse can be undone. Convergence snapshots a prompt the first time it changes in an editing session, records who made the change and when, and lets you restore any earlier version. Restoring is non-destructive: the current version is snapshotted first, so a restore can itself be undone.
By Ijan Kruizinga · Published September 1, 2026
What gets saved, and when
The first time you change a prompt in a session, Convergence saves a snapshot of how it looked beforehand. One snapshot per editing session, not one per keystroke — a history you can actually read, rather than a log you have to sift.
Open a prompt’s ⋯ menu and choose Version history to see the timeline, with each change attributed to the person who made it and stamped with when.
Restoring is non-destructive
Restoring an earlier version snapshots the current one first. That means a restore is never a one-way door: if you roll back and decide the newer wording was better after all, it is still there.
This matters more with prompts than with documents. A prompt that quietly stopped working is usually the result of a well-meant edit weeks ago, and the fix is finding the version that worked — not rewriting it from memory. It matters most on the prompts a team runs constantly, which are usually templates with fill-in blanks.
One shared timeline when several people can edit
When a prompt sits in a shared folder, everyone in that folder can edit it — and everyone sees the same version history, with every change attributed. There is no per-person fork of the truth.
It also answers the question that comes up the first week of any shared library: who changed this, and can we go back? The timeline is the answer, and it is available to every member rather than just an admin.
Versions and drafts are different things
A draft is a status, not a version. Every prompt autosaves as a draft while you write, and editing a published prompt flips it back to Draft until someone publishes again — a signal about how settled the content is. Version history is the separate record of what the prompt used to say.
The distinction matters when several people work on the same prompt: Draft tells a reader "this is moving right now", version history tells them "here is what it said before". More on how the two fit together in the guides.
Why versioning belongs on prompts specifically
Prompts are executable text: a small wording change can move output quality a long way, and the effect is often noticed days later by someone who did not make the edit. That is the same reason source code is version-controlled, and the reason prompt evaluation practice — see Anthropic’s guidance on testing and iterating on prompts — assumes you can compare one version against another.
Frequently asked questions
What is prompt versioning?
Prompt versioning is keeping a history of how a prompt changed over time, so you can see what it used to say, who changed it, and restore an earlier version if an edit made results worse.
How often is a version saved?
Once per editing session. The first change you make in a session snapshots how the prompt looked beforehand, so the history stays readable instead of recording every keystroke.
Can I undo a restore?
Yes. Restoring snapshots the current version first, so the wording you restored away from is still in the history and can be restored back.
Do teammates see the same version history?
Yes. When a prompt is in a shared folder, everyone in that folder sees one shared timeline with each change attributed to the person who made it.
Is version history included on the free plan?
Yes. Version history is part of every prompt, including on the free individual plan. A workspace adds the shared, attributed timeline across a team.