Publishing and updates
Publish a new version of your agent, write what changed, and see what Users of the old version get.
After you publish an agent to the Agent Store, you can keep improving the workflow and publish updates. Each update gets a new version number and a short note on what changed, shown to Users in the store. Users move to the new version when they choose to.
Publish an update
A published workflow is read-only, so you unpublish it, change it, and publish again.
- In the canvas's top bar, open the listing button (for example Live on Store) and choose Unpublish to edit, then Unpublish. The agent leaves the store until you publish again; Users who already have it keep using their conversations. Unpublishing also removes the memory that shipped with the agent: Users' existing conversations lose the FROM plus your name items. Your next publish ships a new set with the new version.
- Change the workflow and test it.
- Click Publish, then Publish Agent in the dialog.
- Open the listing button again and choose Publish to Agent Store. The Update Store Listing dialog opens with your earlier listing filled in; change what you need.
- Click Update Listing. The Version Update Required dialog opens.
- Under Nature of Changes, choose:
- Patch Version: bug fixes and small corrections.
- Minor Version: new features that don't change how the agent is used.
- Major Version: changes that work differently from before, such as removed features or changed inputs.
- Under What changed?, write a short note for Users, for example "Improved the summary and fixed empty inputs". It is required.
- Check the New Version number and click Continue with plus that number.
A version number can't be reused: each update must move to a new one. A paid agent's update goes through review before Users get it; a free agent's update is listed right away.
Where Users see your notes
Your note appears under Version History on the agent's page in the store, next to the version number and the kind of change.
What Users get after an update
- Conversations in My Agents: each conversation a User started stays on the version it started with. Once your update is live in the store, the conversation says that a newer version is out and offers Start new conversation. New conversations run the latest version.
- Price changes: if you raised the price, a User who bought an earlier version pays only the difference to start a conversation on the new version. Their existing conversations keep working.
- Agent flows in other workflows: an agent flow added as Copy stays as it was; one added as Reference (only possible with your own agents) follows your updates. See Agent flows.
Limits
- What changed? note: up to 2,000 characters.
Common problems
Continue with is greyed out
The What changed? note is empty. Write a short note for Users.
Users still see the old version
A paid agent's update waits for review before it goes live. After that, each User gets it when they start a new conversation; existing conversations stay on their version.
The listing went back to Pending review
Updates to paid agents are reviewed like the first listing. The top bar shows Pending review until the update is approved. Users who already have the agent keep using their conversations meanwhile. While it is in review, the agent isn't shown in the store and can't be installed.