v0.8.0

Ragionex Memory 0.8.0 connects your agent through a link you approve in your browser, with no emailed code to wait for.

Highlights

• Approve in your browser. Paste this into your agent: Set up Ragionex Memory for yourself by following the instructions at https://ragionex.com/setup. The setup shows you a link. Open it, sign in and give your agent the one-time code the page shows. The setup then creates the agent's own key and connects it. Quit your agent completely and open it again in a new session. A new account is free.
• In a terminal. Run npx -y @ragionex/memory-mcp@latest install (npx.cmd on Windows), pick your agent and open the link it shows. If you mistype the code, the setup asks again on the same link.
• More agents. Claude Code, Codex and OpenCode are set up automatically. Other agents that run local MCP servers and have a global instructions file can use manual setup (--agent manual), which fills in the key and keeps the memory rule up to date. The setup page walks through it.
• Made for agents. install --agent-mode --agent <code> prints each step with the flags that answer it and never waits for input, so your agent can run the setup for you.
• Clearer messages. A save that is not confirmed yet names the reason: a rate limit, a service error, no connection, or a request to wait.
• Node.js check. Node.js older than 18 now gets a clear message instead of an unrelated error.

Breaking changes

• The emailed-code setup of 0.7.0 and --email are gone. --code now goes together with --link, as the setup prints them. Use @latest for a new or unfinished setup.
• --all-agents is removed from install and uninstall. Run each once per agent. Without a terminal, name the agent with --agent <code> or use --manual.
• The connection check no longer offers to import what your agent already knows.

Upgrade

Nothing to do if your agent already works: it starts the latest version through npx the next time it restarts, and your key and memories stay as they are. If an earlier setup did not finish, run the setup again.

npm: @ragionex/memory-mcp@0.8.0

v0.7.0

Ragionex Memory 0.7.0 sets up your agent without copying an API key.

Highlights

• Setup without a key to copy. Paste this into Claude Code, Codex or OpenCode: Set up Ragionex Memory for me: run npx -y @ragionex/memory-mcp@latest install and follow its instructions. Your agent asks for your email address and the one-time code Ragionex sends you, then the setup creates the agent's own API key and connects it. Restart the agent once to load it. An address without an account gets a free one. You can also run npx -y @ragionex/memory-mcp@latest install in a terminal.
• One key per agent. The setup creates a key for each agent it connects, named after the agent and the date, such as Claude Code (set up 2026-10-31). Earlier keys stay in the dashboard until you revoke them.
• Claude Code in the desktop app. The setup finds the Claude Code that started it, including the one inside the Claude desktop app, even when no claude command is on your PATH.
• Bring what your agent already knows. When the selected Vault is empty, checking the connection offers to import what your agent already knows from its rules files and its notes for this project.
• Windows. Registering the server and updating config files are more reliable on Windows, and install and uninstall no longer abort when they finish.
• Version label. Requests to the Ragionex API identify the connector as ragionex-memory-mcp/<version>.

Breaking changes

• install --api-key is no longer accepted. Run install without it and the setup creates the key. For other MCP clients, create a key in the dashboard and add it to the client's configuration as RAGIONEX_MEMORY_API_KEY.

Upgrade

Nothing to do if your agent already works: it starts the latest version through npx the next time it restarts, and your key and memories stay as they are. If an earlier setup did not finish, run the setup again.

npm: @ragionex/memory-mcp@0.7.0

v0.6.0

Ragionex Memory 0.6.0 gives your agents a memory they manage on their own, organized in Vaults you can share with your team.

Highlights

• Vaults. Each project can keep its own memory. A RAGIONEX_MEMORY.jsonc file in the project folder pins the Vault its agents use, and a search never crosses into another Vault. Share a Vault with teammates from the dashboard, with Read, Create, Update and Delete permissions per member.
• Automatic memory. For Claude Code, Codex and OpenCode, the memory rule that install adds guides your agent to check memory before it answers, acts or asks you, to save lasting decisions, preferences and project facts on its own, and to update or merge records instead of piling up duplicates.
• Version history and trash. Earlier versions of every memory and deleted records are kept for 30 days. Bring any of them back by asking your agent.
• Safer saves. Saves are written to disk before they are sent and retried automatically, so an outage only delays them and a retry never creates a second record.
• Better recall. Ask one complete question per need, optionally limited by creation date, and get results page by page.
• One-command setup. install and uninstall replace init for Claude Code, Codex and OpenCode, with Windows support for Claude Code.

Breaking changes

• init is replaced by install.
• The project tools (ragionex_list_memory_projects, ragionex_rename_memory_project, ragionex_delete_memory_project) are removed. Vaults are created and managed in the dashboard.
• Tool arguments and replies changed: project is removed (the selected Vault applies), recall takes one query and a page number, updates need the full content and the expected_revision from the latest read, lists return up to 100 records per page, delete moves records to the trash, and replies are text only (no structuredContent).
• Saves still waiting from 0.5.1 in ~/.ragionex/pending-memories.jsonl are not sent automatically. Ask your agent to check the connection, which lists the file for review.
• RAGIONEX_API_BASE must be a direct HTTPS address without redirects, credentials, a query or a fragment; only localhost, 127.0.0.1 and [::1] may use HTTP.

Upgrade

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

Use --agent codex, --agent opencode or --all-agents for other agents. Enter your API key when the installer asks for it, so it also updates the agent's registration, then restart the agent. Your existing memories are already in your account's default Vault.

npm: @ragionex/memory-mcp@0.6.0