Yesterday's version is one click away
Your agents keep a history now
Every edit to an agent, an app, a skill, or an instruction is now saved as a version, and you can restore any of them.
Open the history on any of the four, and you get the full list, newest first, with who made each change, when, and the note they left. Pick one and revert. The revert is saved as a new version, so nothing is lost on the way back, and you can always undo the undo.
Files come with it. A skill or agent's uploaded files are now kept per version instead of being overwritten on each edit, so restoring an older version brings back the files as they were at the time, not whichever ones happen to be there today.
Reverting needs the same permission as editing. If you can change it, you can restore it.
The Integrations page tells you which storefront
The Integrations page under Settings has been redesigned around the question people kept having to ask us: which storefront is this actually connected to?
Each row now shows how many of its connections are live out of how many exist, and expands to reveal the accounts behind it. Click a row and a panel opens with that integration's connection details and setup instructions. It's also where you connect a new one, so Add data connection is no longer the route for anything already in the list.
Seven more sources joined the catalogue while we were in there: BeX, BigQuery, Databricks, Google Sheets, Salesforce, Sitoo, and Snowflake.
Two Shopify stores, one agent
If you run more than one store, region, or brand on the same platform, you can now connect all of them to a single custom agent instead of building one agent per account.
Add each connection from the agent's Configuration tab, and the agent addresses them separately at runtime, so one agent can pull from your US and EU stores in the same conversation. This works for every integration that supports multiple accounts, including Shopify, Klaviyo, Centra, NetSuite, Snowflake, Storyblok, and any custom MCP server you've added.
Shared apps work for the people you shared them with
Share an app with your team, and it now runs for them, including when the agent behind it stays private to you. They get the app and its data without needing access to the agent that produces it. Previously, the app would only run for people who could also see that agent, so a private agent meant a shared app worked for you alone.
Approvals are unchanged: each tool still resolves against whoever is using the app, so nothing runs without the permission it needs.