Plans

Two accounts on Silica hosted. Silica on your computer needs neither and has none of these limits.

Free every feature

All of Silica, up to these limits. A wiki you publish is public, or off.

3 wikis
1,000 notes and 250 MB
A monthly AI allowance to try it on your own notes

Paid for sharing

For a knowledge base you share with the people you choose.

Private wikis, read only by the accounts you name
20 wikis
2,000 notes and 1 GB
15 times the free monthly AI allowance

A reader never pays: a free account receives Private wikis too. Nothing is on sale yet: the hosted pilot has no payments. Create an account with your email and a code.

Ask your notes. Check every answer.

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.

Install Silica

Open source, AGPL-3.0. It runs on your computer, with a provider you have a key for or a local model.

Fig. 1Taf. I

wikis.silica-agent.dev/@kiycoh

Browse every public page

A real page, published with Silica by its author. Each point is one of its notes: point at one to read its title, click it to open the note.

How reliable is it?

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.

Fig. 2Taf. II

Written auto · extracted

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.

Proposed propose · inferred

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.

Asked escalate · ambiguous

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.

Three flints at three densities, smaller as the tier drops: a core with its flakes fitted back on and two rough flints from the Yorkshire Wolds, all from John Evans's Ancient Stone Implements. The three tiers and their rules are the analyst plan in Silica's source (silica/kernel/analyst_plan.py); a move, a delete or a bulk write is never in the first tier.

Fig. 3Taf. III

What do my notes say about Bayes' theorem?

read 5 notes

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(H_i | E) = P(E | H_i) · P(H_i) / P(E)

A note the answer read opens here, beside it, so you can check one against the other.

One answer and the five notes it read, replayed from a recorded session on Silica's test vault. Pick a note to read it beside the answer.

How does it write?

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.

Fig. 4Taf. IV

Illustration. A summary that drops the note's frontmatter fails the structure check after it lands, and the snapshot taken before the write puts the note back. The break is drawn here as noise.

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 line

Measured

Every 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.

Tab. 1. From the result files committed in `evals/`, 2026-10. LoCoMo here is 2 of its 10 conversations; these are not vendor-comparable numbers.
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

Where does it run?

Silica runs on your computer, inside Claude Code and inside Obsidian; a hosted pilot runs it in the browser, with an account that takes your email and a code.

On your computer web app or terminal

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

In Claude Code silica-core plugin

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-core

In Obsidian Silica Bridge

Note 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.

In your browser pilot

Nothing to install: you work in the browser, on the pilot's server. An account takes your email and a code, with no password.

Sign in or create an account

When the places are taken, you join the list.

Hosted pilot in the EU

The pilot runs on one server. Where your notes are kept, what it costs, its license, and what changes after the pilot.

Kept in Turin: Notes, files and chats are stored on a server in the EU, in Turin.
Free: There are no payments. You must be 18 or older.
Open source: AGPL-3.0-or-later. Read the code or run it yourself, from GitHub.
After the pilot: Every model call goes to endpoints that keep no data. In the pilot two still do: image reading and result ordering.

Privacy notice Terms

Bring your own notes

Install Silica, point it at a folder of notes, and ask the first question.

Get it on GitHub

Fig. 5Taf. V

Illustration. Silica's mark, its square and three angles drawn as a grey relief and printed one-bit as it comes into view.