Refine an agent
Building an agent is rarely a one-shot process. After testing it in chat, you'll often find things to improve — a sub-agent that needs sharper instructions, a skill that's missing, a scope that's too broad. The Meta-Agent can help with this too: describe what you want to change, and it proposes a revised configuration that you apply as a new version of the same agent.
Continuing a build conversation
If you just created an agent through the Meta-Agent, you're already in the right place — the build conversation is still open. Tell the Meta-Agent what you'd like to change:
"The triage sub-agent is catching too many questions it can't answer. Can we give it clearer boundaries?"
"Add a sub-agent for handling refund requests."
"The system prompt for the billing specialist feels too formal — make it more conversational."
The Meta-Agent revises the spec based on your feedback. A new artifact pill appears in the conversation — click it to review the updated version before applying it.
Starting a new refinement session
You can also start fresh from Meta-Agent mode and ask it to work on an existing agent:
- Enter Meta-Agent mode (click Build agent or type
/meta) - Tell the Meta-Agent you want to improve an agent you already have and describe which one
- It asks questions, proposes changes, and emits an updated spec
The Meta-Agent identifies the existing agent by name and links the spec to it. This is what switches the creation flow into version mode.
Version mode
When the spec the Meta-Agent generates is linked to an agent that already exists, the artifact panel enters version mode. You'll see this reflected in the spec summary:
Save as version v3 of Customer Support Agent
Instead of creating a brand-new agent, the Create agent button saves the proposed configuration as a new version draft of the existing agent. The agent's ID, all connections, and any running integrations are completely unchanged.
Version mode has one additional option — a Promote now checkbox:
| Setting | What happens |
|---|---|
| Unchecked (default) | The new configuration is saved as a draft. Live traffic continues using the current active version until you promote it manually in Flows. |
| Checked | The new configuration is saved and immediately promoted. The agent's live behavior updates for all callers the moment creation completes. |
Test before promoting
The default is to save as a draft because it's the safer option — you can test the new version in the Flows Playground before it affects real users. Leave Promote now unchecked unless you're confident in the change and want it live immediately.
After saving a new version
When the version is saved, the confirmation reads:
🎉 Saved version v3 draft of Customer Support Agent
(Or, if you checked Promote now: Promoted version v3 of Customer Support Agent.)
Click Open in chat → to load the agent and test the new version. If the version is a draft, the Playground in Flows will run it without affecting live traffic — the same principle applies in Chat if you're testing manually.
To view all versions, manage the draft, or roll back, open the agent in Flows and go to the Versions panel.