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

# Troubleshooting

> The exact messages you might run into, what each one means, and the fastest fix.

These are the exact messages you might see, what each one means, and the
fastest fix. If yours isn't here, email
[support@atlaso.ai](mailto:support@atlaso.ai) with the message text and
we'll sort it out.

## Messages you might see

<AccordionGroup>
  <Accordion title="device limit reached for your plan">
    The Free plan includes one device. Either disconnect the old device first
    (**app.atlaso.ai → Connections → Disconnect** — this never deletes
    memories), or upgrade to Pro for unlimited devices.
  </Accordion>

  <Accordion title="… isn't your active tool on the free plan — running in local-only mode">
    Not an error — your second tool keeps working locally but doesn't sync to
    your cloud memory. Switch which tool is active in **Connections**, or
    upgrade for unlimited tools. Full explanation:
    [One active tool on Free](/account/one-active-tool).
  </Accordion>

  <Accordion title="Ambient Memory is a paid feature / Ask your memory is a paid feature">
    Ambient Memory, background enrichment, and Ask your memory are Pro
    features. Upgrade in **Settings**; everything else — capture, recall,
    sync, dashboard — is free.
  </Accordion>

  <Accordion title="invalid or expired token — run `atlaso connect`">
    This device's connection expired or was revoked (for example, after a
    disconnect from the dashboard). Re-run your tool's install command from
    **Connections** — the browser opens, you click Authorize, and the device
    is re-linked. Your memories are untouched.
  </Accordion>

  <Accordion title="Waiting for authorization… (stuck)">
    The browser step didn't complete. Check the tab that opened (or open the
    URL printed in your terminal), make sure you're signed into the right
    Atlaso account, and click **Authorize**. The request expires after a few
    minutes — **Try again** generates a fresh one.
  </Accordion>

  <Accordion title="A browser window opened by itself when my tool started">
    Expected, once per device: that's the authorization step linking the tool
    to your account. It only ever opens your Atlaso authorization page —
    check the address is **app.atlaso.ai** before clicking Authorize.
  </Accordion>
</AccordionGroup>

## Tool-specific

<AccordionGroup>
  <Accordion title="Claude Desktop: the connector doesn't appear / never remembers on its own">
    Two separate things. (1) After adding the connector, fully quit Claude
    Desktop from the menu (not just closing the window) and reopen it. (2) No
    automatic memory is by design in GUI clients — Claude calls the memory
    tools when it decides to; say "check my Atlaso memory" to prompt it. See
    [Claude.ai & GUI apps](/tools/gui-apps).
  </Accordion>

  <Accordion title="Codex Desktop: memory went quiet">
    A known Codex Desktop issue can stop plugin hooks from firing after
    certain updates. Set `ATLASO_DEBUG=1` in your environment to see whether
    hooks are running; if they aren't, reinstall the plugin from the
    marketplace. Codex CLI is unaffected.
  </Accordion>

  <Accordion title="Cursor: a .cursor/rules/atlaso-recall.mdc file appeared in my repo">
    Normal — that's how recalled memory reaches Cursor (its native injection
    isn't available, so recall arrives as a rules file). It's regenerated
    automatically; add it to `.gitignore` if you don't want it in version
    control.
  </Accordion>
</AccordionGroup>

## Still stuck?

Include the exact message text and which tool you're using — that's usually
enough for a one-reply fix. [support@atlaso.ai](mailto:support@atlaso.ai)