Plugin
Claude Code Plugin
Use Origin's richest workflow inside Claude Code: setup, session brief, capture, recall, review, distill, read, and handoff.
At a glance
01
The Claude Code plugin is the fastest and richest Origin path because it adds slash commands around the local daemon and MCP connector.
02
/init is the setup and repair command: it verifies daemon reachability, MCP wiring, local memory setup, and a first round trip.
01
Install path
Install through Claude Code's plugin marketplace, restart if Claude Code asks, then run /init.
/init 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/origin
/plugin install origin@7xuanlu
# restart Claude Code if prompted
/init02
What the plugin adds
The plugin adds Claude Code skills and slash commands on top of the same local Origin 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.
03
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 when memory needs review, distillation, deletion, or inline reading.
Plugin commands
/init setup + diagnosis
/help one-screen reference
/brief load session context
/capture save one durable memory
/recall search local memory
/distill synthesize or refresh pages
/read preview a page inline
/review audit pending captures or revisions
/forget delete a memory by ID
/handoff end-of-session debrief
/debrief alias for /handoff04
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 /init when the daemon is down. It does not own installation logic and should not block a session.
05
Local memory mode
By default, /init 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.
06
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 Origin daemon.
Readable artifacts live under ~/.origin, so you can inspect pages, session logs, project status, and installed binaries without opening a separate app.
Local artifacts
~/.origin/pages/ distilled wiki pages
~/.origin/sessions/ session logs
~/.origin/sessions/_status/ current project status
~/.origin/db/ link to daemon store
~/.origin/bin/ installed binaries07
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 /init.
Use the plugin when Claude Code is your main surface. Use MCP-only setup when you want Origin in other clients or when you intentionally want raw MCP tools without the Claude Code workflow layer.
Next
CLI and Service Management
Use the Origin CLI to install the runtime, manage the daemon, inspect status, search memory, and wire MCP clients.
Read next