Lumbridge Work
Gated · opens on November 13, 2026Lumbridge Library is one service with two shelves. The docs shelf holds research, notes, wiki pages and dated facts in a Markdown vault kept in git. The warehouse holds mirrored open-source repos, your own code, reusable components and design systems. People use two command-line clients; agents use the same shelves over MCP and get cited answers back.
Tour
The two commands
lumbridge-warehouse lists the indexed repositories. lumbridge-docs turns a name into ranked documents and prints the lines you ask for. Shown in both themes.
01 · What it does
Notes, daily pages, clippings, references and wiki pages live in a git vault. The service pulls it on a timer, re-chunks only files whose hash changed and keeps the embeddings of chunks that did not change. A lint report lists broken links, orphans and duplicate titles.
A fact is an entity, an attribute, a value, a source and who verified it. Each has two timelines: when it was true and when you learned it. Recording the same value again does nothing; a new value supersedes the old one, which keeps its history. You can ask what was true as of a date.
Add any git URL as a bare mirror, or your own repos. Code is cut into whole functions and types with tree-sitter for Rust, Python, TypeScript, JavaScript, Go, C, C++, Bash and Java. Search by meaning, by exact text or regex with git grep, or by symbol name, always at the indexed commit.
A component is a reusable piece in its own git repo: distilled from a mirrored repo with attribution, rebuilt clean-room from a written spec, or original. Distilling is refused when the source is copyleft or its license is unknown. Drafts wait for a person to approve them, and every use in a project is recorded.
The design shelf keeps write-ups, tokens and screenshots of websites and products. Measured tokens become filters such as theme, colors and fonts. A vision model captions each screenshot so text search can find a look, for example a dark console with a mono font.
A query returns context packed under a token budget with numbered citations, plus an id. A person records a verdict on that id, with a correction if it was wrong. Verdicts, frozen eval sets and hashed dataset exports form a ledger you can train and test your own models on.
02 · How it works
A core crate holds the engine. The lumbridge-libraryd service and two thin HTTP clients sit on top of it. Everything in the index can be rebuilt from git except facts, verdicts, evals and usage, which are marked for backup.
One service exposes /health and /metrics without auth, a REST API under /v1 and an MCP endpoint at /mcp, both behind a bearer token. Background loops pull the vault, work through the embedding backlog, fetch mirrors and run the lint. Long work such as mirroring a repo runs as a job you can poll.
Both shelves use the same recipe. A full-text list and a vector list are fused by reciprocal rank, the top results go to a reranker, and the two scores are blended. Vectors carry the id of the model that made them and are never compared across models. On the docs shelf a relevance floor lets a query return nothing.
Agents may write clippings, wiki pages and reference pages. Each write is logged, committed to the vault and re-indexed. Pages a person authored are never edited by an agent. Approving a component or a design needs a separate admin token that agents do not hold. Clipped text is marked as data, not instructions.
An upkeep run that turns structured bullets on reference pages into facts, links orphan clippings, and reports near-duplicates, stale pages and eval scores. It uses a local model, is capped per run, and defaults to a dry run that writes nothing. Contradicting facts are reported, never resolved for you.
03 · Use it
Both clients read LUMBRIDGE_LIBRARY_URL and a token from LUMBRIDGE_LIBRARY_TOKEN or ~/.config/lumbridge-library/token. Every command takes --json. Fetching a URL to clip, recording a verdict and exporting a dataset also need the admin token.
lumbridge-libraryd --config ~/.config/lumbridge-library/lumbridge-libraryd.toml --migrate-only
lumbridge-libraryd --config ~/.config/lumbridge-library/lumbridge-libraryd.toml &
export LUMBRIDGE_LIBRARY_URL=http://library.acme.example:8830
lumbridge-docs status
lumbridge-docs clip https://example.com/queue-design --tag queues
lumbridge-docs ask "how do we retry failed jobs?" --max-tokens 2000
lumbridge-docs fact acme-queue max_retries 5 --source https://example.com/queue-design
lumbridge-docs facts acme-queue --history
lumbridge-docs verdict <qa_id> 1
lumbridge-warehouse mirror https://example.com/acme/queue.git --tag rust
lumbridge-warehouse search retry with backoff --lang rust --limit 5
lumbridge-warehouse symbols 'Scheduler::run'
lumbridge-warehouse grep "max_retries" -r acme/queue
04 · Docs
These pages are in the repository and open with it. Until then, the Guide covers the same ground and is readable now.
The database script, the config file, the token files and the systemd unit for lumbridge-libraryd.
Listen address, library root, embedding and rerank endpoints, the vault remote, job timers and the librarian.
Vault layers, search and ask, reading pages, clippings, wiki writes, facts and the lint report.
Mirrors and own repos, sync, repo cards, semantic search, grep, symbols and reading code at a commit.
Origins, license rules, the approval step, usage records, and adding a design from a capture.
Connecting an agent to /mcp, the resolve-then-query pattern, and what agents may and may not write.
Answer ids and verdicts, retrieval eval sets, and reproducible dataset exports.
Git as source of truth, append-only migrations, vector model ids and license handling.
Read the Guide chapter: Work appsRequest access to the repository
05 · Works with
Not yet
Questions
On your own server. Prose is a Markdown vault in a git repo you host. Code is bare git mirrors on disk. Postgres with a vector extension holds the index, the facts and the ledger. Raw design captures stay on disk and are never committed.
Chunks of text and code go to the embedding and rerank endpoints in your config, and screenshots go to a vision endpoint for captions. The librarian uses a local chat model. All of these are addresses you set; the service calls no outside API by itself. Fetching a URL to clip is the one outbound request.
An agent can save clippings, write wiki and reference pages, record facts, mirror public repos and draft components and designs. It cannot edit pages a person authored, approve a component or design, or start a real librarian run. Every write appears in the activity feed with the client that made it.
A Linux server with Postgres and a vector extension, git, and OpenAI-style embedding and rerank endpoints. The vault needs a git remote, and components are published to a Gitea organization. It listens on one address and is meant for a private network.
Apache-2.0. The repository opens on November 13, 2026. Mirrored repos keep their own licenses, which the warehouse detects and shows, with copyleft sources flagged.
Self-host it, or talk to us about setting it up with you.