What is Version History?
Version History provides Git-like version control for your agent configurations. It allows you to track changes, review previous versions, rollback to earlier configurations, and manage multiple development branches.Version History ensures you never lose your work and can always revert to a known-good configuration.
Accessing Version History
Version History is located in the right panel of the Advanced Editor. Click the “Git Changes” or “History” tab to access it.Key Concepts
Versions
Each saved configuration is a version. Versions are numbered and timestamped:| Property | Description |
|---|---|
| Version Number | Auto-incrementing identifier (v1, v2, v3…) |
| Timestamp | When the version was created |
| Commit Message | Description of changes |
| Author | Who made the changes |
Branches
Work on different variations of your agent simultaneously:| Branch Type | Description |
|---|---|
| Main | Primary development branch |
| Live | Production version (what customers experience) |
| Custom | Your own feature or testing branches |
Live Version
The “Live” version is what’s deployed to production. Only the Live version is used for actual customer calls.Viewing Changes
Pending Changes
See what modifications haven’t been committed yet:Change Details
Each pending change shows:- What was modified (greeting, prompt, settings, etc.)
- Previous value
- New value
Committing Changes
Save your changes as a new version:AI-Generated Commit Messages
Let AI suggest a commit message based on your changes:- Click the ”✨ Generate” button
- Review the suggested message
- Edit if needed
- Commit
Browsing History
View all previous versions:Version Information
Each version entry shows:| Field | Description |
|---|---|
| 🔢 Version | Version number |
| 📅 Date | When it was created |
| 💬 Message | Commit message |
| 🏷️ Tags | Live, Latest, etc. |
Restoring Versions
Rollback to a previous configuration:Managing Branches
Creating a Branch
Switching Branches
- Open the Branches tab
- Click on the branch you want to use
- The editor loads that branch’s configuration
Deleting Branches
- Open the Branches tab
- Click the delete icon on the branch
- Confirm deletion
Publishing to Live
Deploy your changes to production:Only the Live version handles actual customer calls. Development versions don’t affect production.
Best Practices
Commit Often
Commit Often
Save versions frequently so you have more restore points.
Write Good Messages
Write Good Messages
Descriptive commit messages make history easier to navigate.
Use Branches for Experiments
Use Branches for Experiments
Create branches when testing major changes to avoid affecting your main configuration.
Test Before Publishing
Test Before Publishing
Always test in Playground before marking a version as Live.
Review Before Rollback
Review Before Rollback
Check what changed between versions before restoring an old one.
Common Workflows
Quick Fix
- Make change
- Test in Playground
- Commit with message
- Publish to Live
Major Update
- Create a new branch
- Make multiple changes
- Test thoroughly
- Merge to main
- Publish to Live
Rollback
- Identify the issue
- Find last working version
- Restore that version
- Publish to Live
- Debug the broken version