Agent Versions: We Save Every Change to Your Agent, So You Can Always Go Back

Changing Your Agent Was Easy. Keeping Track of It Was Not.

On Mihu there are many ways to change your agent. Now every change has a full record, and a way back.

You can change your agent from the dashboard. You can change it through the API, or from the CLI. You can connect Claude, ChatGPT or any other AI client that speaks MCP to your workspace and just tell it what you want. You can ask Mihu Assistant. Simulator Studio tests your agent and proposes fixes. And with Auto-Improvement, the agent reads its own conversations and improves itself.

We built all of that on purpose. Your agent should be easy to change from wherever you happen to be working.

But we also have to be honest about what it created. Before this update, it was not clear what had changed on an agent, where the change came from, when it happened, or who made it. A colleague, a script, an AI assistant and the agent itself could all touch the same agent in the same afternoon, and when it started behaving differently, there was no clean answer to the simple question: what happened? You were left reading the whole configuration and guessing.

What We Did About It

Every change is a version. Every version answers the four questions.

Now, whenever your agent actually changes, we save a version. Not when you press Save, but when something is genuinely different afterwards. Every version records where the change came from and who made it: a team member by name, the API, the CLI, an AI client over MCP, Simulator Studio, Auto-Improvement. And every version can be opened to show exactly what changed, with the old state on the left and the new one on the right, and only the parts that differ. You do not read the whole agent. You read the difference.

What, where, when, who. One list, whatever made the change.

That is really all it is. There is nothing to set up and nothing to remember to do. It is on for every agent in your workspace, on every plan.

Everything Is Included, Not Just the Prompt

A version is the whole agent.

We want to be clear about this, because a lot of tools that say "version history" mean the prompt text and nothing else. That is fine for a prompt box. Mihu is a platform: an agent here is built from many parts, and a version has to cover all of them. So a version is the whole agent: its details, its intents and what they need, its procedures, its guidelines and notes, its training, which documents and tables it answers from, how it sounds on the phone and how it writes, when it hands over to a person and to whom, and the integrations it is connected to. Everything from your integrations to your knowledge base.

We did it this way because problems rarely sit in one place. A change that made the agent worse might have touched a rule, a required field and a phone number at once. When you go back, all of it goes back together. Otherwise it is not really going back.

Going Back

One click, and nothing is ever deleted.

Any version has a Restore button. Press it, confirm, and the agent is exactly what it was at that moment. Restoring adds a new entry to the history rather than rewriting it, so you can always see that a restore happened, who did it, and you can move forward again if going back turns out to be the wrong call. Nothing you or anyone else did is ever lost.

We also check a few things so a restore cannot surprise you. If somebody saved a newer version while you were looking at the page, we ask you to refresh and see it first. If a version was saved while documents were still being imported, we ask you to pick a complete one. And if the version you restore reads from documents that need preparing again, that happens in the background while the agent keeps working.

Name the Versions You Trust

So the one you want is easy to find later.

Any version can be given a name. Approved by legal. Working well. Before the new pricing. This is the small habit we would suggest: before you or an AI assistant makes a big change, name the version you have. It takes a few seconds, and it means that whatever happens next, the way back is obvious.

For teams that deploy agents from scripts, the same thing works from the API and the CLI: list versions, name one, restore one. Details are in the developer documentation.

That is Agent Versions. Change your agent from wherever you like, as boldly as you like. We keep the record, and we keep the way back.

A Note on Credentials

Connections are referenced, not copied.

The accounts you connect under Apps, with their passwords, tokens and API keys, are not copied into versions. A version only points to the connection it used. If a connection was removed after a version was saved, that version cannot be restored until the connection exists again; we tell you, and nothing is changed until it does. Secrets that live on the agent itself are stored encrypted, are never shown in the version view or through the API, and come back with the rest of the agent when you restore.

Frequently Asked Questions