Skip to main content
// ple
// docs / versioning

Never lose a working prompt again.

Every commit is a version. This page covers committing, comparing, undoing, and citing exact versions.

Committing a version

Edit in the dashboard, then hit Commit. Add a one-line changelog: future-you will search these. For meaningful changes, pick Minor or Major in the save dialog to bump the semantic version (v2.3.0 → v2.4.0 or v3.0.0); plain commits bump the patch number.

Free holds up to 3 versions per prompt: a 4th version (a commit here, or a save from the CLI or MCP) asks you to upgrade, and nothing is deleted. Pro keeps everything. Saves from the CLI, MCP, and Loop land in the same history with their source tagged, so the history is one timeline no matter where you worked.

Comparing versions (diff)

Open a prompt → History tab → pick any two versions → Compare. Changed sections show the old text (red) next to the new text (green), and the three sections diff independently, so a CONTEXT change doesn't drown out an INSTRUCTION tweak.

Rolling back

In History, every non-current version has a Rollback action. Rollback never deletes anything: restoring v3 when v5 is current adds v6, a copy of v3 with the changelog "Rolled back to v3", and makes it current. v4 and v5 stay in the history, so you can roll back to them later, and a rollback can itself be undone the same way. You confirm first; the only thing you lose is unsaved work in the editor.

Related

Want the version history to improve on its own? Loop saves each winning variant as the next version with a Loop(strategy) changelog.