# Atlaso

> The memory layer for the AI era — docs and help for Atlaso.

## Docs

- [One active tool on Free](https://docs.atlaso.ai/account/one-active-tool.md): Why a second tool runs in local-only mode, what still works, and how to switch which tool is active.
- [Plans & billing behavior](https://docs.atlaso.ai/account/plans.md): What Pro adds, how upgrading and cancelling work, and what never happens to your memories.
- [Your data, plainly](https://docs.atlaso.ai/account/privacy.md): What gets stored, what gets scrubbed before storage, what your memory is never used for, and how to delete or export it.
- [Troubleshooting](https://docs.atlaso.ai/help/troubleshooting.md): The exact messages you might run into, what each one means, and the fastest fix.
- [Welcome](https://docs.atlaso.ai/index.md): Setup is one command. This is everything else.
- [Set up Atlaso](https://docs.atlaso.ai/setup.md): The exact, copy-paste instructions live in the app — this page covers what to expect, and what each tool can do automatically.
- [Antigravity](https://docs.atlaso.ai/tools/antigravity.md): Full automatic recall and capture in both the IDE and CLI.
- [Claude Code](https://docs.atlaso.ai/tools/claude-code.md): Full automatic memory: recall before every prompt, capture after every turn.
- [Claude Desktop](https://docs.atlaso.ai/tools/claude-desktop.md): Connects through a custom connector (MCP) — memory works when Claude calls the tools, not automatically.
- [Codex CLI & Desktop](https://docs.atlaso.ai/tools/codex.md): Full automatic memory in Codex CLI; Codex Desktop installs the same plugin via its marketplace.
- [Cursor](https://docs.atlaso.ai/tools/cursor.md): Automatic capture; recall arrives through a generated rules file.
- [Claude.ai & GUI apps](https://docs.atlaso.ai/tools/gui-apps.md): Adding Atlaso as a custom connector — and why GUI clients work differently from CLI tools.
- [OpenCode](https://docs.atlaso.ai/tools/opencode.md): Full automatic recall and capture via the npm-distributed plugin.