Origin for Claude Code: The Daily Memory Loop

Origin's Claude Code path starts with the plugin marketplace: `/plugin marketplace add 7xuanlu/origin`, `/plugin install origin@7xuanlu`, then `/init` after the restart Claude Code requests.

`/init` handles daemon setup, MCP wiring, local memory setup, and a first round-trip check. The goal is not to add another manual note-taking habit. The goal is to make the memory route available at the moment work happens.

`/brief [topic]` loads project status, recent handoffs, preferences, and topic-relevant memories before edits begin.

That makes Claude Code less dependent on the current chat window. The agent walks into the session with the context Origin has already earned.

`/capture` is for durable work knowledge: decisions, lessons, gotchas, project constraints, corrections, and preferences.

A good capture includes why the fact matters. One atomic memory is easier to search, supersede, cite, and distill than a paragraph that mixes five ideas.

`/handoff` writes what changed, what remains open, and what the next agent should know. It also gives Origin better source material than a raw transcript.

When a theme repeats across sessions, `/distill` turns related captures into source-backed wiki pages. Those pages cite source memory IDs and refresh as the work changes.