Version Control for Agent Studio

Even a way to export the raw data then deploy the change would help in this regard. Version control in it’s entirety however would be very beneficial

Hi ​@andrewwhitley -- thank you for sharing this feedback! I understand how version control would make the life cycle of plugin development and iteration much easier. It is something we will take into consideration as we improve our Plugin Workspace experience. Please let us know if you have more feedback as well. 

​@mitchell.wood We recently released Plugin Promotion into Limited Preview. While not ideal, one option would be to “export” a version of your plugin into the same instance (maybe name it _v1), and then make any edits. 

Avoiding renames and copies of copies of copies is the greatest argument FOR having a version control mechanism.

Like ​@andrewwhitley and ​@spencerneveux  I would greatly appreciate seeing version control in agent studio for ALL asset objects.   Plugins, Conversational Processes, Actions, etc.   

For each of these, I’d see value in being able to make minor changes - especially across large conversations - and not have to remember each minor change if I wanted to “roll back”.  

The ability to export/import yaml markdown or similar to build the objects would suffice, and users could version control themselves via Git or other tool. 

This is currently on the near-term roadmap (LP date still TBD). V1 will be more of an “undo / revert” button than a full-fledged versioning experience.

What is it?

• Revert to a prior version of an Agent Studio asset (plugin, action, etc.) configuration after an unwanted change

Why it matters?

• Reduces risk of onboarding new developers
• Shortens time-to-recovery when an update causes regressions

Key dates:

• Limited Preview: TBD

We are still evaluating this. Some form of version control may materialize alongside our Agent Architect investments.