Skip to main content
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

Windows — and what the command actually does — are on Install Atlaso. 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.
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.
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, pick your tool, and follow the connector steps: Claude Desktop, Claude.ai & GUI apps, or any MCP tool. 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).

​
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. Claude Desktop and other MCP connectors count as their own device, which is why connecting one through the CLI asks you to upgrade first.