Silica answers from the notes and PDFs you give it, names the note behind every answer, and takes back any write that does not hold.
Open source, AGPL-3.0. It runs on your computer, with a provider you have a key for or a local model.
Before Silica changes a note it sorts the change by how much the vault already agrees with it: the less agreement, the less ink it puts down on its own. Every answer names the notes it read.
Reversible, and the structure of the vault already says yes. Silica writes it and logs it.
An orphan note whose title another note already uses gets its link.
Reversible, but only one signal says yes. You see it first and confirm before it lands.
Two notes that share a concept and are not linked yet.
Irreversible, or a call only you can make. Nothing is written: you get the choices.
A link to a note that does not exist, seen twice: create the note, rename one, or leave it.
silica/kernel/analyst_plan.py); a move, a delete or a bulk write is never in the first tier.What do my notes say about Bayes' theorem?
presents the theorem as a way to calculate the probability that an event is the cause of an event that has already occurred. It is described as a "posterior search for causes."
P(Hi | E) = P(E | Hi) · P(Hi) / P(E)
Every note a run writes passes parse, structure and link checks, and is read back after it lands. One that fails is sent back. The note stays as it was.
Silica keeps a journal of what it wrote and where it came from, so a write can be taken back after the fact as well, however far it spread.
/undothe last write, one note/revert <run-id>everything one run wrote/revert --source <file>every note made from one PDF/changeswhat this session touched, line by lineEvery number comes from the harness in the repository, run on the product path. The samples are small and they are re-runnable on your machine.
| What was measured | Result | Sample |
|---|---|---|
| Questions the notes can answer, answered right (LoCoMo) | 82.1% · 83.2% | 152 and 150 questions |
| Questions it should refuse, refused (LoCoMo) | 87.2% · 82.1% | 47 and 40 questions |
| Keeping the source's words instead of summarizing them | +16.5 · +14.7 pts | 302 questions, same pipeline |
| Facts in written notes the source supports (FActScore, extractive path) | 0.961 | 237-note vault |
| Notes where no write introduced a structural break | 100% | 796 of 796 notes |
| Wikilinks stripped from a real vault, found again | 72.3% | 1,384 links, 442 notes |
| Agreement between /organize and the folders a person chose | 0.32 | the same vault |
Silica runs on your computer, inside Claude Code and inside Obsidian; a hosted pilot runs it in the browser for people invited one by one.
Point it at any folder of Markdown files, adopted as it is. silica init asks where the model runs: a provider you have a key for, or a local model.
$ uv tool install "silica-agent[gui,mcp]" $ cd ~/path/to/your/notes $ silica init $ silica --gui
Indexes the folder Claude Code starts in. Claude searches it before it answers and cites what it used by file and line.
$ claude plugin install silica-core \
--marketplace kiycoh/silica-coreNote panel, ranked search, autolinking and the community graph need no model and no network. The chat panel talks to Silica on your computer, and every write lands in a changes list with a diff per file.
Install from the latest release, then run silica connect in the vault.
Nothing to install: you work in the browser, on the pilot's server. All seats are taken.
To ask for one, write to kiycoh@proton.me with what you would use it for. Already invited? Open Silica.
The pilot runs on one server. Where your notes are kept, what it costs, its license, and what changes after the pilot.
Install Silica, point it at a folder of notes, and ask the first question.
Get it on GitHub