Prompt Version Manager

The Prompt Version Manager is a browser-only workspace for saving named snapshots of your prompts, comparing two versions side by side, restoring an earlier version to the working editor, and exporting your session history as plain text or JSON. Everything runs in your browser's memory and is cleared when you close or reload the page. Nothing is uploaded, stored on a server, or shared.

No. Prompt Compare performs an immediate side-by-side diff between two separate inputs — it has no history and no snapshot storage. Prompt Version Manager maintains a session-only list of named snapshots and lets you compare any two of them, restore a version to the editor, and export the full history. They serve different workflows: use Prompt Compare for a quick one-off diff and Prompt Version Manager for iterative revision tracking within a session.

Versions are kept only in this page's temporary memory for the current browser session. They are cleared when you close the tab, reload the page, or navigate away. If you want to preserve your history beyond the session, use the Export .txt or Export .json button to download a file before closing.

No. The tool runs entirely in your browser. No API is called, no LLM receives your text, no network request is made, and no analytics service logs your prompt content. Your text never leaves the browser tab.

The session limit is 50 versions per session. This bound exists to keep memory usage reasonable. When the limit is reached, a warning is shown and the Save Snapshot button is disabled. You can delete an existing version to free a slot, or export and clear the history to start fresh.

Yes. Each individual snapshot is limited to 200 KB of prompt text (approximately 200,000 characters). Very large prompts beyond this limit are rejected with a warning and must be shortened before saving.

The comparison uses a deterministic Myers diff algorithm on the line-split text of both selected versions. It produces three categories: lines added (shown in green with a + prefix), lines removed (shown in red with a − prefix and strikethrough), and unchanged lines (shown in muted grey with a space prefix). The algorithm does not score, rank, or editorialize — it only shows structural differences. The diff is non-destructive and does not modify any stored snapshot.

Yes, but you will see the result "The selected versions have identical text." The diff output will be empty and the summary will show 0 added, 0 removed, and N unchanged lines. This is useful for confirming that two versions labeled differently actually contain the same prompt text.

Restoring a version copies its prompt text into the working editor. A confirmation dialog is shown before restoring, and if the editor contains unsaved text you are warned that it will be replaced. Restoring does not modify the stored snapshot — the original version remains in the session list unchanged.

Not automatically. If you restore a version and want to go back to what was in the editor before, save a snapshot before restoring and then use that snapshot to restore the previous state. The tool does not maintain an undo stack for the working editor beyond the standard browser text undo (Ctrl+Z).

Duplicate creates a new snapshot in the session list containing the same text, note, and tag as the original but with a new timestamp and the label "(copy)" appended. It is added to the end of the list. This is useful when you want to use an existing version as a starting point for further editing without overwriting the original.

A confirmation dialog is shown before deletion. Once confirmed, the version is removed from the session list immediately. If that version was selected in a comparison slot, the slot is cleared. Deletion cannot be undone within the session, so export the history first if you want a record.

The .txt export contains a header with the export timestamp, the total version count, and a session-only disclaimer. Each version is preceded by a separator line with its index and label, followed by its save time, tag, note, character/word/line counts, and full prompt text. The file is UTF-8 encoded and can be opened in any text editor.

The .json export contains a top-level object with the tool name, export timestamp in ISO 8601 format, a sessionOnly flag set to true, and a versions array. Each element in the array has the version index, label, tag, note, savedAt ISO timestamp, a stats object with chars/words/lines/bytes counts, and the full prompt text. The format is designed to be reimported into this tool in a later session.

Yes. Click the Import .json button in the toolbar, select a .json file that was previously exported from this tool, and the versions are added to your current session list. The import reads the file locally in the browser and never uploads it. Each imported version receives a new in-session timestamp. Versions are validated before import — entries without a text field are skipped. If the session limit would be exceeded, excess entries are skipped with a count shown in the status bar.

No. Only .json exports from this tool are supported for re-import because the JSON format contains structured metadata (label, note, tag, stats) that allows faithful reconstruction. Plain-text exports are intended for human reading and do not have a parseable structured format.

Yes. Once the page has loaded in your browser, the entire tool works without an internet connection. All snapshot storage, diffing, export, and import processing happens in browser memory and does not require any network access.

Git and similar systems provide durable, persistent storage, branching, merging, remote synchronization, and audit trails. This tool provides none of those. It is a lightweight, session-scoped scratch pad for iterating on prompts within a single working session. When the page closes, all versions are gone unless you exported them. Think of it as a local notebook rather than a version control system.

Prompt Template Builder is for authoring reusable prompt templates with named placeholder variables that you fill in with different values. Prompt Version Manager is for tracking and comparing the actual text of a prompt across multiple revisions as you refine it. They serve different stages of the prompt authoring workflow.

Yes. Before clicking Save Snapshot, you can enter an optional note (up to 500 characters) describing what changed in this revision and an optional tag (up to 40 characters) such as "draft", "final", or "baseline". Both are shown in the version list and included in exports. They are stored as plain text and never processed or interpreted by the tool.

If the label field is empty when you click Save Snapshot, a label is generated automatically in the form "Version N" where N is the next sequential number. Labels are truncated to 80 characters. You can give every snapshot a descriptive name to make the version list easier to scan, but a label is not required.

The current tool is intentionally session-only and has no account system, no server-side storage, no sharing, and no collaboration features. A future hosted version with persistent storage, team workspaces, and shared prompt registries may be considered, but any such feature would require explicit sign-in, user consent, and clear data-retention disclosures. For now, export your session to a file if you need persistence.

No. The tool does not read or write to localStorage, sessionStorage, IndexedDB, cookies, or any other browser storage mechanism. All state is held in JavaScript variables that exist only for the lifetime of the current page. Closing or reloading the page discards all data.

Yes. The Myers diff algorithm is deterministic given the same two inputs — it always produces the same output for the same pair of version texts regardless of when you run it or how many other versions are in the list. The comparison never scores, weights, or interprets prompt quality; it only reports structural line-level differences.