Plugin

Claude Code Plugin

Use Wenlan's richest workflow inside Claude Code: setup, brief, capture, recall, lint diagnostics, curation, distillation, pages, and handoff.

Qi-Xuan LuUpdated Jul 17, 20266 min read

At a glance

The Claude Code plugin is the fastest and richest Wenlan path because it adds slash commands around the local daemon and MCP connector.

/setup is the setup and repair command: it verifies daemon reachability, MCP wiring, local memory setup, and a first round trip.

Install path

Install through Claude Code's plugin marketplace, restart if Claude Code asks, then run /setup.

/setup is designed to be the single setup check. It installs or verifies the local runtime, configures local memory, checks daemon and MCP reachability, and confirms a memory round trip.

Claude Code

/plugin marketplace add 7xuanlu/claude-plugins
/plugin install wenlan@7xuanlu
# restart Claude Code if prompted
/setup

What the plugin adds

The plugin adds Claude Code skills and slash commands on top of the same local Wenlan daemon that other MCP clients use.

That means Claude Code gets a more ergonomic workflow, while the memory itself remains shared with Codex, Cursor, Claude Desktop, VS Code, Gemini CLI, and other MCP-compatible clients when configured.

Daily command surface

Most sessions need only /brief at the start, /capture when something durable happens, /recall for a specific lookup, and /handoff before the session ends.

The other commands are maintenance and inspection paths for read-only health diagnostics, review, distillation, deletion, or opening a page.

Plugin commands

/setup       setup + diagnosis
/help       one-screen reference
/brief      load session context
/capture    save one durable memory
/recall     search local memory
/distill    synthesize or refresh pages
/pages      list or open distilled pages
/lint       run read-only memory and page health diagnostics
/curate     audit pending captures or revisions
/forget     delete a memory by ID
/handoff    end-of-session debrief

SessionStart hook

The plugin includes a SessionStart hook that probes the local daemon on 127.0.0.1:7878.

The hook is intentionally light: it prints a nudge to run /setup when the daemon is down. It does not own installation logic and should not block a session.

Local memory mode

By default, /setup configures local memory. That means no model download, no API key, and no cloud sync requirement for the basic memory loop.

The daemon stores, embeds, deduplicates, and serves hybrid search. Claude Code skills can still classify captures, write handoffs, and synthesize pages through the agent-side model fallback because the agent already has language judgment in the active session.

Where data appears

The plugin does not store data by itself. It guides Claude Code to use local MCP tools, and those tools talk to the Wenlan daemon.

Readable artifacts live under ~/.wenlan, so you can inspect pages, session logs, project status, and installed binaries without opening a separate app.

Local artifacts

~/.wenlan/pages/               distilled wiki pages
~/.wenlan/sessions/            session logs
~/.wenlan/sessions/_status/    current project status
~/.wenlan/db/                  link to daemon store
~/.wenlan/bin/                 installed binaries

Plugin versus MCP-only

MCP-only setup gives clients tools for context, capture, recall, doctor, and page distillation. It does not install Claude Code slash skills like /brief, /handoff, /distill, or /setup.

Use the plugin when Claude Code is your main surface. Use MCP-only setup when you want Wenlan in other clients or when you intentionally want raw MCP tools without the Claude Code workflow layer.

Connect MCP clients

Wenlan CLI Commands and Service Management

Use the Wenlan CLI to install the runtime, check the daemon, search memory, and connect MCP clients.