Skip to content

Cloning an Agent

Create copies of existing agents to quickly build similar agents or create variations.

Overview

Cloning allows you to use an existing agent as a starting point, making it easy to: - Create agent variations for A/B testing - Build similar agents for different use cases - Preserve agent configurations before major changes - Deploy agents across different workspaces

How to Clone an Agent

Step 1: Access Clone Option

  1. Navigate to MY AGENTS
  2. Find the agent you want to clone
  3. Click the menu icon (three dots)
  4. Select Clone

Step 2: Review the Clone Configuration

Review the options presented by the Clone flow before confirming. Do not assume a clone includes conversation history, versions, credentials or every shared resource.

Step 3: Review the Result

Inspect Identity, Brain, tools, Knowledge Bases, channels and appearance on the resulting agent. Verify each dependency in the intended workspace, then test with synthetic questions before enabling user access. See Basic Configuration for the current editor.

Use Cases

A/B Testing

Clone an agent to test different instruction sets or models while keeping the original intact.

Example: - Original Agent: "Customer Support v1" - Clone: "Customer Support v2 (GPT-4)" - Test both versions and compare performance

Multi-Language Agents

Clone an agent and modify instructions for different languages.

Example: - Original: "English Support Agent" - Clone: "Spanish Support Agent" (translated instructions)

Workspace Migration

Clone agents when moving to a new workspace or creating separate production/staging environments.

Template Creation

Clone well-configured agents to use as templates for new projects.

Post-Clone Actions

After cloning:

  1. Update Agent Name: Ensure the name clearly identifies the clone
  2. Review Instructions: Modify instructions if needed for the specific use case
  3. Test Thoroughly: Test the cloned agent before deploying
  4. Update Integrations: Verify tool connections work in the new context

Best Practices

  1. Use Descriptive Names: Name clones clearly (e.g., "Sales Agent - Q4 2024")
  2. Document Changes: Keep notes on why clones were created
  3. Clean Up: Delete unused clones to avoid clutter
  4. Version Control: Use version history instead of cloning for minor changes

Troubleshooting

Clone Missing Knowledge Base

Issue: Cloned agent cannot access knowledge base

Solution: - Review the clone’s Knowledge Base references and the intended user’s permissions - Verify the destination workspace has access to the knowledge repository - Re-configure knowledge base connections if in a different workspace

Clone Has Different Performance

Issue: Cloned agent behaves differently than original

Possible Causes: - Model availability differs between workspaces - Tool configurations need workspace-specific credentials - Knowledge base content differs

Solution: - Review all configuration sections - Test with the same queries as the original agent - Update credentials and tool connections as needed