If you use Claude Code, Cursor or Obsidian, you already have a folder of markdown. Lore turns it into something you can search, see and trust — without touching a single file.
Read-only by default — it cannot change your files. Free, open source, and runs entirely on your own machine.
Folders
12 pages · scanned just now
It already does the writing. That was never the missing half.
A folder with 1,400 markdown files in it is readable by a machine and unreadable by a person. Lore is the side of that folder built for the human — search that works, a map of what connects to what, and a way to actually open the thing.
Agents rewrite pages between conversations and nothing announces it. Lore watches the folder itself, so it can show you what moved this week, how much prose got deleted, and which agent did it — including the ones that never asked permission.
Something an agent guessed at in April and something you confirmed yesterday sit in the same folder looking identical. Lore keeps the record of which is which, and that record expires by itself when a page gets rewritten.
Use git. Lore is not a replacement for it. But most of what your agents write never reaches a commit — it happens between them, and on a measured vault that was 303 changed pages in a week against two commits. Git records what you remembered to record.
You can commit a note saying you checked a page. Nothing invalidates that note when an agent rewrites the page underneath it. Lore pins your sign-off to the content hash, so a rewrite lapses it automatically — that is the one primitive git does not have.
Because your agents read the wiki through Lore, it sees every search that came back with nothing. That is a list of what to write next, assembled from real demand. No amount of version control produces it.
Put shortly: your agents are the writers. Nothing was the reader.
Read-only is on when you install it. Eight routes in this app can write to a page, and with the lock on every one of them is refused before it runs — so this is a check you can read in the source, not a promise about intent.
First run asks what Lore may do to your wiki; the recommended answer is 'look, don't touch'. It is enforced in one file — proxy.ts — rather than in eight handlers that each have to remember, and it fails closed: a corrupt or missing setting reads as locked.
Lore has no background job, no cleanup pass, and no opinion about what your agent wrote. It reads and it reports. The only things that ever change a file are things you did, in front of you.
There is no queue and no gate. Your agents keep writing exactly as they do now, without asking Lore or you for permission. Review is a record of what happened, not a list you are expected to clear.
Every change your agents make is snapshotted outside your wiki, so the page as it was last Tuesday is still readable. Restoring one is a button you press, never something Lore decides.
That is one vault, seven days, one person's agents doing ordinary work. Not one of those diffs was read by a human, and the wiki has no idea which of them to trust.
changed in seven days
Written by agents, across four folders, while the person who owns the wiki was working on something else.
modified files rewritten in place
Rewritten rather than appended to, so the previous wording is gone unless git happened to catch it.
of prose deleted unreviewed
Removed in the same week, without anyone reading what was removed or why it went.
Nothing is blocked, because nothing local can block it. Everything lands unverified and you promote what you have read.
Every write lands in a journal — Claude Code, Codex, Cursor, a sync script, you in your editor at midnight. Reading the filesystem instead of intercepting a tool call is what makes that possible: no harness has to opt in, so none of them can quietly opt out. What comes back is a ranked list of what changed, how much prose it deleted, and how many pages link to the thing it touched.
A sign-off is pinned to the content hash of the page as you saw it. Rewrite that page and the hash stops matching, the sign-off lapses on its own, and the page comes back to the top of Review wearing the label that says why. Trust that can never lapse is a sticker, not a signal — and it is the reason the ledger sits outside your vault, where an agent cannot edit its own grade.
2 of 12 pages checked by a human
hash 4f9c…c1a2 · 21 pages link here
A sign-off is pinned to the bytes you read.
Your agents read the wiki through Lore. That is a poor place to stand if you want to block a write, and an excellent one if you want to hear the questions. Lore logs which pages actually get opened and every search that came back with nothing. The empty ones are a to-write list assembled out of real demand instead of a planning session.
A search with no hits is a question the wiki could not answer.
You mark a page verified. Everything else follows from the clock and from what your agents do next.
A person confirmed this page against the world, and nothing has touched it since.
Signed off long enough ago that it has earned a second look. Pricing rots faster than tooling does.
It was verified, then an agent rewrote it. The hash moved, so the sign-off came off with it.
Where every page starts, including the ones that read as authoritative because they are well written.
That is the reference vault: 1,424 pages, counted with a real BPE tokenizer rather than characters divided by four. A 200k context window holds about a twelfth of it.
The filled block is everything a model can hold at once.
Nothing will ever read your wiki whole. Every answer an agent gives you is assembled out of the handful of pages a search happened to surface, which is precisely why it matters whether those pages are still true.
Lore measures the same budget folder by folder and page by page, so the corner of the vault that is too heavy to hand to anything is a number you can look at rather than a surprise you hit mid-task.
Seven tools over MCP, or a plain AGENTS.md for agents that only open files. Both point at the same folder, and the watcher covers whatever else you run.
The same local server behind all of them. The desktop build is a window onto 127.0.0.1, not a different product with a different backend.
Apple silicon and Intel. The only platform where the folder picker also works straight from a browser tab.
The desktop build is how you get a native folder picker here — a browser cannot open one.
AppImage or .deb, x64 and arm64. Or skip packaging entirely and run it from source.
Installable as a PWA and pairable with the machine your wiki is on, over your own network.
Nothing to sign up for. The free build has no account step because it has no server behind it — you point it at a folder and it starts reading.
Clone and run it, or build the desktop app. Node 20 and nothing else — no account, no database, no key.
One click drops AGENTS.md into your vault. Every file-reading agent finds it without being told.
Copy the config — the path is already filled in — restart your client, and all seven tools are live.
Open Review, read the page at the top, press the button. That is the first human mark your wiki has ever carried.
Not unless you switch off the lock, and it is on when you install it. Read-only mode refuses every route that could write to a page, at the boundary, before the code runs — it is not a setting Lore promises to honour. Turn it off and Lore can edit, but even then it only writes when you do something: save a page, create one, capture a link. There is no background job, no cleanup pass, and nothing that runs while you are not looking.
Your agents will keep writing. Nobody was recording this part.
Open your wiki