Deleting an Agent
Open in CMSDeleting an agent removes it β and everything attached to it β permanently. This page explains what that actually means, who can do it, and the safety check that stands in the way of a misclick.
Who can delete an agent? Only Owner and Admin, at the organization level. This used to be something the agent's own owner could do from inside the agent; it now belongs to organization administration instead.
What deletion removes
Deleting an agent cascades through everything that belongs to it:
- Its content β persona, conversation settings, knowledge base, tools, and channels
- Its authors and contributor assignments
- Any connected messenger accounts (WhatsApp, Instagram)
- Uploaded assets (documents, videos, images)
- Its users and participants
This cannot be undone. There is no trash, archive, or recovery step after deletion completes.
Why this moved to Organization
Deleting an agent is a decision about the organization's portfolio of agents, not about how one agent is configured. Tying it to Organization Admin/Owner means the people accountable for the organization's assets are the ones who can remove one β regardless of who happened to build it.
One consequence: an agent's original creator, if they only hold the Builder role, can no longer delete the agent they made. They can still edit it as a contributor; removing it is now an organization-level action.
Where to find it
Open the Organizations page β select your organization β Manage (gear icon) on the agent's card β Delete tile (Delete agent). (The Manage button only appears for Owners and Admins.)
The confirmation flow
Because deletion is irreversible, it uses a stricter confirmation than a simple "are you sure?" dialog:
- Click the Delete tile on the agent's Manage page.
- A confirmation dialog opens, showing the agent's name and a warning about what will be removed.
- Type the agent's exact name into the confirmation field. The Delete button stays disabled until the typed text matches.
- Click Delete once it's enabled. You are taken back to the organization's Agents page, which confirms the agent was deleted.
This type-the-name step is the same safeguard the agent's own sidebar used before the action moved here β it carried over unchanged, because it's what actually prevents an accidental click from destroying an agent.
Worked example
Dina, an Admin at Acme, needs to remove a test agent called Sandbox Bot that's no longer used.
She opens the organization β Agents tile β Manage on the Sandbox Bot card β Delete tile. The dialog warns her this will permanently remove the agent and its content. She types
Sandbox Botexactly, and the Delete button becomes enabled. She clicks it, lands back on the Agents page, and the card is gone.
Next step
Learn about the other agent-level administrative action: Admin Key.