> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Versions

> Duvo saves a version of an agent each time you change it, so you can iterate safely, track changes, and revert.

## Introduction

Duvo maintains versions of your agents as you make changes. This allows you to iterate safely, test modifications, and understand how your agents have evolved over time.

***

## How Versioning Works

Every time you make significant changes to an agent and save, Duvo creates a new version. This means:

* Your previous configuration is preserved
* You can see how the agent has changed
* Recent changes can be reviewed and understood

```mermaid theme={"dark"}
stateDiagram-v2
    [*] --> Live: Save first version
    Live --> NewRevision: Make changes and save
    NewRevision --> Live: New revision becomes live
    Live --> ViewingOlder: Open an older revision
    ViewingOlder --> NewRevision: Create a new revision based on it
    ViewingOlder --> Live: Return to the live revision
```

***

## Why Versions Matter

### Safe Iteration

Versioning lets you improve agents with confidence:

* Make changes without fear of losing working configurations
* Test modifications knowing you can reference previous versions
* Iterate quickly without extensive documentation

### Change Tracking

Understand how agents have evolved:

* See what changed between versions
* Track who made modifications
* Understand the history of an agent

### Troubleshooting

When something stops working:

* Compare current version to previous working versions
* Identify what changed
* Understand what might have caused issues

***

## Working with Versions

### Viewing Version History

To see an agent's version history:

<Steps>
  <Step title="Open the agent">
    Open the agent.
  </Step>

  <Step title="Open the revision selector">
    Click the revision selector in the builder toolbar.
  </Step>

  <Step title="Select a revision">
    Review the list of saved revisions and select one to view.
  </Step>
</Steps>

### Non-Live Revision Warning

When you open an older revision that is not currently live, a warning banner appears at the top of the builder:

<Warning>
  **You are viewing a non-live revision.** Scheduling and triggers run the latest revision, not this one.
</Warning>

This means:

* Runs started manually while viewing this revision will use its configuration
* Scheduled runs and trigger-based runs always use the **live** revision, regardless of which revision you are currently viewing
* To make an older revision live, create a new revision based on it or use it as a starting point for your next changes

### Understanding Changes

Each version captures:

* AOP and configuration
* Connected connections
* Skills and files attached
* Settings and options

### Building on Previous Work

When creating similar agents:

* Review successful agents for patterns
* Understand what configurations work well
* Apply learnings to new automation

***

## Best Practices

### Make Meaningful Changes

Group related changes together rather than saving after every small edit. This creates cleaner version history.

### Test Before Major Changes

Before significantly modifying a working agent:

<Steps>
  <Step title="Verify the current version">
    Verify the current version is working.
  </Step>

  <Step title="Make your changes">
    Make your changes.
  </Step>

  <Step title="Test thoroughly">
    Test thoroughly before relying on the new version.
  </Step>
</Steps>

### Document Significant Updates

When making important changes, consider:

* Updating the agent description
* Noting why changes were made
* Recording expected improvements

### Regular Review

Periodically review your agents:

* Are they still meeting needs?
* Have requirements changed?
* Is the configuration still optimal?

***

## Version Management Tips

### Keeping Agents Current

* Review agents when connected systems change
* Update when business processes evolve
* Refresh when better approaches become available

### Managing Multiple Agents

For teams with many agents:

* Use consistent naming conventions
* Group related agents logically
* Document dependencies between agents

### Coordinating Changes

When multiple people work on agents:

* Communicate about planned changes
* Avoid simultaneous modifications
* Review changes made by others

***

## Things to Know

* Revisions are created automatically when you save changes
* Scheduling and triggers always run the **live** revision, even if you are currently viewing an older one
* A warning banner appears whenever you open a non-live revision so you always know which revision you are looking at
* Version history helps you understand agent evolution
* Major changes should be tested before deployment