Version Control

Every change to your prompts is automatically tracked, allowing you to review history, compare versions, and restore previous states. Never lose work or wonder “what did it look like before?”

How Versioning Works

Automatic Versioning

The editor creates version snapshots automatically:

Smart Deduplication

Versions are only created when content actually changes:

1. Each save computes a SHA-256 hash of the content
2. If the hash matches the latest version, no new version is created
3. This prevents duplicate versions from repeated saves

Viewing History

Open the History Tab

1. Click the History tab in the editor header
2. Or use the keyboard: navigate with arrow keys after selecting tabs

History Timeline

Versions are displayed in a timeline grouped by date:

Today
├── v12 (2 hours ago) - edit
├── v11 (3 hours ago) - auto
└── v10 (4 hours ago) - edit

Yesterday
├── v9 (deployed)
└── v8 (auto)

Dec 20 - Dec 24
└── v7, v6, v5...

Version Information

Each version card shows:

Filtering Versions

Use filters to find specific versions:

Search

Search by version number:

• Type 12 to find version 12
• Type v12 or just 12 — both work

Comparing Versions

Select Versions

1. Click the checkbox on up to 2 versions
2. Click Compare button that appears
3. View side-by-side diff

Diff View

The comparison shows:

• Left panel: Older version
• Right panel: Newer version
• Highlights: Added (green), removed (red), changed (yellow)

Restoring a Version

From History Tab

1. Find the version you want to restore
2. Click the Restore button (or right-click menu)
3. Confirm the restoration

What Happens

1. The editor content is replaced with the version’s content
2. Metadata is restored to that version’s state
3. A new version is NOT automatically created — your current work becomes the restored content
4. Save manually (Cmd + S) to create a new version if desired

Partial Restoration

To copy just specific content:

1. Click View on a version to open the details modal
2. Click Copy Content to copy to clipboard
3. Paste specific sections into your current prompt

Version Details Modal

Click View on any version to see full details:

Information Shown

• Version number and timestamp
• Full content (scrollable)
• Metadata snapshot at that version
• Injected prompts referenced at that time
• Deployment info if linked

Actions Available

Source Types Explained

auto — Automatic Saves

Created by the auto-version system every 2 minutes while editing. These are your safety net — work is captured even if you don’t manually save.

Characteristics:

• Created silently (no notification)
• Only created if content changed
• Lower priority for cleanup (if implemented)

edit — Manual Saves

Created when you press Cmd + S or click Save. These represent intentional checkpoints.

Characteristics:

• Triggered by explicit user action
• Good for marking meaningful milestones
• Higher priority for retention

deploy — Deployment Versions

Created when you deploy a prompt to production. These are linked to deployment records.

Characteristics:

• Always linked to a deployment ID
• Captures exact state sent to production
• Critical for rollback capability

rollback — Rollback Versions

Created when you roll back to a previous deployment. Documents the restoration.

Characteristics:

• References the deployment being restored
• Creates audit trail for compliance
• Links back to original deploy version

Content Hash

Each version includes a SHA-256 content hash:

Why Hashes Matter

1. Deduplication: Prevents duplicate versions
2. Integrity: Verify content hasn’t changed
3. Comparison: Quickly check if two versions are identical

Viewing the Hash

The hash isn’t prominently displayed but is used internally. In version comparisons, the system can tell you if two versions have identical content even if they’re days apart.

Best Practices

1. Save Before Major Changes

Press Cmd + S before starting a significant rewrite. This creates a checkpoint you can return to.

2. Use Descriptive Commits (Future)

When prompted for descriptions, add context:

• “Added error handling section”
• “Simplified greeting logic”
• “Fixed variable name typo”

3. Review Before Deploying

Always check the diff between your current version and the last deployment:

1. Select current version
2. Select last deployed version
3. Compare to see all changes going to production

4. Don’t Fear Experimentation

With automatic versioning, you can experiment freely:

• Try radical changes
• Restore if they don’t work
• Compare different approaches

5. Clean Up Occasionally (Future)

If you accumulate many auto-versions, future features may allow:

• Archiving old versions
• Keeping only milestone versions
• Exporting version history

Troubleshooting

”No versions found”

The prompt was just created and hasn’t been saved yet. Save once (Cmd + S) to create the first version.

Versions not appearing

1. Check your filter settings (are you filtering out the type you’re looking for?)
2. Wait a moment — versions update asynchronously
3. Refresh the page if versions seem stale

Can’t restore version

1. Verify you have edit permissions
2. Check if the prompt is locked by another user
3. Try refreshing and attempting again

Lost work after restore

Restoring replaces your current content. If you need the pre-restore content:

1. Check for a recent auto-version before the restore
2. Look for the restore action which may have created a version

Version Storage

What’s Stored

Each version captures:

• Content: Full prompt text
• Metadata: Variables, tags, settings
• Context: Prompt name and path at that time
• Injections: List of prompts referenced

Retention

Currently, all versions are retained indefinitely. Future updates may include:

• Retention policies
• Archive functionality
• Export capabilities

Privacy

Version history is:

• Only visible to organization members
• Not included in public shares
• Excluded from API key access by default