Skip to main content

​
Install

One command sets up Cursor along with any other AI tools on this machine:
Pick Cursor when the CLI asks which tools should share your memory. Already have Atlaso? Run atlaso setup and add it.
Last step — fully quit and reopen Cursor (Cmd/Ctrl+Q). A window reload connects the tools but won’t start the memory hooks; a restart does.
Cursor has no cursor plugin install command, so the Atlaso CLI installs the plugin by writing it to ~/.cursor/plugins/local/atlaso itself. If you’d rather add it from Cursor’s chat:
Use the full atlaso-labs/cursor name — the short /add-plugin atlaso form needs our Cursor Marketplace listing, which is still in review, and won’t resolve until it lands.The CLI path is the one we test, and it’s the only one that also links the device and installs your other tools in the same pass.

​
How recall works in Cursor

Recall reaches Cursor through a small generated rules file at .cursor/rules/atlaso-recall.mdc. That file appearing in your project is normal — it’s refreshed automatically and safe to add to .gitignore if you don’t want it in version control.
Cursor’s background/cloud agents don’t run the memory loop — memory works in your editor sessions.

​
What it wires

​
Removing it

That revokes Cursor’s access and removes the plugin. By hand: rm -rf ~/.cursor/plugins/local/atlaso, or Cursor → Customize → Plugins.