What it does, in order
1
Installs the CLI
Downloads the
atlaso binary for your platform into ~/.atlaso/bin and adds
that directory to your PATH (on Windows, %USERPROFILE%\.atlaso\bin).2
Opens your browser to authorize
The installer hands off to
atlaso connect, which opens your browser. Sign
in — or create your account here, if this is your first time — and click
Authorize to link this machine.3
Asks which tools to wire up
Back in the terminal, the CLI lists the AI tools it found on this machine.
Pick the ones that should share your memory and it installs each integration
for you — no config files, no API keys.
4
Done — memory runs by itself
Each connected tool now recalls what matters before your prompts and captures
as you work. Some tools need one restart to activate; the CLI tells you which.
The browser opening on its own is expected — it’s how this machine links to
your account, and it only ever opens your Atlaso authorization page. Check the
address bar says app.atlaso.ai before you click Authorize.
No terminal? Start in the browser
Claude Desktop, Claude.ai and other MCP chat apps don’t need the CLI at all — they connect over a URL and authorize in the browser. Sign in at app.atlaso.ai and follow the connector steps, or see Claude.ai & GUI apps.Options
The installer reads a few environment variables, which matter mostly for CI and scripted setups:
If there’s no interactive terminal — a CI job, or an agent running the command —
the macOS/Linux installer stops after installing and tells you to run
atlaso connect when you have a terminal, rather than hanging on a prompt.
Upgrading and removing
Re-running the install command upgrades you in place — it’s safe to run again, and it won’t duplicate yourPATH entry or re-link the device.
There’s no uninstall command. To remove Atlaso completely: run
atlaso disconnect to unlink the machine, remove each
tool’s integration with the commands it prints, then delete ~/.atlaso and the
PATH line the installer added to your shell profile.
Next
What setup looks like
The flow end to end, and what each tool can do automatically.
CLI reference
Every command — connect, setup, status, sync, unlink, disconnect.