Versions and rolling back
Deploying keeps the old one. Nothing is overwritten.
On this page
Every deploy creates a version: the instructions, the model, the tool selection and the limits as they were at that moment.
Why this matters
An agent that behaved well last week and badly today has usually changed. The version history makes that answerable rather than a matter of memory.
Rolling back
Open the agent, find the version that worked, and roll back to it. That creates a *new* version with the old contents rather than deleting anything, so the history stays honest — you can see that a rollback happened and when.
Editing is not deploying
Saving an agent changes the draft. Runs keep using the deployed version until you deploy again. That is deliberate: it means you can work on an agent in the middle of the day without changing what is answering customers.