LibrisVault

Knowledge arrives as PDFs, office documents, web articles, images, and videos. Saving them somewhere is easy; what has value is the connected form - pages that link related ideas, cite their sources, and stay findable years later. Doing that by hand does not scale past the first busy week.

LibrisVault automates the whole path, across nearly any input channel: a watched folder, drag-and-drop, or anything sent to its Telegram bot from your phone - PDFs, office documents, blog posts and web links, YouTube videos, screenshots, plain notes. Everything is preprocessed and handed to sandboxed Claude Agent SDK sessions that write linked, cited wiki pages into an Obsidian vault. It all runs on your own machine - the vault stays a plain git repository on disk.

The vault format and its ingest skill are claude-obsidian, an MIT-licensed project by AgriciDaniel, used unmodified. LibrisVault is the service layer around it - automated intake, sandboxed agent runs, a job queue, the dashboard - and it extends what the vault holds through documented extension points rather than by editing it: a registry that binds every page to one field of knowledge from a closed list, and a set of rules carried into every run, from English-only content to page hygiene and entity notability.

A Fastify backend over SQLite with a React dashboard, 81 source files on the server side and 74 on the web side. An ingest is a job in a queue. A job is an agent session. An agent session is a git commit. Nothing else in the design matters as much as that last equivalence: it is what makes every automated change revertible with a tool the user already trusts.

A vault that stays a vault. Plain markdown in a git repository on disk, readable in Obsidian with the service switched off. There is no proprietary store and nothing to migrate out of.

A dashboard for the machine room. Intake, job status with live updates over server-sent events, a browsable library of every page, and research over the web and the vault, each answer citing the pages it came from.

A shape you can see. The whole vault renders as one interactive wikilink graph, laid out by a web worker and drawn on canvas: communities detected and tinted, cross-community bridges drawn with their direction, six lenses over one layout - field of knowledge, page type, authority by inbound links, recency, orphans, stubs. Sources are not a pile. Each one sits beside the concepts and entities it supports, so what a cluster of knowledge actually rests on is visible rather than asserted.

An order that survives growth. Every page carries exactly one field of knowledge from a closed, human-governed set. The library browses along that field, along page type, recency and backlink count. Orphans and stubs are filters rather than surprises. The gaps - links pointing at pages nobody has written yet - are listed rather than quietly dropped. A vault of a thousand pages stays navigable in the same shape as one of fifty.

One command to stand it all up. A setup script installs Node, the sandbox and preprocessing toolchain, the vault and the service, and leaves exactly one step for the browser: connecting an Anthropic account. Windows without WSL gets a PowerShell path that installs it first.

It is a service layer, not a vault format. The vault and its ingest skill are claude-obsidian's, used unmodified. What this project owns is everything that makes them run unattended: intake from three channels, the job queue, the sandboxed runner, the domain governance, ten maintenance jobs, the demo guard, the dashboard.

The sandbox is the boundary, not the callback. The Agent SDK's permission callback was measured to fire zero times, so the guarantee cannot sit there. It sits in the sandbox the runner configures: writes confined to the vault root, no web access in an ingest run, with the web reserved for the research flow. If the sandbox cannot be created, the run fails rather than proceeding. Unsandboxed commands are switched off as well, because the shell tool ships a parameter that would otherwise let a command opt out. Without that one setting the sandbox would be decorative.

What is on this page is what ships today. The next line of work is private for now. In it the library becomes a place with rooms and shelves rather than a filter bar. The agents become named research assistants that work a shift overnight, plan before they act, and leave proposals to be accepted or vetoed in the morning. None of that is described above, because none of it ships yet.

The licence is deliberately not open source. PolyForm Noncommercial: free to self-host, commercial use by arrangement.