Claude Code Keeps Forgetting? Give It a Memory That Lasts

Yesterday you told Claude Code how to run your tests. Today it asks again.

This guide fixes that with one install command, one saved fact, and a fresh session that already knows it.

Why Claude Code forgets

A Claude Code session works with what is in its current context. When the session ends, so does that context.

Claude Code's own memory files help with standing instructions. But the facts you settle while working, such as a test command, a decision or a gotcha, usually stay in the conversation where they came up.

Ragionex Memory gives Claude Code a place to save those facts as they happen and search them in any later session. You can open, edit and delete every saved memory in your dashboard.

Set it up in three steps

You need Node.js 18 or later and Claude Code installed.

1. Run the setup

Run this in a terminal:

npx.cmd -y @ragionex/memory-mcp@latest install --agent claude-code

npx -y @ragionex/memory-mcp@latest install --agent claude-code

Or paste this into Claude Code, and it runs the setup for you: Set up Ragionex Memory for yourself by following the instructions at https://ragionex.com/setup.

2. Approve it in your browser

The setup shows a link. Open it and sign in; a new account is free and comes with a Vault called My vault. The page shows a one-time code: paste it into the terminal, or into the chat if Claude Code runs the setup.

The setup registers Ragionex with Claude Code and adds its memory instructions. No config files to edit.

3. Restart Claude Code

Quit Claude Code completely and open it again. Then ask:

Check my Ragionex Memory connection.

You should see your Vault name and your key's permissions.

The "same fact, new session" test

Pick one fact you are tired of repeating. Here is an example with a made-up project:

Save this in Ragionex Memory:
For acme-app, run the API tests with python3 -m pytest tests/api.
Use the local test database. Never use production credentials for tests.

A new memory needs to finish processing before it becomes searchable.

Now close the session and start a new one. Do not paste the fact back in. Ask:

How do I run the API tests for acme-app, and which database do they use?
Check Ragionex Memory first.

The new session searches your memory, finds the saved fact and answers from it: the exact command, the local database and the production rule. You can ask it to show the saved text, so you see where the answer came from.

What to save first

Start with the things you retype most:

Write each memory as a complete sentence with its context. "Use port 5433" is weak. "acme-app's local Postgres runs on port 5433" works in any future session.

Offline saves wait for a connection

No connection, or no requests left in this 30-day period? The save is kept on your machine and sent automatically once the connection is back or a new period starts, as long as the connector is running. Up to 100 saves can wait at a time.

Next steps

• Use the same memory from Codex and OpenCode: share one memory across all three agents
• Turn saved decisions into a second brain: save the reasons behind your decisions
• Fix a memory that is wrong or out of date: correct the saved memory itself

Start free

The Free plan includes 10,000 requests every 30 days, memories up to 10,000 characters, 2 Vaults and 100 API keys. A new memory, a content edit or a search call is one request. Browsing, viewing, exporting and deleting are not counted.

Set it up in one line and give your next Claude Code session something to remember. The Memory quickstart has the full reference.