Give Claude Code a memory.

It keeps what you decided and why, and brings it back in later sessions, citing where it came from. Personal memory is free, and you sign in as part of the install. There's no key to copy.

  • Free for personal memory
  • Sign in during install
  • Plugin source on GitHub
In Claude Code
  1. /plugin marketplace add Assertion-AI/assertion
  2. /plugin install assertion@assertion-ai
  3. /reload-plugins
  4. /assertion:login

Paste these into Claude Code one at a time.

Prefer the terminal?

Run this before you start Claude Code, then run /assertion:login inside it.

In a terminal
claude plugin marketplace add Assertion-AI/assertion && claude plugin install assertion@assertion-ai

What happens next

  1. 1

    Your browser opens

    /assertion:login 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. 2

    Memory is on in this session

    No restart. From here on, Claude Code keeps the decisions you make and the reasons behind them as you work.

  3. 3

    It comes back when it matters

    In a later session, when something you already settled comes up, Claude uses it and says where it came from.

How you'll know it worked

If something's off

Claude Code says /plugin isn't a command

Plugins need a recent Claude Code. Run claude update in a terminal, start Claude Code again, and repeat the commands.

The sign-in page sent me back to the start

Private browser windows can lose the sign-in partway through. Run /assertion:login again and finish it in a normal window.

Updating later

Run /assertion:upgrade, then /reload-plugins. Same session, no restart.

CI or a shared machine

Use a key instead of signing in. It's on studio.assertion-ai.com/plugin under Use a key instead. /assertion:logout signs this computer out.

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.