Updated
trovex for open-source maintainers
Contributors' coding agents read your CONTRIBUTING, architecture, and setup docs to make a change, and they often read a stale copy. trovex serves the one current doc per query with a freshness marker, so a contributor's agent works from the canonical answer instead of last year's wiki. Local-first, open source, about 60% fewer tokens per lookup.
The problem for a maintainer
A drive-by contributor points an agent at your repo, and the agent reads whichever doc looks relevant, often an outdated one. You get PRs built on stale conventions, and you answer the same setup questions over and over because the agent could not tell which doc was current.
One current answer per query
trovex indexes your markdown and returns the one canonical doc for a question, marking stale and duplicate copies so they are skipped. A contributor points an agent at it and the agent reads the current CONTRIBUTING and architecture notes, not a fork of them. It runs locally with an on-device embedder, so nothing leaves the contributor's machine.
How it rolls out
Recommend it in your CONTRIBUTING as the setup step: a one-line install, no account, works with any MCP client. Contributors opt in locally, and their agents start from your current docs.
When docs hygiene is the real bottleneck
trovex makes the current doc easy to find; keeping a large project's docs and agent workflows healthy is a bigger job. The tool is open source you can adopt today; if making agents reliable across a project is the hard part, tsukumo consults, and trovex is the proof.
FAQ
How does this help contributors?
Their agent reads the one current doc for a question with a freshness marker, instead of guessing among stale copies, so changes start from your actual conventions and you field fewer repeat questions.
Does a contributor need an account?
No. trovex is a local-first MCP server with a one-line install; no SaaS, no sign-up, and the repo's docs stay on the contributor's machine.
Will it send my repo to a cloud?
No. Indexing and embeddings run locally, vectors in SQLite, no cloud or API keys, so nothing leaves the machine it runs on.
Keep contributors' agents on your current docs.
Recommend it in CONTRIBUTING. One-line install, no account, local-first. About a minute to set up.
uv tool install trovex
Open source. No cloud, no API keys. Your docs never leave your machine.