Clone, archive, and delete
Manage assistant lifecycle without losing work — clone for experiments, archive to hide from deployments, or delete when no longer needed.
Clone an assistant
Section titled “Clone an assistant”Agent Builder (admin only) is the fastest way to duplicate an assistant with its prompt, model, KB attachments, and tools:
- Open Agent Builder in the dashboard.
- Ask: “Clone the Website Support assistant as Staging Support.”
- Review the proposed copy and confirm.
Agent Builder creates a new assistant record — it does not copy underlying knowledge-base documents (those remain shared org resources).
See What is Agent Builder? and Agent Builder limits.
Manual alternative
Section titled “Manual alternative”- Assistants → open source assistant → note settings.
- Create assistant with the same master prompt, model, RAG settings, KB, and tool attachments.
- Test before switching deployments.
Archive an assistant
Section titled “Archive an assistant”Archiving hides an assistant from active deployment pickers while preserving configuration and conversation history.
- Assistants → ⋮ menu → Archive.
- Confirm — linked deployments stop serving this assistant until you reassign them.
Use archive when sunsetting a bot but keeping records for compliance or analytics.
Delete an assistant
Section titled “Delete an assistant”Permanent deletion removes the assistant configuration. Conversations may be retained per your organization’s data policy.
- Assistants → ⋮ menu → Delete.
- Confirm — only admins can delete.
Before deleting: re-point or delete deployments that reference this assistant. See Deployments overview.
Plan limits on clone
Section titled “Plan limits on clone”Cloning counts toward your plan’s assistant limit. If you are at capacity, upgrade or archive unused assistants first. See Limits by plan.