remnic MCP工具

Quick install (OpenClaw)

If you have OpenClaw installed, the fastest path to working Remnic memory is:

```bash

1. Install the plugin package

openclaw plugins install clawhub:@remnic/plugin-openclaw

Installation

Option 1: Install from the CLI

openclaw plugins install clawhub:@remnic/plugin-openclaw

Option 2: Ask your OpenClaw agent to install it

Tell any OpenClaw agent:

Install the @remnic/plugin-openclaw plugin and configure it as my memory system.

Your agent will run the install command, update openclaw.json, and restart the gateway for you.

Option 3: Developer install from source

git clone https://github.com/joshuaswarren/remnic.git \
  ~/.openclaw/extensions/remnic
cd ~/.openclaw/extensions/remnic
pnpm install && pnpm run build

Note: This repo uses pnpm workspaces. npm ci / npm install will fail on workspace: specifiers. Install pnpm first: npm install -g pnpm.

Verify installation

remnic doctor              # Health diagnostics with remediation hints
remnic connectors doctor   # Connector-specific health checks
remnic status              # Daemon status and local endpoint summary

Setup & diagnostics

openclaw engram setup # Guided first-run setup openclaw engram doctor # Health diagnostics with remediation hints openclaw engram config-review # Config tuning recommendations openclaw engram stats # Memory counts, search status openclaw engram inventory # Full storage and namespace inventory

Standalone Usage

Remnic also works as a standalone tool without OpenClaw. Install and run the CLI directly:

npm install -g @remnic/cli
remnic init                     # create remnic.config.json
export OPENAI_API_KEY=sk-...
export REMNIC_AUTH_TOKEN=$(openssl rand -hex 32)
remnic daemon start             # start background server
remnic query "hello"            # verify

The CLI provides 15+ commands for querying, onboarding projects, curating files, managing spaces, running benchmarks, and more. See the full CLI reference for all commands.

Trust-zone demos

openclaw engram trust-zone-demo-seed --dry-run # Preview the opt-in buyer demo dataset openclaw engram trust-zone-demo-seed --scenario agentic-commerce-v1 --dry-run openclaw engram trust-zone-demo-seed # Explicitly seed the demo dataset openclaw engram trust-zone-promote --record-id <id> --target-zone working --reason "Operator review" ```

Option 4: Standalone (no OpenClaw)

From npm (recommended):

npm install -g @remnic/cli      # Installs `remnic` plus the legacy `engram` forwarder
remnic init                     # Create remnic.config.json
export OPENAI_API_KEY=sk-...
export REMNIC_AUTH_TOKEN=$(openssl rand -hex 32)
remnic daemon start             # Start background server
remnic status                   # Verify it's running
remnic query "hello" --explain  # Test query with tier breakdown

From source (requires Node.js 22.12+ and pnpm):

git clone https://github.com/joshuaswarren/remnic.git
cd remnic
pnpm install && pnpm run build
cd packages/remnic-cli && pnpm link --global  # Makes `remnic` and `engram` available on PATH
cd ../..
remnic init                     # Create remnic.config.json
export OPENAI_API_KEY=sk-...
export REMNIC_AUTH_TOKEN=$(openssl rand -hex 32)
remnic daemon start             # Start background server
remnic status                   # Verify it's running
remnic query "hello" --explain  # Test query with tier breakdown

Note: remnic is the canonical CLI. The legacy engram binary is a compatibility forwarder to the same implementation. Running pnpm link --global from packages/remnic-cli/ (not the repo root) makes both names available on PATH. Alternatively, invoke directly: npx tsx packages/remnic-cli/src/index.ts <command>.

The standalone CLI provides 15+ commands for memory management, project onboarding, curation, diff-aware sync, dedup, connectors, spaces, and benchmarks -- all without requiring OpenClaw. See the Platform Migration Guide for the full command reference.

Option 5: Connect Other AI Agents

Once the Remnic daemon is running, connect any supported agent:

remnic connectors install claude-code   # Claude Code (hooks + MCP)
remnic connectors install codex-cli     # Codex CLI (hooks + MCP + memory extension)
remnic connectors install pi            # Pi Coding Agent (extension + MCP + compaction)
remnic connectors install replit        # Replit (MCP only)
pip install --upgrade remnic-hermes     # Hermes Agent (Python MemoryProvider)
remnic connectors install hermes        # Writes Hermes config + token

For Codex CLI, installation also drops a phase-2 memory extension at <codex_home>/memories_extensions/remnic/instructions.md so Codex's consolidation sub-agent auto-discovers Remnic. Opt out with --config installExtension=false if you prefer to manage Codex extensions yourself.

For Pi Coding Agent, installation writes an auto-discovered extension under ~/.pi/agent/extensions/remnic/. The extension recalls context before turns, observes Pi messages and tool activity into Remnic/LCM, exposes Remnic MCP tools as Pi tools, and coordinates session_before_compact with Remnic LCM flush/checkpoint recording. See docs/integration/pi.md.

Each connector generates a unique auth token, installs the appropriate plugin/hooks, and verifies the connection. All agents share the same memory store — tell one agent your preference, and every agent remembers it.

Hermes uses Remnic as a Hermes MemoryProvider, not a context_engine. Automatic recall runs in pre_llm_call, observations run after each turn, and the provider now registers the full Remnic parity tool surface (remnic_lcm_search, recall explain/X-ray, memory CRUD, continuity, identity, governance, work-board, shared-context, compounding, day-summary, briefing, checkpoint, and profiling tools) plus legacy engram_* aliases. Lossless Context Management is delivered through the daemon recall envelope when lcmEnabled is on; no Hermes context_engine registration is required. See docs/plugins/hermes.md for the full reference.

Configure

After installation, add the Remnic bridge plugin to your openclaw.json:

{
  "plugins": {
    "allow": ["openclaw-remnic"],
    "slots": { "memory": "openclaw-remnic" },
    "entries": {
      "openclaw-remnic": {
        "enabled": true,
        "hooks": {
          "allowConversationAccess": true
        },
        "config": {
          // Recommended for OpenClaw: use the gateway model chain.
          "modelSource": "gateway",
          "gatewayAgentId": "remnic-llm",
          "fastGatewayAgentId": "remnic-llm-fast",

          // Optional: Use Remnic's local LLM path (plugin mode only; no API key needed):
          // "openaiApiKey": false,
          // "localLlmEnabled": true,
          // "localLlmUrl": "http://localhost:1234/v1",
          // "localLlmModel": "qwen2.5-32b-instruct"

          // Optional: Use OpenAI directly (plugin mode only):
          // "modelSource": "plugin",
          // "openaiApiKey": "${OPENAI_API_KEY}"
        }
      }
    }
  }
}

Gateway model source: When modelSource is "gateway", Remnic routes all LLM calls (extraction, consolidation, reranking) through an OpenClaw agent persona's model chain instead of its own config. Extraction starts on the gatewayAgentId chain directly in this mode; localLlm* settings do not control primary extraction order. Define agent personas in openclaw.json → agents.list[] with a primary model and fallbacks[] array — Remnic tries each in order until one succeeds. This lets you build multi-provider fallback chains like Fireworks → local LLM → cloud OpenAI. See the Gateway Model Source guide for full setup.

Restart the gateway:

```bash launchctl kickstart -k gui/$(id -u)/ai.openclaw.gateway # macOS

ChatGPT (OpenAI data export: saved memories + optional conversation summaries)

npm install -g @remnic/import-chatgpt remnic import --adapter chatgpt --file ~/chatgpt-export/memory.json --dry-run

Then (after enabling sources in config):

remnic wearables sync --days 7 remnic wearables transcript --date 2026-06-10 remnic wearables search "that solar quote" remnic wearables memories --source limitless --date 2026-06-10 ```

Memory creation defaults to smart mode — a fully automated trust pipeline: every candidate runs through Remnic's LLM extraction judge, gets a per-source transcription-quality prior, and earns corroboration boosts when a second wearable recorded the same content or an existing memory supports it. High-trust facts are written active, borderline facts go to the review queue, ASR garbage is dropped — and the trust evidence (score, judge verdict, corroborating sources) persists on every memory. Tune per source with sourceTrust, autoApproveTrust, reviewTrust, and maxMemoriesPerDay, or pick review/auto/off. MCP tools (remnic.transcript_day, remnic.transcript_search, remnic.transcript_memories, remnic.wearables_sync, remnic.wearables_status — engram.* aliases included) and HTTP routes expose the same surface to agents.

See docs/wearables.md for the full pipeline, configuration reference, speaker labeling, corrections, redaction, and per-provider setup.

mem0 (REST API — paginated; honors --rate-limit)

npm install -g @remnic/import-mem0 export MEM0_API_KEY=... remnic import --adapter mem0 --rate-limit 2

HTTP API

remnic daemon start

Key endpoints: GET /engram/v1/health, POST /engram/v1/recall, POST /engram/v1/memories, GET /engram/v1/entities/:name, and more. Full reference in API docs.

The HTTP server also hosts a lightweight operator UI at http://127.0.0.1:4318/engram/ui/ for memory browsing, recall inspection, governance review, trust-zone promotion, and entity exploration.

CLI Reference

```bash

Omi necklace (integration app: appId + uid + sk_ key)

npm install -g @remnic/connector-omi export OMI_API_KEY=...

Package Architecture

@remnic/core            — Framework-agnostic engine (re-exports orchestrator, config, storage, search, extraction, graph, trust zones)
@remnic/cli             — Standalone CLI binary (15+ commands)
@remnic/server          — Standalone HTTP/MCP server
@remnic/bench           — Benchmarks + CI regression gates
@remnic/hermes-provider — HTTP client for remote Remnic instances

Integrations & Extensions

• Codex Marketplace — Install Remnic via codex marketplace add joshuaswarren/remnic. Marketplace manifest at repo root. (issue #418)
• Memory Extension Publisher Contract — Pluggable contract for installing host-specific instruction files into any AI agent host's extension directory. Generalizes the pattern previously hard-coded for Codex. (issue #381)
• Memory Extension Discovery — Third-party memory extensions provide structured instructions that influence consolidation, auto-discovered from extension directories. (issue #382)

Trust-zone demo workflow

Trust zones now ship with a dedicated admin-console view plus an explicit demo seeding path for buyer-facing walkthroughs.

• Never automatic — Remnic does not seed sample trust-zone records on install, startup, or feature enablement.
• Explicit only — demo records appear only after you run openclaw engram trust-zone-demo-seed or trigger the matching admin-console action.
• Buyer-friendly story — the trust-zone view surfaces provenance strength, promotion readiness, corroboration requirements, and operator promotion actions in one place.

The default scenario is enterprise-buyer-v1, which creates a small, opinionated dataset covering:

• quarantine records that are ready for review
• working records that are blocked on missing provenance
• working records that still need corroboration
• work

Troubleshooting: hooks aren't firing

Symptom: Remnic appears installed but no memories are created. The gateway log shows no [remnic] lines after conversations.

Root cause: OpenClaw gates memory plugins on plugins.slots.memory. If this slot is not set to the plugin's id, OpenClaw skips register(api) entirely — no hooks fire, no memory is stored or recalled.