> ## 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.

# Install Atlaso

> One command installs Atlaso, links this machine to your account, and wires up the tools you pick.

You don't need an account first. The command installs the Atlaso CLI, then opens
your browser to sign you in — creating your account if you don't have one — and
finishes by asking which of your AI tools should share the memory.

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

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

  ```powershell Windows theme={null}
  irm https://atlaso.ai/install.ps1 | iex
  ```
</CodeGroup>

macOS and Linux run the same script — it detects your platform and picks the
right binary. Windows is a genuinely different one-liner for PowerShell.

## What it does, in order

<Steps>
  <Step title="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`).
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Note>
  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.
</Note>

## 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](https://app.atlaso.ai) and follow the connector steps, or see
[Claude.ai & GUI apps](/tools/gui-apps).

## Options

The installer reads a few environment variables, which matter mostly for CI and
scripted setups:

| Variable              | What it does                                                                             |
| --------------------- | ---------------------------------------------------------------------------------------- |
| `ATLASO_NO_CONNECT=1` | Install the binary only — skip the browser handoff. Run `atlaso connect` yourself later. |
| `ATLASO_INSTALL_URL`  | Download binaries from somewhere other than our GitHub releases.                         |
| `ATLASO_HOME`         | Use a different home than `~/.atlaso` (macOS/Linux only).                                |

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.

<Warning>
  The Windows installer always runs `connect` after installing. For unattended
  Windows setups, set `ATLASO_NO_CONNECT=1` first.
</Warning>

## Upgrading and removing

Re-running the install command upgrades you in place — it's safe to run again,
and it won't duplicate your `PATH` entry or re-link the device.

There's no uninstall command. To remove Atlaso completely: run
[`atlaso disconnect`](/cli#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

<CardGroup cols={2}>
  <Card title="What setup looks like" icon="plug" href="/setup">
    The flow end to end, and what each tool can do automatically.
  </Card>

  <Card title="CLI reference" icon="terminal" href="/cli">
    Every command — connect, setup, status, sync, unlink, disconnect.
  </Card>
</CardGroup>