Skip to main content
Sometimes you want to duplicate an agent—either to create a variation for yourself, share it with another team, or let anyone on the internet use your creation. Abundly makes this easy with cloning.
Clone agent modal showing options to name the cloned agent and select which team to clone it to

​
Internal cloning

Internal cloning lets you duplicate an agent within your own workspace or to another team you’re a member of. This is useful when you want to:
  • Create a variation of an existing agent with different instructions
  • Set up a similar agent for a different team or project
  • Make a “template” agent that you can clone and customize for different use cases
To clone an agent, open the agent’s settings and click Clone. You’ll be asked to name the new agent and choose which team to clone it to.

​
What gets cloned

CopiedNOT copied
Agent name (with ” Clone” suffix)Chat conversations
Description and profile pictureAPI keys and credentials
InstructionsScheduled triggers (cross-team only)
CapabilitiesPublic sharing settings
LLM configuration and model
Agent status
Scheduled tasks
When cloning to a different team, credentials and scheduled triggers are reset for security reasons. You’ll need to reconnect any integrations that require authentication.

​
Including documents

When cloning, you can optionally include the agent’s documents. Enable Include documents in the clone modal to copy all agent documents—including files, databases, and apps—to the new agent.

​
Access on cloned agents

The person who performs the clone automatically becomes an Admin of the new agent, regardless of their access level on the source agent. For same-team clones, the original access settings are preserved. For cross-team clones, only the person who cloned it gets Admin access initially.

​
Public sharing

Public sharing lets you publish your agent so anyone with a link can clone it to their own workspace. This is perfect for sharing agent templates, showcasing your work, or letting others benefit from an agent you’ve built.
Public sharing settings panel with toggle to allow public cloning and a shareable link

​
Enabling public sharing

  1. Go to the agent’s Settings → Public sharing tab
  2. Toggle Allow public cloning on
  3. Copy the Public Clone Link to share with others
When someone clicks your link, they’ll see a landing page with the agent’s name, description, and a button to clone it.
Shared agent landing page showing agent name, creator, and Clone this agent button

​
What’s publicly visible

When you enable public sharing, visitors can see:
  • Agent name and description
  • Your name (as the creator)
  • The agent’s instructions (they can click “See agent instructions” to view them)
Visitors cannot see chat conversations, credentials, or documents (unless you’ve enabled document cloning).

​
Including documents in public shares

You can optionally allow people who clone your public agent to also receive copies of its documents. Enable Also clone my documents in the public sharing settings to include documents in the clone.
If your agent relies on specific reference documents to work properly, consider enabling document cloning so people get the full experience.

​
Cloning someone else’s public agent

When you find a public agent you want to clone:
  1. Click the shared link to view the agent
  2. Click Clone this agent
  3. If you’re not logged in, you’ll be prompted to sign in or create an account
  4. Choose a name for your clone and select which team to add it to
  5. Click Clone to create your copy
The cloned agent is completely independent—changes you make won’t affect the original, and updates to the original won’t affect your clone.

​
Example use cases

  • Template library: Create a collection of “starter agents” that team members can clone and customize for their specific needs
  • Cross-team deployment: Build an agent once, then clone it to multiple teams in your organization
  • Community sharing: Share useful agents with the broader Abundly community via public links
  • Backup and versioning: Clone an agent before making major changes, keeping the original as a backup

​
FAQ

Not currently. The system tracks clone relationships internally, but there’s no UI to browse this data.
Cloned agents track their source internally, but they are completely independent. Changes to one don’t affect the other, and if the original is deleted, the clone continues to work normally.
You need Admin access on the agent to change public sharing settings.
You need Use access on the source agent to clone it.
Yes. If your workspace uses groups, you can choose which group to place the cloned agent in. If you don’t have permission to create global agents, you must select a group.
No. Clones are completely independent from the moment they’re created. Updates to the original don’t propagate to existing clones.

​
Learn more

Agent Management

Organize and manage agents across your team

Groups

Organize agents and team members into groups

Access Control

Configure who can access your agents