ACP registry
Install and manage agents from the official ACP catalog.
Open Settings → Agents to browse the official Agent Client Protocol registry. The registry is the catalog for external agents in Atlas; there is no separate list of built-in external agents.
Find an agent
Search by name, ID, or description. Filter the catalog to All, Installed, or Not Installed. Atlas refreshes stale data itself, but Refresh fetches the latest catalog whenever you need it.
Atlas currently runs registry entries that publish an npx package or a binary for your platform. A binary-only entry stays visible but cannot be installed when the registry has no build for your operating system and architecture.
The ACP registry also accepts uvx-only entries. Atlas does not run that distribution type yet, so those entries do not appear in its catalog.
Install an agent
Select Install on an agent card. This adds the agent to Atlas immediately; Atlas resolves and downloads its package the first time it connects.
For npx agents, Atlas manages its own Node.js runtime and keeps each agent in a separate install directory. Binary agents use the archive and command published for your platform. If an agent is already on your PATH, its card can offer that detected copy instead of downloading another one.
Installed agents appear after Atlas Agent in the switcher, sorted by name.
Update an agent
When the registry publishes a newer version of an installed agent, Settings → Agents offers an update, and a session using that agent shows the new version and an Update button above the composer. The update waits for any reply in progress to finish, then installs. Your conversation continues on the new version with your next message.
Atlas Agent has no registry update. It's updated with Atlas itself.
Remove an agent
Select Remove and confirm. Atlas stops any live connection, removes the agent from the switcher, and deletes its managed package cache. Existing sessions stay in history, and you can install the agent again later.
Atlas Agent is not a registry card because it runs in process and cannot be removed.
Read the trust signal
Unverified marks a binary distribution for which the registry publishes no checksum. Atlas checks a registry checksum when one is available and may recover a checksum from a GitHub release asset, but the badge is only a transport-integrity signal. It is not a security review or an endorsement of the publisher.
Work offline
Atlas opens its last good cached catalog first and refreshes stale data in the background. A failed refresh keeps the cached list. You can browse that list offline, but a package that has not been downloaded still needs a network connection on first use.
Use the agent
Registry agents work in the open project, and their sessions can join the same timeline and checkpoint record. Authentication, model choices, commands, session restoration, image input, terminals, and memory access depend on the capabilities each agent advertises. Use the repository or website on its card for setup help.
Next
- Agents: how agents and their capabilities work in Atlas
- Atlas Agent: the agent built into Atlas
- Concepts: learn Atlas terminology