Copy or Duplicate an Agent
The dashboard doesn't have a one-click duplicate button — but Advanced mode's Copy JSON makes it a quick job.
Steps
1. Open the source agent
Go to Your AI Agents → click View more → Edit (pencil icon) on the agent you want to copy.
2. Switch to Advanced mode
Click the code icon button in the top-right of the editor header (the right button in the icon pair). This switches to the JSON editor.
3. Copy the JSON
Click Copy JSON in the toolbar above the editor. The full agent configuration is now on your clipboard.
4. Create a new agent
Go back to Your AI Agents → click the + icon button (top-right) → Create from Scratch.
5. Switch to Advanced mode on the new agent
Click the code icon button again to switch to Advanced mode. The editor pre-fills with a default stub:
{
"name": "",
"textModelId": "global.amazon.nova-2-lite-v1:0"
}
6. Paste the copied JSON
Select all in the editor (⌘/Ctrl+A) and paste the copied JSON. This replaces the default stub entirely.
7. Change the name
Update the "name" field in the JSON. Two agents with the same name are confusing for end users.
8. Save
Click Create Agent.
The new agent inherits everything: model, system prompt, tool declarations, and any KB override settings.
What does NOT carry over
| Not transferred | Why |
|---|---|
| Knowledge Base content | KBs are tied to the source agent. The new agent's KB starts empty — you must re-upload content. |
| OAuth tokens for tools | Per-user tokens are not transferable. Re-authorize on the Tool Configuration page for the new agent. |
| Usage history | Analytics start fresh for the new agent. |
Templates vs. copying
The dashboard ships with a catalog of agent templates. Templates are read-only — you can't save your own from the UI today. For creating variations of your own agents, copying via Advanced JSON is the recommended approach.
Tips
- Select all before pasting. Always use ⌘/Ctrl+A to replace the entire pre-filled JSON — partial pastes produce invalid JSON.
- Version-control the JSON. Paste it into your repo. When something breaks, roll back by pasting the old JSON.
- Don't copy secrets. OAuth Client IDs and other auth details in the tool list travel with the copy. Re-issue credentials if the new agent is for a different audience or environment.
- Re-upload KB content. After copying, the new agent's KB is empty. Treat it as a fresh KB and add the documents again.