Skip to main content
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 with the message text and we’ll sort it out.

​
Messages you might see

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.
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.
Ambient Memory, background enrichment, and Ask your memory are Pro features. Upgrade in Settings; everything else — capture, recall, sync, dashboard — is free.
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.
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.
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.

​
Tool-specific

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

​
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