Agents
Run Atlas Agent, or any agent from the ACP registry, in the same chat.
Atlas runs its own agent, Atlas Agent, and any coding agent published in the official Agent Client Protocol registry: Claude Code, Codex, Cursor, OpenCode and more. You pick the agent in the composer. Atlas supplies the project and renders every agent's conversation through the same interface.
Whichever agent you run, session capture records the work the same way, so all of it reaches the timeline and links to commits.
Atlas Agent
Atlas Agent is built into Atlas and needs no install. It runs through the Atlas gateway on your Atlas account and is billed to your organization, so it needs no provider key. In exchange, it needs a signed-in, synced organization with AI access. Until then the composer explains what's missing and offers the next step.
It reads and edits files, searches the project, runs commands, uses skills and shared memory, and asks you a question mid-turn when a request is ambiguous. It can also navigate the Atlas window for you and, in a Cloud project, read and act in your organization.
Permission modes
Choose one of four modes in the composer, or press ⇧Tab to cycle through them:
| Mode | What Atlas Agent may do |
|---|---|
| Ask | Asks before edits and commands. The default. |
| Accept edits | Edits files in the project without asking. Asks before anything that reaches outside it. |
| Plan | Read-only. It reads and plans, with no edits and no commands that change anything. |
| Bypass | Runs everything without asking, with full access to your machine. |
In every mode except Bypass, commands run in a sandbox that can write only inside the project and has no network access unless you approve it.
Model
Pick a model from the list in the composer. The list comes from the Atlas gateway and shows the models your organization has access to. Atlas Agent offers no reasoning-effort control.
Limits
Atlas Agent takes text prompts only. It does not accept images yet.
Install an ACP agent
Open Settings → Agents to browse the registry, or install a popular agent with one click from the agent picker in the composer. Both routes create the same installation. Atlas does not ship a built-in copy of Claude Code, Codex, Cursor, OpenCode, Kilo Code or any other external agent.
When a newer version of an installed agent is available, an Update button appears above the composer of a session using it. See ACP registry for installing, updating and removing agents.
Expect capabilities to vary
ACP lets an agent advertise what it supports. Atlas shows only the controls and actions the connected agent provides, including:
- sign-in methods
- models, modes and configuration controls
- slash commands and permission requests
- session listing, loading and forking
- images and embedded terminals
An entry in the registry means Atlas can install and start it, not that it implements every optional ACP capability. Use the repository or website on its registry card for account setup and agent-specific behavior.
Switch agents in a session
Pick another agent from the composer at any point. What happens to a session that already has a conversation depends on Settings → Sessions → Switching agents in a session:
- Start over switches in place with a clean chat. This is the default.
- New tab keeps the conversation on screen and opens the new agent beside it.
- Hand off switches in place and attaches the conversation to your next message, so the new agent picks up where the last one stopped.
Every conversation stays in your history either way. Turn on Save to memory before switching agents to have the agent you're leaving save its decisions and findings to shared memory first, when it offers /remember.
Bring in earlier sessions
Agents that support session listing can bring their past sessions into Atlas. Open the project picker at the top of the sidebar and select Import sessions from agents….
Keep the record in Atlas
Every agent runs against the open project. Atlas keeps its sessions in your history, and session capture adds the work to the timeline and links commits to checkpoints.
To keep running an agent in its own terminal interface instead, the Atlas CLI records it through the agent's hooks.
Shared memory depends on capability. When memory sharing is on, Atlas offers its memory tools to Atlas Agent and to agents that advertise HTTP MCP support. The agent decides when to call them; agents without that capability don't receive memory.
Next
- Atlas Agent: what it can do in your app and your organization
- ACP registry: install, update or remove an agent
- Concepts: Atlas terminology