Cursor forgets the plan. Assertion doesn't.
Unlike rules files, you don't write it or keep it up to date. It captures decisions and the reasons behind them as you work, updates them when you change your mind, and brings them back in later chats, citing where each came from. Free for individual developers, including at work.
- Free for individual developers
- Sign in during install
- Plugin source on GitHub
Memory keeps decisions and their reasons, not your transcripts or source code. What memory stores →
git clone https://github.com/Assertion-AI/assertioncd assertion/plugin/cursor && python3 install_cursor.pyPaste this into a terminal and press Enter.
Break the checkout form into smaller components.
Following the plan from Tuesday: one component per step (address, shipping, payment), validation in one shared hook, and the payment iframe left alone until the PCI review. Starting with the address step.
↳ recalled from memory · agreed Tuesday · checkout cleanup
“Our team works from one shared memory. When someone picks up our algorithm work, their coding agent already knows what everyone else has tried and why, so we build on each other's work instead of repeating it. Day to day, it's also made my LLM interactions more productive.”
Measured on BEAM 100K, a public long-term memory benchmark
81.1%
overall score
Hindsight, the leading memory system: 77.9%
98.3%
summarizing many sessions
Hindsight: 78.3%
31% less
memory per question
12.2k tokens vs 17.7k
Same answer model and judge for both. Ahead in all three runs; every answer is published. See the benchmark →
What happens next
- 1
Your browser opens
The installer adds the hooks and memory tools, then opens a sign-in page. Sign in with your email or Google and click Connect. If you're new, this creates your free account.
- 2
Quit Cursor and reopen it
Quit fully (
⌘Q), not just the window. Cursor loads new hooks and memory tools only when it starts. Then send one message. - 3
It comes back when it matters
In a later chat, when something you already settled comes up, Cursor uses it and says where it came from.
How you'll know it worked
- studio.assertion-ai.com/plugin lists this computer under Cursor, with its version and when it last captured.
- After some real work, studio.assertion-ai.com/memory shows what it kept.
If something's off
Nothing seems to be captured
Cursor was probably still running from before the install. Quit it with ⌘Q, reopen it, and send a message.
Signing in again
Run /assertion-login in Cursor.
Updating later
Run /upgrade in Cursor, or cd assertion && git pull in the folder you cloned. There's no need to run the installer again. Quit and reopen Cursor afterwards.
CI or a shared machine
Use a key instead of signing in: add --key and your key to the installer command. The key is on studio.assertion-ai.com/plugin under Use a key instead.
Still stuck? Email support@assertion-ai.com with what you ran and what you saw.
Using something else?
It's one memory. Whatever you keep here is there in the other tools too.