---
sourceDocument: Zurich Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/intelligent-experiences

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Version control

# Version control for AI agents and agentic workflows {#ariaid-title1}

Release version: Zurich  
Updated July 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Version control enables you to track changes made to instructions sent to the LLM for AI agents and agentic workflows.

## Version control overview

When creating an AI agent or agentic workflow, the List of steps field is important because it provides the context necessary for the large language model (LLM) to accomplish tasks. You can use version control to
create multiple versions of the List of steps field in the guided setup. Tracking your changes with version control helps enable you to experiment and test new instructions. You can create versions, edit and refine
versions, and revert to previous versions as needed.  
Figure 1. Version control modal

## Creating versions

You can create a version by selecting View versionsNew version in the guided setup of an AI agent or agentic workflow. Doing so brings up the Create a new version modal where you can name the version and make changes. Naming your version enables you to identify
what changes were made to make it easier to track.

You can choose to make the new version active immediately by selecting the Set as active toggle.

For more information about writing effective descriptions and instructions, see [General guidelines for creating AI agents and agentic workflows](https://www.servicenow.com/docs/~MlCy7RCcV46CgQnJ0PsGw "By following some general guidelines for creating AI agents and agentic workflows, you can create clear and effective instructions that help maximize their efficiency and effectiveness.").

When creating a new version, you also have the option to use ServiceNow Otto to refine your current List of steps. You must already have an active version for this option to be available. Selecting View versionsRefine version brings up the modal where ServiceNow Otto generates and displays a new List of steps for you to review. You can change any of the generated text, or you can use it as it was generated. Select Create to use the new, refined version.  
Figure 2. Create a version modal

## Changing between versions

When you have multiple versions of the same List of steps field, you can switch which one is active at any time. Choosing to make a new version active enables you to test it and evaluate its effectiveness.

If you're updating an agentic workflow, you can [execute an agentic evaluation run](https://www.servicenow.com/docs/3HpdefgYzICpE1J1NMccsw "Evaluate agentic AI assets against datasets to monitor performance and compare benchmarks.") to measure performance.

You can decide which version is active by selecting View versions in the guided setup. Toggle the Set as active field and save your changes to make the new version active.

## Testing different versions

You can test different versions of an agentic workflow or AI agent from the AI Agent Studio
Testing page. The Version selector dropdown displays both active and inactive versions with the currently active version marked as (Active). You can also start evaluation runs for specific versions by selecting Set up evaluation run.  
Figure 3. Version selector in the AI Agent Studio Testing page

## Version logs

The AI Agent Studio
Activity page enables you to track AI agent and agentic workflow executions by version. When in the guided setup, you can select View version logs in the View all versions modal. Choosing to view the version logs opens the Activity tab in a new window with the list filtered for the version you selected.

When viewing the Activity tab at any time, you can choose to filter by version. The more specific your version names, the easier it is to identify those changes in the list.  
Figure 4. Example execution logs

*[\>]: and then