Decisions across IDE and CLI
A choice made while working in the IDE is there when you drop to the CLI, and the reverse. One memory, so the two surfaces never disagree about what you decided.
Persistent memory for Antigravity
Antigravity spans an IDE and a CLI, and Atlaso gives both a shared, automatic memory. One install covers them both, recalling what matters before each turn and capturing what's new after, across every agent run.
How it works
One command wires Atlaso into both the Antigravity IDE and CLI through their shared config. It adds hooks, an MCP server, a skill, and rules. Recall and capture are fully automatic in both surfaces, from the same memory.
What it installs: Hooks, MCP server, Skill, Rules.
01
Run one command
Paste the Atlaso install command in your terminal and pick Antigravity when it asks which tools should share your memory. Because the Antigravity IDE and CLI share config, one install covers both.
02
Authorize this device
The browser opens to connect this device to your Atlaso account. About a minute, no API keys.
03
Work across both
Recall and capture run automatically in the IDE and the CLI, from one shared memory, with nothing to switch on when you move between them.
What it remembers
Questions
Yes. Antigravity's IDE and CLI share the same config, so a single install wires memory into both. You don't set them up separately.
Still have a question?
Write to usOther tools
Memory built in Antigravity travels to every tool you connect.
Atlaso keeps one memory, not one per app. Connect Antigravity and it draws from, and adds to, the same memory as every other tool you use. One tool on one device is free; Pro shares that one memory across as many tools and devices as you like.
Never explain twice
Connect Antigravity and what you decide today is there in tomorrow's session, and in every other tool you use.
Get Started