Renor

io.github.patrickpassosbPublished by GitHub account patrickpassosbv1.0.1Updated Oct 29, 2026

Private memory for AI agents: save and recall facts across Claude Code, Codex, Cursor and ChatGPT.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Renor gives AI coding agents a shared private memory so facts and decisions saved in one session can be recalled by other agents later.

What you can do
  • Save decisions, corrections and facts as plain Markdown notes that persist across sessions.
  • Recall stored context before starting non-trivial work, with keyword search and optional hybrid keyword-and-meaning search.
  • Share one memory across multiple agents such as Claude Code, Codex, Cursor, Grok, Gemini, VS Code and OpenCode.
  • Run several agents against one memory with per-agent connection names to get multi-agent tools.
  • Check status and manage the local store, which keeps notes in a folder and a SQLite search index.
When to use it
Useful when you work with several coding agents and want decisions, root causes and corrections to carry over between sessions instead of being repeated. Also fits teams or individuals who want a self-hosted, file-based memory they own rather than a hosted service.
Requirements
Hosted option: remote endpoint at mcp.renor.cloud with OAuth sign-in and an account at renor.cloud. Self-hosted option: Node.js 22.16 or later, run via npx renor-engine mcp; notes go to ~/.renor unless VAULT_PATH is set. Optional OpenAI or local model for hybrid search; optional RENOR_CONNECTION_NAME for multi-agent use.
Before you install
The hosted path stores memory on Renor's servers and requires an account; the self-hosted path keeps notes locally. Anonymous telemetry is on by default and can be disabled with DO_NOT_TRACK=1 or the telemetry off command. Saved memory may include project details, so avoid storing secrets; the README's memory rule explicitly says not to save secrets.

Installation

In SourceWeft

  1. Open Renor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.patrickpassosb%2Frenor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "renor": {
      "type": "http",
      "url": "https://mcp.renor.cloud/mcp"
    }
  }
}

README

[Renor]

Shared memory for coding agents, over MCP.

What one agent learns in a session, every agent knows in the next.

How it works

  1. Tell one agent once: a decision, a root cause, a correction.
  2. Renor saves it as plain Markdown you own.
  3. Every agent recalls it in its next session: Claude Code, Codex, Cursor, Grok, Gemini, VS Code, OpenCode, Pi or any MCP client.

Quickstart

Two ways in. Both take under a minute.

Hosted: the easiest path

bash
npx renor connect --client claude-code

--client is claude-code, codex, cursor, grok, gemini, vscode, opencode or pi. One command adds Renor to that app, signs you in through the app's own flow (no token to copy), writes the memory rule below, and ends with a live check that your workspace answers. Search is hybrid (keywords and meaning). Sign up at renor.cloud.

Self-hosted: the private path

Your memory stays in a folder on your machine. No account, no API key. You need Node.js 22.16 or later (22.16+ or 24+); on an older Node, renor-engine prints one line saying so and exits.

bash
claude mcp add --scope user renor-local -- npx -y renor-engine mcpcodex mcp add renor-local -- npx -y renor-engine mcp

Restart the agent. The first start downloads about 12 MB, and the first Renor call works about 3 seconds after an empty start. Notes go to ~/.renor (set VAULT_PATH to use another folder).

Then add the memory rule to the agent's instructions file, so it saves on its own.

Cursor or VS Code, one click:

[Add to Cursor] [Add to VS Code]

Grok. Grok starts project servers only in a folder it trusts, so register Renor in the project:

bash
grok mcp add --scope project renor -- npx -y renor-engine mcp

Trust the folder in Grok, then restart Grok. To check it: ask Grok to save a real decision from your project, restart Grok, and ask about it in the new session. To turn telemetry off, set DO_NOT_TRACK=1 in the environment Grok runs in. Paste the memory rule into the project's AGENTS.md.

Any other MCP client: the command is npx with the arguments -y renor-engine mcp (stdio).

Check it works:

bash
npx renor-engine status

Then tell your agent a real decision ("remember that the orders service uses Postgres 16"), start a new session, and ask about it.

Running it on a server or with Docker: docs/self-hosting.md.

Several agents on one memory: start each with its own RENOR_CONNECTION_NAME and they get the multi-agent ("hive") tools (details).

The memory rule

Five lines that make agents save decisions, corrections and facts on their own. In our Grok test (grok-4.7, renor-engine 1.4.0, 3 Nov 2026), agents with the rule saved in 8 of 8 sessions and the next session recalled 5 of 5 project facts.

renor connect writes it for you. Self-hosted, paste it into ~/.claude/CLAUDE.md (Claude Code), ~/.codex/AGENTS.md (Codex) or the project's AGENTS.md (Grok):

md
## Renor memory
Renor is connected to this app and remembers across sessions.- Before deciding anything non-trivial, recall first: one get_context call is usually enough.- Save with remember when the user makes a decision, corrects you, or states a fact that should outlive this chat. Include the reason.- Save the specific value (a port, a name, a path), not a summary of it.- Do not save secrets, or things that are already in the code.

Self-hosted, the local tools are search, remember_fact and note; agents map the rule onto them (tool list).

What runs on your machine

  • Your memory is plain Markdown in one folder you own. Edit it with anything; back it up like any folder.
  • SQLite holds the search index, next to the notes. It is rebuilt from the Markdown at any time.
  • No embedding model needed. Search is by keyword; when the exact words miss, it retries with word stems. Hybrid search (keywords and meaning) is the hosted default; self-hosters can opt in to OpenAI or a local model (details).
  • Small: a 1.8 MB package, about 5 MB installed. About 143 MB of memory with 1,000 saved memories.
  • Telemetry: anonymous usage numbers (never text, names or paths) are on by default, with a notice on first run. renor-engine telemetry off or DO_NOT_TRACK=1 turns them off. Your memory text is never shared unless you say yes to that separately. Every field: docs/TELEMETRY.md.

Benchmarks

BenchmarkRenorSetup
LongMemEval-S98.4% (492/500)Deep search, off by default
LongMemEval-S94.4% (472/500)Default settings
LoCoMo (categories 1 to 4)96.7% (1,489/1,540)Deep search
BEAM 128K / 1M / 10M76.2 / 74.7 / 60.2Deep search, score out of 100
ConvoMem88.4% (191/216)Default search, 100 conversations per memory

Claude Opus 5.5 answers LongMemEval, LoCoMo and BEAM; DeepSeek V4.1 Flash answers ConvoMem (a research run). One run each, Oct 2026. Deep search is top-K 50 with a 4,000-token budget (RENOR_TOPK_SCALES_BUDGET=1). Judges and methods for every run: renor.cloud/research.

Build from source

You need Node.js 22.16 or later and git.

bash
git clone https://github.com/renorai/renor-engine.gitcd renor-enginenpm ci && npm run buildnode scripts/smoke-self-hosted.mjs

The last command starts the MCP server in a temporary folder, saves one fact, finds it again and ends with PASS: self-hosted stdio MCP can remember and retrieve a current fact. It never touches your notes. Downloaded a ZIP instead of cloning? Build with RENOR_BUILD_COMMIT=0000000 npm run build. Connecting a local build to each agent: docs/self-hosting.md.

Learn more

Docs · Self-hosting, servers and Docker · Every setting · Telemetry

License and contributing

The engine is Apache-2.0 (LICENSE); 1.0.0 was released under AGPL-3.0; 1.1.0 and later are Apache-2.0; files imported from the upstream project stay ISC (NOTICE, UPSTREAM.md). The renor CLI, the SDKs and the integrations are MIT.

Contributions are welcome: CONTRIBUTING.md has setup, tests and good first issues. Sign off each commit with the DCO (git commit -s); there is no CLA. Report vulnerabilities privately as described in SECURITY.md.

If Renor saves you re-explaining, a ⭐ helps other developers find it.

Source: README.md at commit ef6e988

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts