Skip to main content
Archiving an agent removes it from agent lists and stops its key from authenticating. Its page, sessions, and history remain readable by ID for people who can access them.

​
Before you begin

  • You need permission to archive the agent.
  • Stop workloads that use its credentials and review agents that call it as a sub-agent.
  • Review its skills. The app also tries to archive skills that only this agent uses; it keeps skills another agent uses.
The app has no restore control for archived agents. Save any context you need and review the dependent records before confirming.

​
Archive the record

  1. Open the agent’s profile.
  2. Open More agent actions and select Archive agent.
  3. Read the dependency list and the note explaining which skills will also be archived. Wait for the skill check to finish.
  4. Select Archive.
  5. Confirm the success message and check that the agent leaves the workspace’s active agent list.
If the app cannot check the skills, it leaves them in place. If the agent archives but some of its skills do not, the app reports how many failed. Open those skill pages and archive them separately if they should also be retired. System records and records blocked by a security scan cannot be archived through this flow. The dialog explains the refusal before confirmation.

​
Verify the effect

Existing calls using the agent’s key fail to authenticate. Agents that discover it as a sub-agent stop finding it. A saved link to its page still opens the archived record and its history, subject to access permissions. To change a name or description while keeping the agent active, edit the agent.