How to Clone Agents in Assist 2.0

Overview

Agent Cloning lets you create an exact duplicate of any existing agent in your workspace. Use it to replicate successful agent configurations, experiment with variations, or scale your workflows without rebuilding from scratch.

In Assist 2.0, cloning sits alongside the new marketplace model — so you can clone either a Team agent you've built or a Built-in agent you've installed, then customise the copy to your needs.

What Gets Cloned?

When you clone an agent, the following elements are copied to the new agent:

Custom Instructions: All prompts and instruction sets
Knowledge Connections: Links to any attached workspace knowledge
Tool Configurations: All enabled tools and their settings (subject to your workspace's tool permissions)
Skills: Any custom skills attached to the original agent
Model Settings: Selected AI model and parameters
Response Settings: Temperature and output configuration preferences
Mode Defaults: Whether the agent defaults to Plan Mode or Execute Mode

Note: The clone is a separate, independent agent. Changes to it do not affect the original, and vice versa. In the Clone Agent dialog, use Destination to choose Same Place or another available workspace you have access to. Check that the knowledge, tools and skills the clone needs are available at its destination.

How to Clone an Agent

Follow these steps to clone an existing agent:

Open Library → Agents.
Find the agent and open its three-dot menu (⋮).
Select Clone Agent.
Choose the Destination and enter the Agent Name.
Click Create.
Review the cloned agent and check its knowledge, tools and skills before using it.

Use Cases

Customer Support

Clone your primary support agent to create specialised versions for:

Different product lines
Regional variations with localised knowledge
Tiered support levels (basic, advanced, technical)

Content Creation

Duplicate content agents to create variations for:

Different brand voices or tones
Specific audience segments
Various content types (blog posts, social media, technical documentation)

Development Workflows

Clone coding assistants for:

Different programming languages
Specific frameworks or libraries
Project-specific coding standards

Research & Analysis

Create multiple versions of research agents optimised for:

Different data sources or knowledge bases
Specific analysis methodologies
Various research domains or topics

Best Practices

When to Clone an Agent

Proven performance: Clone agents that have consistently delivered high-quality results
Similar requirements: When you need an agent with similar functionality but slight variations
Testing variations: To experiment with different configurations without affecting your production agent
Scaling operations: When deploying similar agents across multiple teams or projects

Before cloning, it's worth checking whether a near-identical agent already exists in your workspace or the marketplace — Assist 2.0 will surface existing agents when you describe what you need in chat, which can save you from creating duplicates.

Naming Conventions

Use clear, descriptive names for cloned agents:

Include the purpose: "Customer Support — Product A"
Add version indicators: "Content Writer v2 — Formal Tone"
Specify the audience: "Developer Assistant — Python"

Managing Cloned Agents

Document changes: Keep notes on what differentiates each clone from the original
Regular reviews: Periodically assess which cloned agents are actively used
Archive unused clones: Remove or archive clones that are no longer needed to keep your workspace tidy and stay within your agent limit

Comparing Clones to Originals

To evaluate a cloned agent against the original:

Run parallel tests: Use the same prompts on both agents
Compare outputs: Evaluate quality, accuracy, and relevance
Measure performance: Track response times and consistency
Gather feedback: Where possible, collect user feedback on both versions

Limitations

Cloned agents are independent and do not sync with the original
Bulk cloning multiple agents at once is not currently supported
Clones do not include conversation history from the original agent
Workspace agent limits still apply — you'll see your current usage (e.g. 2/10 agents used) in the Agents panel
Tool availability on the clone is limited to the tools your workspace has permission to use, even if the original agent referenced others

Troubleshooting

Clone option not visible

Check you have permission to create agents in your workspace
Check you're not at your workspace's agent limit — if you are, archive an unused agent or contact your account manager
Check that you have access to the source agent and permission to create agents at the intended destination.

Cloned agent missing elements

Verify that all linked knowledge is accessible in your current workspace
Check that any custom skills or tools used by the original are available to you
Confirm you have permissions for all resources used by the original agent

Performance issues after cloning

Review the cloned agent's settings to ensure they match your intended use
Test the agent with a range of prompts to spot any configuration gaps
Consider adjusting model selection or temperature if outputs differ from expectations

Agent Marketplace: Browse and install Built-in agents, or publish Team agents for others in your workspace
Templates: Reusable output templates that work alongside agents
Plan Mode vs Execute Mode: Control whether an agent proposes a plan before acting or executes immediately

Need Help?

If you run into issues with agent cloning or have questions:

Browse our video guides on YouTube
Contact your account manager or support for technical assistance