Wire Claude Code

One command, in the project you code in:

npx memcell connect

It prints a code; one tap in your browser approves it. No account needed — an anonymous session holds real memory and carries over if you sign in later.

what it writes hooks in the settings file Claude Code itself gitignores

Connect wires Claude Code through .claude/settings.local.json: hooks on session start, prompt submit, turn end and session end — plus the MCP bridge registration and an agent key for this directory. Nothing lands in files you commit.

see the loop run no cooperation required — the lifecycle carries it

Work a normal session: make a decision, fix something, move on. When the turn ends, the hook hands the session's material to the curator, and what was durable becomes statements. Start a new session and recall arrives before your first prompt is answered.

$ memcell status
machine   linked · this directory → your space
hooks     claude · installed · 4 moments

next session, before the first token:
· recalled 6 statements — 2 pinned, 4 matched

taking it out removal is as clean as install

memcell hook remove takes the hooks out of this directory; memcell agents revoke <id> takes back the key. What was filed stays in your space — wiring is about the machine, memory is about you.

Something look wrong instead? Start from why agents forget — the failure this wiring exists to end.