Skip to main content

Cloning an agent

The Cloner flow lets any tenant member discover a shared agent in the Internal Marketplace, trial it, and bring a copy into their own project.

Who can clone​

Any tenant Member or higher by default. Tenant admins can restrict cloning to specific roles or disable it for the workspace — see Admin controls.

Browse the Marketplace​

Open the Marketplace sidebar tab. The browse surface lists every Internal Marketplace listing in your tenant.

Each listing card shows:

  • Name + creator.
  • Description (truncated; click for full).
  • Clone count — how often the listing has been cloned.
  • Last updated.

No additional permission gate is required to browse — every tenant member can see what's available.

Try before you clone​

Click Try on a listing to open a sandboxed trial session:

  • The session is isolated from your projects — nothing is permanently added.
  • A pre-trial checklist surfaces what's needed to make the trial usable — adding credentials, KB stub content, LLM selection.
  • Trial credits are drawn from your account only. The Builder is never charged for trials.

Use the trial to confirm the agent does what you expect before you commit a clone into a project.

Clone — the 4-step flow​

When you're ready to clone:

1. Pick a destination project​

Choose an existing project, or create a new one. The cloned agent lands in the project's Applications tab, tagged "Cloned from: <Source>".

2. Pre-clone summary​

The clone modal shows a summary of what the clone will bring in:

  • Tools the agent uses.
  • Sub-agents it invokes.
  • Knowledge Base resolutions — for each referenced KB, the source's resolution (dummy stub / generated KB / your KB to map).
  • Credentials required — items marked "Action Required" are highlighted.
  • Optional components — items the agent supports but doesn't require; you can choose to include or skip.

3. Clone executes​

  • The Builder's published version is snapshotted as an immutable "Cloned from v<X>" baseline. Your clone is independent from the Builder's source from this moment forward.
  • If the clone fails for any reason, the platform performs a full rollback — there is no partial clone state to clean up.
  • On success, the cloned agent is fully installed in your destination project.

4. Setup dialog (conditional)​

If the source listing has credentials marked "Required by cloner", the Setup dialog opens automatically on first open of the cloned agent. Fill in the required values (API keys, connections, etc.).

Until the setup is complete, the agent shows an orange "Setup Incomplete" badge in your Applications list. You can't run it productively until setup is finished.

After cloning — editing and re-sharing​

  • The cloned agent is first-class — edit it like any agent you built yourself.
  • You cannot re-share the clone. Only the original Builder can publish the source as a Marketplace listing. If you want to share your customized variant, build it from scratch (or fork it via copy) and share the new copy.
  • You retain the clone regardless of what happens to the source — if the Builder unpublishes, disables, or even has the listing removed by an admin, your cloned copy continues to work.

Billing during and after a clone​

  • Trial — your credits, charged at the trial rate.
  • Failed clone — zero charge to either party.
  • Post-clone runs — your credits, like any other agent in your account.
  • The Builder is never billed for any execution you trigger.

Where cloned agents show up in audit​

Every clone event appears in the Audit log with the action "Clone initiated", "Clone completed", or "Clone failed", plus the destination project and outcome. The Builder analytics view will reflect the clone count and your org name, but never your individual identity.