silica-agent 0.21.0

Let an LLM read, write and organize your Markdown notes, and take back any edit it gets wrong.

Point Silica at a folder of notes, PDFs or code. It answers from what is there, brings new material in,
and checks every write it makes: parsed, validated, read back, and reverted if it does not hold.

_{A real 748-note vault, written in Italian, so the answers are too: a question answered from the notes it found,
then the vault as a graph, one note's reading path, the study queue, and the audit. Recorded with Qwen3.5-9B.}

Install

uv tool install "silica-agent[gui,mcp]"

Needs Python 3.11+ and uv. With pipx: pipx install "silica-agent[gui,mcp]".

Quickstart

cd ~/notes        # any folder of .md files, adopted as it is
silica init       # pick a model: a hosted API key, or a local LM Studio / Ollama model
silica --gui      # opens http://localhost:8765; plain `silica` opens the terminal instead

Then type /report. It is read-only: it writes one file, GRAPH_REPORT.md, and shows the hubs, bridges and orphans already in your vault. Search, the graph and the MCP server work with no model at all.

_{The audit as a tab: what holds the vault together, the areas it sorts itself into, and how its links are spread.}

What you can do

• Turn a library into notes: /nucleate Inbox/ takes a folder, a glob or one file (PDF, DOCX, EPUB, PPTX, notebooks). Each file is its own transaction, checked against what you already have, and lands as the source's own sentences rather than a summary. Stop it whenever; it resumes.

• Ask, and be refused when the answer is not there: /explain, /compare, /summarize and the chat answer from your notes and cite them. What the vault does not hold is refused, not filled in. /web is the explicit way out, with citations from the pages it actually opened.

  
  _{Every claim links to the note it came from; a link with no note behind it says so.}

• Find how two ideas connect: /path "RAG" "Transformers" walks the reading path between two notes over your wikilinks and the concept graph, /relate names the kind of each link, /graph and /map draw it.

  
  _{One note in its reading order: what to read first, and what it unlocks.}

• Test yourself on what you wrote: /learn asks, then corrects you by quoting the source line the note rests on; /quiz re-tests what is fading, scheduled with FSRS-6.

  
  _{Questions waiting from earlier sessions, the ones you missed, and your plans.}

• Take anything back: /undo one note, /revert <run-id> one run, /revert --source paper.pdf everything one document produced, however far it spread.

• Keep code docs honest: launched in a git repository, /wiki writes an ARCHITECTURE.md plus a note per subsystem under docs/silica/, and /stale flags the notes whose code changed shape since.

_{The same vault in 3D, coloured by the 23 areas it sorts itself into. A note's size is how much the vault routes through it.}

How a write is checked

The model never touches a file. It proposes; a parser and a state machine decide.

Benchmarks

Every number comes from a committed result file in evals/, run on the product path.

Small samples, a flash-class judge, 2 of LoCoMo's 10 conversations: not comparable to vendor numbers, but re-runnable on your machine. The unflattering rows ship too: /organize agrees with a human's folders 32% of the time.

Use it from

Over MCP the vault is the folder the client started in, and search, recall and reading need no model or API key.

git clone https://github.com/kiycoh/silica-agent && cd silica-agent
SILICA_VAULT_HOST=~/notes docker compose up -d gui   # http://localhost:8765; your OPENROUTER_API_KEY passes through

License

AGPL-3.0-or-later. A commercial license covers proprietary embedding or a modified hosted service without releasing source. Contributing: CONTRIBUTING.md.