> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# Archive an agent

> Retire an agent, review the skills affected, and verify that its history remains available.

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.

<Warning>
  The app has no restore control for archived agents. Save any context you need and review the dependent records before confirming.
</Warning>

## 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](/registry/skills/how-tos/archive-skill) 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](/registry/agents/how-tos/edit-agent).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.