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

# Set up Atlaso

> One command sets up every tool on your machine — here's the shape of it, and what each tool can do automatically.

Setup is one command. It installs the CLI, links this machine, and then asks
which of your AI tools should share the memory — so you don't set them up one at
a time.

## The flow

**1. Run the install command**

```bash theme={null}
curl -fsSL https://atlaso.ai/install.sh | bash
```

Windows — and what the command actually does — are on [Install
Atlaso](https://docs.atlaso.ai/install.md). You don't need an account first; the next step creates one.

**2. Authorize in the browser**

A browser window opens by itself — that's this machine linking to your
account. Check it's **app.atlaso.ai** and click **Authorize**.

**3. Pick your tools**

Back in the terminal, the CLI lists the AI tools it found on this machine and
installs the integration for each one you pick. Change your mind later with
[`atlaso setup`](https://docs.atlaso.ai/cli#atlaso-setup).

**4. Done**

Each tool starts capturing as you work and recalling before your prompts —
nothing else to configure. Some tools need one restart to activate; the CLI
tells you which.

> [!NOTE]
>
> The browser opening on its own is expected — it's how this device links to
> your account. It only ever opens your Atlaso authorization page.

## If you'd rather not use a terminal

Claude Desktop, Claude.ai and other MCP chat apps connect over a URL instead —
no CLI involved. Sign in at [app.atlaso.ai](https://app.atlaso.ai), pick your
tool, and follow the connector steps: [Claude Desktop](https://docs.atlaso.ai/tools/claude-desktop.md),
[Claude.ai & GUI apps](https://docs.atlaso.ai/tools/gui-apps.md), or [any MCP tool](https://docs.atlaso.ai/tools/custom-mcp.md).

The dashboard also hands you the exact command for a tool, which is what you
want when you're adding a second machine — **Connections → Add a device**.

## What each tool supports

CLI and IDE tools get the full automatic loop: we install hooks that recall
before every prompt and capture after every turn. GUI chat apps connect through
MCP, where the model calls memory tools when it decides to — it works, but it's
model-initiated rather than automatic (see [Claude.ai & GUI
apps](https://docs.atlaso.ai/tools/gui-apps.md)).

| Tool | Auto recall | Auto capture | Ambient (Pro) | Notes |
| - | :-: | :-: | :-: | - |
| [Claude Code](https://docs.atlaso.ai/tools/claude-code.md) | ✓ | ✓ | ✓ | Hooks + MCP server + skill |
| [Codex CLI / Desktop](https://docs.atlaso.ai/tools/codex.md) | ✓ | ✓ | ✓ | One install covers both — they share `~/.codex` |
| [Cursor](https://docs.atlaso.ai/tools/cursor.md) | ✓ | ✓ | ✓ | Fully quit and reopen Cursor to activate |
| [OpenCode](https://docs.atlaso.ai/tools/opencode.md) | ✓ | ✓ | ✓ | Start a fresh session to activate |
| [Antigravity](https://docs.atlaso.ai/tools/antigravity.md) | ✓ | ✓ | ✓ | One install covers the IDE and the `agy` CLI |
| [Claude Desktop](https://docs.atlaso.ai/tools/claude-desktop.md) | — | — | — | MCP tools only — model-initiated memory |
| [Any MCP tool](https://docs.atlaso.ai/tools/custom-mcp.md) | — | — | — | MCP tools only — model-initiated memory |

## On the Free plan

Free includes one device and one active tool — the first tool you use claims
the slot automatically. A second tool keeps working locally but stops syncing
to your cloud memory. How that works and how to switch:
[One active tool on Free](https://docs.atlaso.ai/account/one-active-tool.md).

Claude Desktop and other MCP connectors count as their **own** device, which is
why connecting one through the CLI asks you to upgrade first.


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