Introduction
Duvo maintains revisions 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 Revisions Work
Revisions are explicit: choosing New revision in the builder’s revision selector creates a draft copy of the revision you branched from, and clicking Make active promotes it to live. Ordinary edits save to whichever revision you have selected — including the live one — so fork a draft before changing an agent that is already in production. This means:- Your previous configuration is preserved every time you activate a new revision
- You can see how the agent has changed
- Recent changes can be reviewed and understood
Why Revisions Matter
Safe Iteration
Revisions let you improve agents with confidence:- Make changes without fear of losing working configurations
- Test modifications knowing you can reference previous revisions
- Iterate quickly without extensive documentation
Change Tracking
Understand how agents have evolved:- See what changed between revisions
- Track who made modifications
- Understand the history of an agent
Troubleshooting
When something stops working:- Compare current revision to previous working revisions
- Identify what changed
- Understand what might have caused issues
Working with Revisions
Viewing Revision History
To see an agent’s revision history:1
Open the agent
Open the agent.
2
Open the revision selector
Click the revision selector in the builder toolbar.
3
Select a revision
Review the list of saved revisions and select one to view.
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: 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 again, open it in the revision selector and click Make active — it becomes the live revision directly, keeping its original number
Understanding Changes
Each revision 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 revision history.Test Before Major Changes
Before significantly modifying a working agent:1
Verify the current revision
Verify the current revision is working.
2
Make your changes
Make your changes.
3
Test thoroughly
Test thoroughly before relying on the new revision.
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?
Revision 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
- A new revision is created when you choose New revision in the revision selector (or when the AI builder stages changes as a draft) — ordinary edits save to the revision you have selected
- 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
- Revision history helps you understand agent evolution
- Major changes should be tested before deployment