Your agent solved yesterday but hit ECONNREFUSED 5432 today, rewriting a file that was fine. It wakes with amnesia. The usual pitch is a platform you adopt, but this is a single command and a folder you own—plain files on your disk, no account, no network.

Two minutes to memory. One command scaffolds the lorekit‑memory, lorekit‑setup and lorekit‑groom skills, an MCP server entry, and the lifecycle hooks into your .claude/ or ~/.claude/:

```

npx @lorekit/cli install

```

It asks three things: project or global, a token, and which hooks to wire. Leave the token blank and take all hooks. Two small files finish the job: a .lorekit.json at repo root (safe to commit) and an edited .mcp.json pointing the MCP server at your own machine.

When tests fail, the Post Tool Use Failure hook writes a note to your local file:

```

~/.lorekit/repo/acme/checkout/tests-need-local-postgres.md

```

The note is not a DB row, it's a file. Commit or remove it, and the next session starts already knowing the lesson.

You can switch to remote by creating a free account at lorekit.io, generating a key, and re‑running the installer. The CLI migrates your local notes, and you see both stores side by side. No service sits in the middle; everything lives on your disk or the hosted store.