Prompt engineering is iterative, and the hard part is remembering what you changed and why. A single reworded sentence can swing an LLM’s output from useless to excellent — and then a later “improvement” quietly regresses it. The AI Prompt Version Tracker gives each prompt a version history with labels and notes, lets you compare any two versions side by side, and lets you star the one that actually worked, all stored locally in your browser.
How it works
You paste a prompt, give it a label (like “v3 — added role + examples”) and a note describing what changed, and save it. As you iterate, each save becomes a new entry in your history. Select any two entries to see them side by side with a quick summary of how many characters and words were added or removed, so you can gauge how much a version really changed. Star your best performer to pin it, and export the whole history as JSON for backup. Everything is read from and written to your browser’s localStorage — nothing leaves your machine.
Tips and examples
Treat the note field as a lab log: record not just what you changed but what the change did to the output (“v4 — added 2 few-shot examples; cut hallucinated dates”). When a version works, star it immediately — it is much harder to reconstruct later from memory. Use the side-by-side compare before discarding an old version, because a “worse” prompt sometimes contains a phrasing worth keeping. Export to JSON periodically as a backup, since clearing your browser’s site data will wipe the local history; the export is your only safety net.