Mindset AI

Docs / Managing what's live

Change something that's already live

For editing an agent that colleagues are using, without breaking their week.

What this is

The invoice agent has been running for a month. Finance now wants supplier queries to include the contract clause in the text. That is a change to something people depend on, so the questions are: what happens the moment you save, who is affected and when, and how do you get back if it goes wrong.

What keeps a history and what does not

Thing Keeps versions? How you undo a change
The agent itself: its prompt fields, model, reply language, name, script, resources and schedules Yes Activate an earlier version on the agent's Versions & Availability tab
Functions Yes Re-activate an earlier version on the function's own Versions tab
Widgets Yes Re-activate an earlier version on the widget's own Versions tab
Scripts No. A script belongs to one agent and is saved as part of that agent's versions Activate an earlier version of the agent
Connections No An operation is enabled or it is not. Change it and it is changed

Two of those rows are the ones people get wrong.

  • The agent is versioned. Going back is one action: you activate an earlier version, and the agent returns to how it behaved then. See Agent versions for how saving and activating work.
  • Connections have no history at all. Revoking an operation takes effect immediately for everything using it, including a conversation already under way. That is what makes it the emergency lever, and it is also why there is no undo beyond enabling it again.

Rollback

To roll an agent back, activate an earlier version on its Versions & Availability tab. For a function or widget, go to its own Versions tab and re-activate an earlier one.

Going back puts back everything recorded on the agent itself. It does not put back earlier versions of the functions and widgets it uses, because an agent version records which ones it uses, not which version of each. The agent uses whatever version of each is published now.

What happens when you change each thing

What you change When it takes effect Who is affected, and when
System prompt When you activate the version you saved it in Everyone, from their next message
Agent settings When you activate the version you saved it in Everyone, from their next message
Script Saved as part of the agent's version. Live when you activate that version Everyone, from their next message
The agent's resources Saved as part of the agent's version. Live when you activate that version Everyone, from their next message
A function Save changes creates a version, then publish Every agent that calls it, on their next call
A widget Save changes creates a version, then publish New conversations
Enabling or revoking an operation Immediately Everything, including conversations already running
Connection login details Immediately Everything, including conversations already running

The pattern: anything on the connection is instant and everywhere; anything on the agent reaches people on their next message, once you activate the new version. If you need access stopped this minute, go to the connection.

One more thing about functions. Publishing a new version of the invoice-comparison function changes behavior for every agent that calls it, not only the one you had in mind. Before you publish, check which agents use it in Monitor, then Topology.

Test somewhere that is not live

An environment is a named partition inside your org: Demo, Test, Production. Any member can create one, list them and switch between them. Nobody can rename, archive or delete one. Every org starts with one called original.

Use a second environment for anything you would not want a colleague to meet first:

  1. Switch to Test and make the change there.
  2. Point the finance connection at a sandbox copy if the change touches a write. Operations execute for real during a test run, so a real connection means a real supplier query.
  3. Run it on invoices you know the right answer for.
  4. Make the same change in Production once it holds up.

Changes do not travel between environments on their own. A version belongs to the environment it was saved in. Test is where you find out, not where you build the thing you then ship.

Check the acceptance tests afterward

Every change above is a change to how the agent behaves.

The agent's Acceptance tests tab lists what it has to get right, and whether each test is still passing. The tab is a read-only view: you write, run and retire the tests in Optimize.

  1. Open Optimize and press Run all. This asks the agent every accepted test again, against the agent as it is set up today.
  2. Read the failures first. A change that fixes one thing and breaks another is the normal way this goes wrong.
  3. Amend a test if it no longer describes what you want, or Retire it if the business has moved on.
  4. Add a test for what you just changed, if none covers it.

Scheduled runs are off by default, so these tests run when someone presses Run all.

When it does not work

  • You activated and nothing changed. The most likely cause is that you saved a new version but never activated it. Check the Versions & Availability tab to see which version is active. Otherwise, the people testing it are in conversations that started before you activated.
  • A version will not activate. Mindset refuses a version that depends on a resource switched off or deleted since, that uses a model no longer offered in your region, or that was saved before Mindset recorded the whole agent. The reason is shown on the Versions & Availability tab. Switch a resource back on, or save and activate a new version instead.
  • An acceptance test now fails. Either your change is wrong, or the test describes behavior the business no longer wants, in which case amend or retire it in Optimize with a reason.

You're done when

  • You can say which of your changes were instant and which needed activating.
  • You have activated an earlier version at least once, so you know where it is before you need it in a hurry.
  • The acceptance tests pass, or you know why they do not.
  • The people who use the agent know it changed.