How Versioning Works
- Each save creates an immutable version
- Versions are numbered sequentially (v1, v2, v3…)
- Only Live prompts can be set as the endpoint default
- You can view, compare, and restore any version
Version Properties
Viewing Version History
1
Open the Prompt
Navigate to your endpoint’s Prompts tab and click on the prompt.
2
Open Version History
Click the History or Versions button in the prompt editor.
3
Browse Versions
See all versions with timestamps and status indicators.
4
View Details
Click any version to see its full configuration.
Comparing Versions
Compare two versions side-by-side:- Open version history
- Select two versions to compare
- View a diff showing what changed
- What changed between versions
- Why a prompt started behaving differently
- What to restore if something breaks
Status Workflow
Draft → Live
Promote a prompt when it’s ready for production:1
Test Thoroughly
Ensure the prompt works correctly with various inputs.
2
Open Actions Menu
Click the ⋯ menu on the prompt.
3
Select Promote to Live
Click Promote to Live.
4
Confirm
The prompt is now Live and can be set as default.
Live → Default
Set a Live prompt as the endpoint’s default:- Ensure the prompt has Live status
- Click Set as Default in the actions menu
- All requests to the endpoint now use this prompt
Only one prompt can be the default at a time. Setting a new default replaces the previous one.
Demote to Draft
If a Live prompt needs more work:- Click ⋯ → Demote to Draft
- The prompt returns to Draft status
- If it was the default, you’ll need to set a new default
Archive
Remove a prompt from active use:- Click ⋯ → Archive
- The prompt is hidden from lists
- History is preserved for reference
Rollback Scenarios
Something Broke in Production
1
Identify the Issue
Check logs to see when problems started.
2
Open Version History
Find the last working version.
3
Restore
Click Restore this version to create a new version with that content.
4
Promote and Set Default
Promote the restored version and set it as default.
A/B Testing Results
After testing two prompts:- Review metrics (latency, success rate, user feedback)
- Promote the winning prompt to Live
- Set it as default
- Archive the losing prompt
Version Best Practices
Write meaningful changes
Write meaningful changes
Make each version a meaningful improvement. Avoid saving trivial changes.
Test before promoting
Test before promoting
Always test Draft prompts thoroughly before promoting to Live.
Keep one Live prompt as default
Keep one Live prompt as default
Your endpoint should always have a reliable default prompt.
Use Draft for experiments
Use Draft for experiments
Try new models, approaches, or major changes in Draft status.
Document big changes
Document big changes
Use the prompt name or description to note significant changes.
Calling Specific Versions
While your endpoint uses the default prompt by default, you can call specific prompts:Version Limits
When you exceed version limits, oldest versions are archived but not deleted.
Next Steps
Testing Prompts
Learn to test prompts effectively
Prompt Snippets
Create reusable template fragments

