Agent memory you can actually read — it lives in your own markdown, not a vendor's database
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: go install github.com/JeremiahM37/grimoire/go/cmd/grimoire@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 记忆增强. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository JeremiahM37/grimoire;first catalogued 2026-10-10;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Memory your agents read. You edit.
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Quickstart ·
Docs ·
MCP tools ·
Benchmarks ·
Releases
Point it at the markdown vault you already have. Your agents read what you know,
remember what they learn back into the same files, and act with credentials they
can use but never see. One self-hosted Go binary, mounted over MCP.
- **Jev-checked memory, now running locally on Laya.** We fine-tuned Laya (421M parameters, runs on CPU) on Jev's judgements. It flags facts that have probably gone stale before an agent relies on them, and on held-out real facts it ties its teacher (AUC 0.92 vs 0.90). Open weights.
- **Memory that fires when it matters.** The right memory is injected with each prompt and again right before a risky command. Rule violations fell from 26 to 11 in 101 cases, and from 10 to 3 in long sessions. When you repeat yourself, Jev spots it and the memory learns that situation.
- **Credentials it can use but never read.** Agents call APIs through Grimoire with scoped, time-boxed grants; the secret never enters their context. Keep secrets in Grimoire's vault or in Bitwarden, 1Password, KeePassXC or HashiCorp Vault.
- **Your notes always win.** Agents propose; they never overwrite what you wrote.
- **It dreams.** Overnight it merges duplicates, fixes broken links, re-checks procedures and sweeps for leaked secrets.
- **An Obsidian-like notes app for you and your agents.** Take your own notes in it, and agents write theirs into the same vault, side by side, with backlinks and a live graph. It works on your phone, and with Obsidian itself via the plugin.
- **One memory for every agent, wired into your stuff.** Claude Code, Codex or any MCP client reads the same vault. It pulls in Google Drive and Docs, Gmail, Calendar, Slack, GitHub, Notion, Jira, Confluence and Outlook, and agents can search them live.
| | |
|---|---|
| **Homebrew** (macOS) | brew install JeremiahM37/tap/grimoire |
| **Windows** (PowerShell) | irm https://raw.githubusercontent.com/JeremiahM37/grimoire/main/install.ps1 \| iex |
| **Scoop** (Windows) | scoop bucket add jeremiahm37 https://github.com/JeremiahM37/scoop-bucket && scoop install grimoire |
| **Debian / Ubuntu**, **Fedora / RHEL** | the .deb / .rpm on the latest release |
| **Docker** | docker run -p 127.0.0.1:9111:9111 -v grimoire-vault:/vault ghcr.io/jeremiahm37/grimoire:latest |
| **Go** | go install github.com/JeremiahM37/grimoire/go/cmd/grimoire@latest (and …/grimoire-mcp@latest) |
Release archives and packages ship static binaries for Linux, macOS and Windows
on amd64 and arm64, verified against checksums.txt, plus console/plugin files.
go install installs the executables only. The shell installer defaults to
~/.local; the native server defaults to localhost. See fresh installs and
remote setup for Docker, tokens, services and upgrades.
To build the console from a source checkout, use Node 24 and the Go version in
go/go.mod:
The console uses React and TypeScript. Its production assets are in
frontend/dist; the server uses that directory when running from the checkout.
Docker and release archives build and include those assets automatically, with
no Node runtime required. Keep the generated worker and hashed assets together
when deploying.
Point your agent at the notes you already have
The runbooks and decisions you have been writing for years already answer many
of your agent's questions. Without a connection to those notes, you keep pasting
the same context into new sessions. Grimoire makes that existing knowledge
available alongside the facts your agents deliberately save.
Grimoire's substrate is a folder of markdown you already own — an **Obsidian**
vault, a Logseq graph, a plain ~/notes. It needs no plugin and does not need
Obsidian running, because it reads the files, not the app. Nothing is copied
or converted; the watcher picks up edits you make in your own editor, and writes
through Grimoire preserve foreign frontmatter byte-for-byte, so whatever notes
app you use keeps working on the same files.
Everything else follows from that one decision.
The dark-mode workspace
Create notes in a dedicated panel, search titles and content, or explain the current note
without changing it. Search results show the line that matched, with the words
you typed marked. Both searches use arrow keys to choose a result, Enter to open
it, and Escape to clear the query.
**Ctrl/⌘ K** (or **O**) opens one box for everything: the notes you had open
last, every note by fuzzy title, and every command, with its shortcut beside it.