Skip to main content

Understanding Version History for AI Agents

Learn how version history works and how to review past configurations for your AI agents.

Maria Cairns avatar
Written by Maria Cairns
Updated over a week ago

Why it matters

Version history helps you track every change made to an agent’s configuration. This visibility ensures you can audit updates, understand when behavior changed, and maintain consistent performance. Version tracking is essential for both messaging and calling, since the agent’s behavior depends entirely on the version active at the time of the interaction.

Key Concepts

Version: A saved snapshot of your agent’s configuration at a specific point in time.

Editor save: Every time you save changes in the editor, a new version is automatically created.

Version metadata: Information such as who made the change and when it was saved.

Linked version: The exact version an agent used during a call or chat, visible in interaction logs.

Step-by-Step: View Version History

  1. Open your agent in the editor.

  2. Click the Versions tab at the top of the screen.

  3. Review the list of all saved versions.

  4. Check who created or edited each version and the timestamps.

  5. Sort versions by creation date if needed.

  6. Click a version to view its configuration snapshot.

  7. Compare versions to see how instructions, settings, tools, or parsing configurations have changed over time.

Tips and Best Practices

  • Save changes intentionally so each version reflects a meaningful update.

  • Use version timestamps to correlate behavior changes with call or chat outcomes.

  • Before major edits, take note of the current version for easier troubleshooting later.

  • Review the version linked to specific calls or chats to understand why the agent responded a certain way.

  • Avoid frequent minor saves that create unnecessary clutter in the version list.

Troubleshooting

Issue

Possible Cause

Fix

Agent behavior changed unexpectedly

A recent version altered instructions or settings

Review recent versions and compare with earlier snapshots

Hard to trace which version caused an issue

Version history not monitored regularly

Use interaction logs to identify which version was used and analyze that snapshot

Agent feels inconsistent

Many small edits made without intentional versioning

Consolidate edits into deliberate saves and document major changes

Did this answer your question?