Version History - Meetzy Docs

What is Version History?

Version History provides a complete Git-based version control system for your AI agent configurations, featuring real-time collaboration, intelligent conflict resolution, and safe production deployment workflows. Every modification is tracked with detailed change diffs, collaborative editing locks, and professional commit workflows similar to GitHub or GitLab.

Version History operates like a professional development environment with Git-style workflows. Track changes in real-time, collaborate safely with team members, resolve conflicts intelligently, commit with descriptive messages, and deploy to production with confidence. Your entire development history is preserved with comprehensive audit trails.

Accessing Version History

Version History is seamlessly integrated into the Advanced Editor interface with two main access points:

Git Status in Header Bar

The editor header displays comprehensive Git status with real-time collaboration indicators:

Status badges: Live indication of working tree state (Clean, Modified, Conflicts, Syncing, Locked)
Version display: Current version number with immediate updates
Collaboration indicators: Active user presence and edit locks
Quick action toolbar: Integrated Check, Pull, and Commit buttons

Changes Panel

Access the full version control interface through the right panel “Changes” tab, providing:

Pending Changes: Review all modifications with detailed diffs before committing
History Timeline: Complete chronological version history with deployment status
Commit Workflow: Professional commit interface with AI-powered message generation

Git-Style Status System

Real-Time Status Indicators

The header status badge provides instant feedback on your working tree state:

Clean Working Tree
Modified State
Conflict State
Syncing State
Locked State

Green Badge: “Clean”

No pending changes, synchronized with remote
Version display shows current committed version
All changes committed and pushed to remote
Ready for new modifications or production deployment
Collaboration indicators show any active team members

Quick action buttons seamlessly integrated into the editor header provide professional Git-style workflow control:

Check Button (🔍)

Keyboard Shortcut: ⌘UManually check for remote updates and potential conflicts. Useful when auto-sync is disabled or when you want to verify remote state before making changes.

Pull Button (⬇️)

Keyboard Shortcut: ⌘⇧PFetch and merge latest changes from remote repository. Automatically resolves non-conflicting changes and flags conflicts for manual resolution.

Commit Button (✓)

Keyboard Shortcut: ⌘EnterSave current changes with descriptive commit message. Opens professional commit interface with AI-powered message generation and production deployment options.

Push to Production (⬆️)

Keyboard Shortcut: ⌘⇧EnterDeploy committed version directly to production environment. Available after successful commit with immediate live deployment.

Advanced Change Tracking

Granular Change Detection

The system provides comprehensive change tracking at multiple levels:

Field-Level Precision
Section-Based Organization
Real-Time Diffing
Intelligent Conflict Detection

Individual property tracking: Every configuration field monitored for modifications
Type-aware comparison: Intelligent comparison based on data types
Nested object support: Deep tracking of complex configuration structures
Array change detection: Additions, removals, and reordering in lists

Enhanced Change Categories

Different types of changes have varying impact on agent behavior. System prompt modifications directly affect conversation flow, while basic settings changes may only impact metadata. Always test changes thoroughly in Playground before production deployment.

Core Configuration
Input/Output Parameters
Actions and Tools
Metadata and Settings

High Impact Changes

System Prompt: Primary behavioral instructions and conversation logic
Voice Model: Speech synthesis and voice characteristics
Response Settings: Timing, interruption handling, and conversation flow
Language Configuration: Primary language and accent settings

Professional Commit Workflow

Smart Commit Interface

The commit process follows professional Git workflows with enhanced AI assistance:

Comprehensive Change Review

Access the Changes tab to review all pending modifications with expandable diff views, impact assessment, and change categorization for thorough inspection.

Selective Change Staging

Use checkboxes to stage specific changes for commit, enabling granular control over what gets included in each version for logical change grouping.

AI-Powered Commit Messages

Click ”✨ Generate” to create intelligent commit messages based on actual changes made, with context-aware suggestions and best practice formatting.

Production Deployment Toggle

Enable “Deploy to Production” to automatically make changes live after successful commit, with safety confirmations and rollback preparation.

Commit Validation and Confirmation

Final review dialog shows complete change summary, deployment impact, and confirmation options before creating the new version in timeline.

Intelligent Commit Message Generation

AI-Generated Messages
Best Practice Guidelines
Common Mistakes to Avoid

Context-Aware Generation

Change Analysis: AI analyzes actual fields and content modifications
Impact Assessment: Identifies behavioral changes and their significance
Action-Oriented Language: Uses clear, descriptive verbs and technical accuracy
Scope Indication: Includes specific components and areas affected

Example Generated Messages:

✅ Update system prompt to improve customer service tone
✅ Add weather lookup capability with OpenWeather integration  
✅ Fix webhook timeout configuration for order processing
✅ Remove deprecated email notification from end call workflow
✅ Optimize response timing for better conversation flow

Professional Commit Message Format

Type: Brief description of what changed

Optional longer explanation of why the change was made,
what business need it addresses, and any relevant context
for future developers.

- Key changes or impacts
- Testing performed
- Related tickets or requirements

Recommended Types:

feat: New feature or capability
fix: Bug fix or correction
update: Modification of existing functionality
config: Configuration or settings change
docs: Documentation updates only

Ineffective Commit Messages

❌ "Fixed stuff"
❌ "Updates"
❌ "Changed things around"
❌ "WIP - work in progress"
❌ "Minor tweaks"
❌ "Commit before deadline"
❌ "Testing"
❌ "Temporary changes"

Why These Are Problematic:

No indication of what actually changed
Impossible to understand impact without reviewing diffs
Makes debugging and rollback decisions difficult
Provides no context for team collaboration

Comprehensive Version Timeline

Professional History Interface

The History timeline provides complete chronological tracking of all agent versions:

Timeline Navigation

Browse through complete version history with intuitive chronological layout, visual hierarchy, and comprehensive filtering options.

Rich Version Metadata

Each version displays commit message, timestamp, author information, production status, change summary, and performance metrics.

Quick Action Buttons

Instant access to Restore Version, Deploy to Production, View Detailed Changes, Compare with Current, and Create Feature Branch.

Detailed Version Inspection

Click any version for expanded view with complete diff visualization, metadata analysis, and deployment history.

Enhanced Version Cards

Each version in the timeline provides comprehensive information for effective version management:

Element	Information	Visual Features
Version Number	Sequential versioning (v1, v2, v3…)	Prominent version tag with status indicators
Commit Message	Developer-provided change description	Primary text with intelligent truncation and expansion
Timestamp	Creation time with relative display	Human-readable relative time (e.g., “2 hours ago”)
Author Information	User details with role and permissions	Avatar, name, role badge, and contact information
Production Status	Current deployment and live status	Prominent “LIVE” badge for active production versions
Change Summary	Quantified modification statistics	Colored badges showing adds/modifications/deletions
Performance Metrics	Success rates and call statistics	Real-time performance data for deployed versions
Branch Information	Source branch and merge details	Branch indicators and merge commit relationships

Production Deployment Management

Safe Production Workflow

Only the version marked as “Production” handles live customer calls. All other versions remain in development state. Exercise extreme caution when deploying to production, as changes immediately affect customer interactions and business operations.

Pre-Deployment Validation

Thoroughly test changes using Playground, run automated regression tests, validate with stakeholders, and ensure rollback plan is ready.

Target Version Selection

Navigate the History timeline to identify the specific version for production deployment, review change summary and impact assessment.

Change Impact Review

Use “View Changes” to examine detailed modifications, assess business impact, verify compliance requirements, and confirm testing completion.

Production Deployment

Click “Mark as Production” to designate version for live traffic, review deployment confirmation dialog showing affected systems.

Deployment Confirmation

Final confirmation dialog shows complete impact analysis, affected call volumes, and emergency rollback procedures before deployment.

Post-Deployment Monitoring

Monitor live call performance metrics, success rates, error patterns, and be prepared for immediate emergency rollback if issues arise.

Production Status Management

Live Production Indicators
Deployment History Tracking
Multi-Environment Support

Prominent “LIVE” badge: Clearly identifies currently deployed version
Crown icon: Visual hierarchy indicator for production status
Green border highlighting: Makes production version stand out in timeline
Real-time metrics: Live performance statistics and call success rates
Traffic routing status: Confirmation of active call routing to this version

Real-Time Collaboration Features

Advanced Collaboration System

Professional team collaboration with conflict prevention and resolution:

Live User Presence

Real-time display of all team members currently editing the agent, with activity status and current focus areas for coordination.

Intelligent Conflict Prevention

Automatic locking system prevents simultaneous edits to the same configuration sections, with clear lock indicators and timeout management.

Continuous Auto-Sync

Background synchronization every 30 seconds checks for remote changes, with smart merging of non-conflicting modifications automatically.

Guided Conflict Resolution

When conflicts occur, visual diff interface provides step-by-step resolution workflow with merge options and preview capabilities.

Collaboration State Management

Active Collaboration Indicators
Conflict Resolution Interface
Auto-Sync Intelligence

User avatars: Live display of currently active editors with status
Section-level locks: Visual indicators when specific areas are being edited
Real-time sync status: Header badge showing current collaboration state
Change notifications: Instant alerts when remote changes are detected
Activity timeline: Recent collaborative activities and contributions

Pull and Sync Operations

Automatic Sync Monitoring

System continuously monitors remote repository for changes, with configurable polling intervals and immediate notification of conflicts.

Manual Check Operation

Use “Check” button (⌘U) to manually verify remote change status, bypass automatic sync, and get immediate status update.

Pull Remote Changes

Use “Pull” button (⌘⇧P) to fetch and integrate all remote changes, with automatic conflict detection and resolution guidance.

Conflict Resolution Workflow

When conflicts are detected, guided interface helps resolve each conflict with visual diff tools and merge options.

Sync Completion Verification

Status automatically updates to “Clean” when local and remote states are fully synchronized and all conflicts resolved.

Advanced Workflow Patterns

Emergency Production Hotfix

Critical Issue Identification

Rapidly identify urgent production issue requiring immediate configuration change through monitoring alerts or customer reports.

Targeted Quick Fix

Make precise, minimal changes to only the specific configuration elements needed to resolve the critical issue.

Rapid Validation Testing

Use Playground for immediate verification that the fix resolves the issue without introducing unintended side effects.

Emergency Commit and Deploy

Use “Deploy to Production” toggle during commit to push changes live immediately, bypassing normal review cycles.

Live Monitoring and Verification

Monitor call analytics and performance metrics in real-time to confirm successful resolution of the production issue.

Post-Incident Documentation

Update commit messages with detailed incident context for future reference and create post-mortem documentation.

Feature Development with Branching

Feature Branch Creation

Create new development branch from stable main branch for isolated feature development without affecting production.

Iterative Development Process

Make incremental changes with frequent commits, descriptive messages, and regular testing to maintain development momentum.

Comprehensive Testing Protocol

Use Playground extensively, run automated regression tests, and validate in staging environments before merge consideration.

Team Code Review Process

Collaborative review of changes using integrated diff views, comment system, and approval workflows before integration.

Main Branch Integration

Merge completed and fully tested feature back to main development branch with conflict resolution as needed.

Production Deployment Strategy

Deploy merged version to production with comprehensive monitoring, gradual rollout, and prepared rollback procedures.

Emergency Rollback Procedures

Issue Detection and Assessment

Quickly identify production issues through automated monitoring, customer reports, or team observations with severity assessment.

Impact Analysis and Decision

Evaluate issue severity, customer impact, and business consequences to determine if immediate rollback is necessary.

Last Known Good Version

Use History timeline to quickly identify the most recent stable production version with confirmed good performance.

Emergency Version Restore

Use “Restore This Version” to immediately revert configuration to last stable state, bypassing normal review processes.

Immediate Production Deployment

Mark restored version as Production to stop customer impact immediately and restore service to known good state.

Post-Rollback Analysis

After stability is restored, analyze the problematic version to understand root cause and prevent future occurrences.

Comprehensive Keyboard Shortcuts

Primary Version Control Actions

Action	Windows/Linux	macOS	Description
Open Changes Panel	`Ctrl+G`	`⌘G`	Switch to Changes tab for reviewing pending modifications
Check for Updates	`Ctrl+U`	`⌘U`	Manually check remote repository for new changes and conflicts
Pull Remote Changes	`Ctrl+Shift+P`	`⌘⇧P`	Fetch and merge latest changes from remote repository
Open Commit Dialog	`Ctrl+Enter`	`⌘Enter`	Open professional commit interface for current changes
Deploy to Production	`Ctrl+Shift+Enter`	`⌘⇧Enter`	Push committed version directly to production environment
Generate Commit Message	`Ctrl+Shift+G`	`⌘⇧G`	AI-generate descriptive commit message based on changes

Action	Windows/Linux	macOS	Description
View History Timeline	`Ctrl+H`	`⌘H`	Switch to History view for complete version timeline
Quick Rollback	`Ctrl+Shift+R`	`⌘⇧R`	Quick access to emergency rollback to last production version
Compare Versions	`Ctrl+D`	`⌘D`	Open side-by-side comparison between current and selected version
Search Version History	`Ctrl+F`	`⌘F`	Search version history by commit message, author, or date

Change Review and Editing

Action	Windows/Linux	macOS	Description
Expand All Changes	`Ctrl+Shift+E`	`⌘⇧E`	Expand all change sections for comprehensive review
Collapse All Changes	`Ctrl+Shift+C`	`⌘⇧C`	Collapse all sections for overview and navigation
Next Change	`Ctrl+Down`	`⌘↓`	Navigate to next changed configuration section
Previous Change	`Ctrl+Up`	`⌘↑`	Navigate to previous changed configuration section
Toggle Diff View	`Alt+D`	`⌥D`	Switch between inline and side-by-side diff views

Production Best Practices

Frequent Commits with Clear Messages

Atomic Commits StrategyCreate commits after each logical change rather than bundling multiple unrelated modifications. This creates more granular restore points and makes the timeline easier to navigate for debugging and collaboration.

One feature or fix per commit
Clear, descriptive commit messages explaining what and why
Include business context and requirements references
Test each commit individually before pushing

Comprehensive Testing Before Deployment

Multi-Layer Testing ApproachAlways validate changes thoroughly before production deployment to minimize customer impact and business disruption.

Use Playground for conversation flow testing
Run automated regression test suites
Validate in staging environments that mirror production
Perform load testing for performance-critical changes
Get stakeholder approval for behavioral changes

Strategic Branching for Complex Work

Branch Management StrategyUse feature branches effectively to isolate development work and enable parallel development without conflicts.

Create feature branches for major changes or experiments
Keep main branch stable and deploy-ready
Use descriptive branch names reflecting the work
Merge branches only after thorough testing and review
Delete branches after successful merge to avoid clutter

Proactive Production Monitoring

Continuous Production OversightMonitor agent performance continuously after deployments to catch issues early and ensure optimal performance.

Set up automated alerts for performance degradation
Monitor key metrics: success rate, response time, error patterns
Establish baseline metrics before major changes
Prepare rollback procedures before each deployment
Document monitoring procedures for team consistency

Collaborative Conflict Prevention

Team Coordination Best PracticesPrevent conflicts through communication and coordinated development practices.

Communicate major changes before starting work
Use the collaboration lock system effectively
Resolve conflicts promptly when they occur
Maintain awareness of team member activities
Establish team conventions for commit messages and workflows

Comprehensive Documentation

Change Documentation StandardsDocument not just what changed, but why changes were made and their expected impact.

Include business context in commit messages
Reference tickets, issues, or requirements driving changes
Document testing performed and results achieved
Note any special deployment considerations or risks
Maintain changelog for major feature releases

Troubleshooting and Recovery

Common Scenarios and Solutions

Resolving Merge Conflicts

Step-by-Step Conflict ResolutionWhen conflicts appear, the system provides a guided resolution process:

Identify Conflicts: Changes tab highlights conflicting fields in red
Review Changes: Use diff interface to understand both local and remote changes
Choose Resolution: Select local changes, remote changes, or create custom merge
Preview Results: Review the merged result before committing
Complete Resolution: Commit the resolved changes to complete the merge

Each conflict must be resolved individually for complete merge completion.

Recovering Lost Changes

Change Recovery ProcessAll changes are preserved in version history - nothing is permanently lost:

Check History Timeline: Review recent commits for your changes
Search by Author: Filter history by your username
Search by Message: Use commit message search to locate changes
Check Uncommitted Changes: Look in Changes tab for unsaved work
Branch Investigation: Changes might be in feature branches

If changes still seem missing, contact support with specific details about when changes were made.

Emergency Production Response

Critical Issue Response ProtocolFor production emergencies requiring immediate action:

Assess Impact: Determine severity and customer impact scope
Emergency Rollback: Use quick rollback to last known good version
Verify Resolution: Confirm issue is resolved with rollback
Communicate Status: Update stakeholders on resolution
Investigate Root Cause: Analyze problematic version after stability restored
Implement Preventive Measures: Update processes to prevent recurrence

Document all emergency actions for post-incident analysis.

Synchronization Issues

Sync Problem ResolutionWhen auto-sync shows persistent errors or fails to complete:

Manual Sync: Use Check and Pull buttons to force synchronization
Clear Browser Cache: Refresh authentication and cached data
Network Verification: Check internet connectivity and firewall settings
Authentication Check: Verify login status and permissions
Browser Refresh: Complete page reload to reset sync state

If problems persist after these steps, contact technical support with error details.

Collaboration Lock Resolution

Resolving Edit Lock IssuesWhen locked out due to collaborative editing conflicts:

Wait for Timeout: Locks automatically release after 30 minutes of inactivity
Contact Active User: Reach out directly to the user holding the lock
Save Work Locally: Preserve your changes to prevent loss during resolution
Admin Override: System administrators can manually release stuck locks
Alternative Approach: Use feature branches to work around active locks

Document recurring lock issues to improve team coordination processes.

Performance and Deployment Issues

Deployment Problem ResponseWhen deployed changes cause performance problems or unexpected behavior:

Immediate Assessment: Check call analytics for impact measurement
Traffic Analysis: Monitor call volume, success rates, and error patterns
Gradual Rollout: If available, limit exposure using A/B testing
Performance Baselines: Compare against pre-deployment metrics
Emergency Rollback: If severe issues, immediately revert to stable version
Issue Documentation: Record problems for future deployment planning

Always establish performance baselines before significant changes.

Integration with Advanced Editor

Seamless Cross-Feature Integration

Version History is deeply integrated with all Advanced Editor features for unified workflow:

Monaco Editor Integration
AI Copilot Integration
Playground Integration
Testing Suite Integration

Real-time change detection: Every keystroke and modification tracked automatically
Syntax-aware diffing: Intelligent comparison considering code structure
Auto-save with version tracking: Continuous preservation without committing
Conflict highlighting: Visual indicators directly in editor for conflicts

Workflow Automation

Change Detection Pipeline

Monaco Editor modifications automatically flow into version tracking with real-time diff generation and change categorization.

AI-Enhanced Commits

Copilot analyzes pending changes to generate contextual commit messages and impact assessments for informed decisions.

Testing Integration

Playground test results and automated test suite outcomes are incorporated into deployment decision workflows.

Production Pipeline

Successful commits can trigger automated deployment pipelines with safety checks and monitoring integration.

Next Steps

Test Changes in Playground

Validate your modifications with comprehensive conversation testing before committing changes to version history

AI Copilot Assistant

Get intelligent assistance with commit messages, change analysis, and optimization recommendations

Automated Testing Suite

Set up comprehensive regression tests to prevent production issues and ensure quality

Production Call Analytics

Monitor real-time performance metrics and success rates after deploying configuration changes

Getting Started

Agents

Advanced Editor

Voice Library

Calls

CRM

Account

​What is Version History?

​Accessing Version History

​Git Status in Header Bar

​Changes Panel

​Git-Style Status System

​Real-Time Status Indicators

​Integrated Control Toolbar

​Advanced Change Tracking

​Granular Change Detection

​Enhanced Change Categories

​Professional Commit Workflow

​Smart Commit Interface

​Intelligent Commit Message Generation

​Comprehensive Version Timeline

​Professional History Interface

​Enhanced Version Cards

​Production Deployment Management

​Safe Production Workflow

​Production Status Management

​Real-Time Collaboration Features

​Advanced Collaboration System

​Collaboration State Management

​Pull and Sync Operations

​Advanced Workflow Patterns

​Emergency Production Hotfix

​Feature Development with Branching

​Emergency Rollback Procedures

​Comprehensive Keyboard Shortcuts

​Primary Version Control Actions

​History and Navigation

​Change Review and Editing

​Production Best Practices

​Troubleshooting and Recovery

​Common Scenarios and Solutions

​Integration with Advanced Editor

​Seamless Cross-Feature Integration

​Workflow Automation

​Next Steps

Test Changes in Playground

AI Copilot Assistant

Automated Testing Suite

Production Call Analytics

What is Version History?

Accessing Version History

Git Status in Header Bar

Changes Panel

Git-Style Status System

Real-Time Status Indicators

Integrated Control Toolbar

Advanced Change Tracking

Granular Change Detection

Enhanced Change Categories

Professional Commit Workflow

Smart Commit Interface

Intelligent Commit Message Generation

Comprehensive Version Timeline

Professional History Interface

Enhanced Version Cards

Production Deployment Management

Safe Production Workflow

Production Status Management

Real-Time Collaboration Features

Advanced Collaboration System

Collaboration State Management

Pull and Sync Operations

Advanced Workflow Patterns

Emergency Production Hotfix

Feature Development with Branching

Emergency Rollback Procedures

Comprehensive Keyboard Shortcuts

Primary Version Control Actions

History and Navigation

Change Review and Editing

Production Best Practices

Troubleshooting and Recovery

Common Scenarios and Solutions

Integration with Advanced Editor

Seamless Cross-Feature Integration

Workflow Automation

Next Steps