Claude Code Plugin

August 7, 2026 · View on GitHub

The Claude Code integration ships as @remnic/plugin-claude-code. The package README is the single source of truth for what it does and how to install it:

What the package README covers, in order:

  1. The three discrete manual install steps (none is automated end-to-end today).
  2. What ships in the package (.claude-plugin/plugin.json, hooks/hooks.json, hooks/bin/*.sh, skills/, agents/memory-review.md, .mcp.json, settings.json).
  3. The runtime behavior you get once both a Remnic daemon and the plugin are loaded.
  4. The .mcp.json block you must paste into Claude Code's MCP config yourself.
  5. The agent note explaining why hook/skill/agent files are not auto-published.

Install from the Claude Code marketplace

The repo ships a Claude Code marketplace manifest (.claude-plugin/marketplace.json), so the plugin can be installed with two commands instead of the manual npm install -g + plugin-loader step:

claude plugin marketplace add https://github.com/joshuaswarren/remnic.git
claude plugin install remnic@remnic
# in an already-open Claude Code session, activate it without restarting:
/reload-plugins

The explicit HTTPS URL avoids the SSH-clone default that the bare owner/repo shorthand triggers for users without GitHub SSH keys set up (the marketplace would fail to clone before claude plugin install runs). If you previously added the marketplace under the SSH form, remove it (claude plugin marketplace remove remnic) and re-add with the HTTPS form.

This loads the hooks, skills, and the memory-review agent through Claude Code's own plugin system. claude plugin install registers the plugin but does not activate it inside a session that is already open — run /reload-plugins (or start a new session) so the SessionStart / UserPromptSubmit / PostToolUse hooks are live before you rely on auto-recall / auto-observe. The hooks resolve the daemon bearer token from the Remnic token store (~/.remnic/tokens.json) or the REMNIC_AUTH_TOKEN / OPENCLAW_REMNIC_ACCESS_TOKEN env vars, so auto-recall / auto-observe work against a local daemon out of the box.

The marketplace install registers the MCP server for you. The plugin manifest declares two promptable fields in its userConfig block (#2314):

  • remnic_daemon_token — sensitive; Claude Code routes the value to the OS keychain (macOS) or a protected credentials file (Linux/Windows) rather than persisting it on disk. The single canonical mint command is remnic connectors install claude-code — it (a) registers the claude-code connector in ~/.remnic/connectors/ and (b) mints the bearer token and stores it in ~/.remnic/tokens.json. Paste the emitted token (or copy it from the token-store file) into the Claude Code install prompt.
  • remnic_daemon_url — optional; defaults to http://localhost:4318/mcp. Use a loopback URL or https://; plaintext http:// to a non-loopback host is rejected by the plugin because the bearer token travels with every MCP request.

During claude plugin install Claude Code prompts for the bearer token (and, if you want a non-default URL, the URL). It then launches a small stdio proxy that ships at mcp-server-stdio/server.js inside the plugin tree. The proxy forwards each JSON-RPC request to the URL you provided with Authorization: Bearer <your token> and X-Engram-Client-Id: claude-code, so the remnic MCP server is wired up at install time and there is no placeholder to fill. The hooks/skills still resolve their tokens independently from ~/.remnic/tokens.json / REMNIC_AUTH_TOKEN / OPENCLAW_REMNIC_ACCESS_TOKEN, so they work even if you installed the plugin before the daemon's bearer token exists.

Security — use HTTPS for a remote daemon. The MCP config sends Authorization: Bearer <your token> to whatever url you set. Plain http:// is acceptable only for loopback endpoints (http://localhost:4318/mcp, http://127.0.0.1:…). For any non-loopback / remote daemon the URL must be https:// so the bearer token is never transmitted in cleartext. (If you reach a remote daemon over an already-encrypted overlay such as a VPN/WireGuard tunnel, terminate TLS or keep the daemon bound to loopback on the far side rather than exposing plain HTTP.)

Reality vs. older docs

Earlier versions of this page claimed remnic connectors install claude-code "installs the plugin / configures MCP / runs a health check." That is no longer true:

  • The Claude Code memory-extension publisher in @remnic/core (packages/remnic-core/src/memory-extension/claude-code-publisher.ts) is an intentional all-no-op stub: isHostAvailable() returns false, publish() writes nothing, and all PublisherCapabilities flags are false.
  • remnic connectors install claude-code only writes Remnic-side connector state and mints a bearer token. It does not touch Claude Code's plugin tree or MCP config.
  • Claude Code has no file-based memory extension directory, so there is nothing for the publisher to write to today.

Follow the package README. The legacy docs/guides/claude-code-integration.md and the scripts/hooks/claude-code/ + scripts/hooks/codex/ engram-branded hook trees were deleted in #1527 PR1 (this change) because they described a flow that no longer exists; do not recreate them.

Troubleshooting

The remnic connectors install claude-code step only writes Remnic-side state; the plugin still has to be loaded, and the MCP credential still has to be supplied. How those two happen depends on the install path:

  • Marketplace path (see "Install from the Claude Code marketplace" above): claude plugin install remnic@remnic loads the plugin, Claude Code prompts for the bearer token (and optional daemon URL), and the bundled stdio proxy registers a working remnic MCP server at install time. If the server is missing or rejects your token, see the claude mcp list output and the package README's Troubleshooting section.
  • Manual / npm path (package README): you npm install -g @remnic/plugin-claude-code, load it through Claude Code's plugin loader, and paste the README's .mcp.json block into your MCP config by hand with the bearer token.

Either way the three things to verify are: Remnic-side token + connector state, the MCP config (token present, URL correct), and that the plugin is actually loaded. The package README's Troubleshooting section lists the specific failure modes for each step.

If remnic connectors doctor claude-code reports green but auto-recall/auto-observe do not fire in a Claude Code session, the most common cause is step 3 (plugin load) being skipped — the Remnic-side state is fine, but Claude Code has no hook/skill/agent tree to invoke until the plugin is loaded through Claude Code's own loader.