remnic MCP工具

Prerequisites

• Node.js 22.12 or newer.
• A model provider for extraction (an OpenAI API key, the OpenClaw gateway model chain, or a local LLM). Retrieval-only mode needs none of these.
• Optional but recommended: QMD for the highest-quality hybrid search. Without it, Remnic falls back to embedding search and then recency-ordered reads.

Build for Good 2026: What Helps Me

Explain what helps once. Share only what you choose. Stop sharing at any time.

What Helps Me is a private support passport built on Remnic. It turns selected memories into short first-person cards. The owner reviews every word before a helper can see it.

No OpenAI API key is required. Manual cards need no model. Draft and question calls use the owner's existing Remnic route, including an OpenClaw gateway or a local model.

Watch the narrated 102-second product story or read the full Build for Good entry. The walkthrough always shows a Synthetic replay banner. It is not live-call proof. The separate live runner exercises the real standalone server and model flow. Its receipt validator checks internal consistency, not independent proof.

OpenAI Build Week 2026: Remnic Relay

Correct once. Every agent learns.

Remnic is shared memory for AI agents. Remnic Relay is the human-governed correction loop we built for OpenAI Build Week: it exposes the stale belief behind an agent failure, shows where that belief came from, puts the proposed replacement behind human approval, and proves a brand-new agent learned the approved correction from Remnic.

The demonstration follows an online-payment failure. One Codex agent reads the current rule while another confidently applies an older retry rule. Relay opens an evidence X-Ray connecting the recalled memory to the failing test, presents a before-and-after memory diff for approval, preserves the old belief as superseded, and then starts a fresh agent with no handoff. The mission is only complete when that agent recalls the replacement and turns the same payment test green.

What we built during Build Week

- a versioned contract for conflicts, evidence, corrections, lineage, and fresh-agent verification; - a human-gated correction engine with append-only supersession; - Mission Control views for conflict inspection, evidence X-Ray, approval, propagation, and the final mission receipt; - an isolated four-role Codex mission runner using only a cleared synthetic Remnic instance; and - a dependency-free judge package that binds the recorded agent run, product UI, synthetic fixture, and verification receipt into one reproducible story.

Install, supported platforms, and testing

The fastest judge path uses the committed synthetic mission and requires no dependency install, model call, account, or credential:

git clone https://github.com/joshuaswarren/remnic.git
cd remnic
node scripts/relay/judge-package.mjs serve

Open the printed loopback URL, compare the current and stale beliefs, open the X-Ray, review and approve the proposed correction, and follow the fresh agent through the passing payment test. Verify the same evidence from the terminal:

node scripts/relay/judge-package.mjs verify
node scripts/verify-relay-judge-package.mjs

- Judge package: Linux with procfs and Node.js 22.12 or newer; Linux x64 is independently clean-room verified. - Mission Control: Chrome/Chromium 151 verified at desktop and mobile sizes, including keyboard-only and reduced-motion flows. - Live isolated mission runner: Linux x64 with Codex CLI 0.144.4 or newer and the repository development dependencies. This is not required for the judge experience. - macOS and Windows: use the submission video/gallery or run the verifier in a supported Linux environment. The executable verifier fails closed where equivalent filesystem-safety primitives are unavailable.

Remnic's core memory engine, integrations, and benchmark framework predate Build Week. The submission ledger separates that foundation from the new Relay work. See the judge guide and claim ledger for the complete evidence.

Quick start

Configuration

Remnic is zero-config by default: remnic init writes a working remnic.config.json and every subsystem ships a sensible default. When you need control, there are hundreds of options grouped under four presets, selectable with a single memoryOsPreset key:

• conservative — minimal footprint, extraction judge and heavier features off.
• balanced — the general-purpose default.
• research-max — every quality feature enabled, highest cost.
• local-llm-heavy — tuned for local-model extraction and rerank.

Extraction routing (gateway, OpenAI, or a local LLM), recall budget, search backend, lifecycle, namespaces, and encryption are all configurable. Every setting, its default, and operator guidance live in docs/config-reference.md.

OpenClaw (native plugin)

OpenClaw gets the deepest integration: a memory-slot plugin that recalls every session and observes every response.

openclaw plugins install clawhub:@remnic/plugin-openclaw   # install the plugin
remnic openclaw install                                    # wire the memory slot in openclaw.json
launchctl kickstart -k gui/$(id -u)/ai.openclaw.gateway    # restart the OpenClaw gateway (macOS)
remnic doctor                                              # verify every check passes

remnic openclaw install writes plugins.entries["openclaw-remnic"] and sets plugins.slots.memory = "openclaw-remnic" in ~/.openclaw/openclaw.json. Without the slot, OpenClaw skips plugin registration and no hooks fire, so remnic doctor checks the slot explicitly and points you at the fix. After the restart, confirm the plugin is live:

grep "gateway_start fired" ~/.openclaw/logs/gateway.log

A matching line means Remnic is active and hooks are firing. (The [engram] log prefix remains during the v1.x compatibility window.)

Prefer to let the agent do it? Tell any OpenClaw agent: "Install the @remnic/plugin-openclaw plugin and configure it as my memory system." It runs the install, updates openclaw.json, and restarts the gateway for you. Comprehensive install and first-run guide, including QMD setup: docs/getting-started.md.

How Remnic compares

Most alternatives trade away at least one of local-first storage, a free license, or multi-host support; Remnic combines all three in one package.

Hosting and price labels mirror the canonical matrix at remnic.ai/compare, which also carries the per-competitor teardowns. Importers for mem0, Supermemory, ChatGPT, Claude, and Gemini: remnic.ai/import.

FAQ

Do I need OpenClaw? No. Remnic runs standalone through @remnic/cli and connects to any tool over MCP or HTTP. OpenClaw simply gets the deepest native integration.

Does it work offline or without an API key? Retrieval works with no provider at all. Extraction needs a model, but you can route it to a local LLM to keep everything on-device.

Where is my data? In markdown files under your configured memory directory. Nothing leaves your machine except during extraction with a remote provider, or when a hosted client reads memories through Remnic's tools.

How much does it cost? The software is MIT and free. Your only cost is your chosen extraction provider, which is zero when you use a local LLM.

Do I need QMD? No, but it gives the best search. Without it, Remnic falls back to embedding search and then recency-ordered reads.

Can multiple agents share one memory? Yes. Every connected tool reads and writes the same store, and namespaces isolate tenants when you want separation.

Is it production-ready? Remnic is extensively tested with CI regression gates and a published benchmark suite. See docs/benchmarks.md for the evidence.

I was using Engram. Everything still works. See Engram to Remnic below for the migration path.