lockdocsThe docs for the version you actually installed.

Exact-version library docs from your lockfile — local, offline, no rate limits.

🔒

Exact version, zero config

Reads package-lock, pnpm, yarn, bun, Cargo.lock, uv, poetry, Pipfile, requirements and go.mod. No library IDs, no version hints in the prompt.

📦

Docs that ship with the code

READMEs, changelogs and docs folders, plus API reference from .d.ts + JSDoc, Python docstrings, rustdoc and Go doc comments. Private packages included.

✈️

Offline and unlimited

Everything comes from node_modules, your virtualenv, the Cargo registry and the Go module cache. Offline after a one-time model download; keyword-only needs no network. No account, no rate limit.

🎯

Small, cited answers

Hybrid search (BM25 + a small local embedding model) over symbols and sections, packed into a 1,200-token budget by default, every section cited as package@version path:line.

🏷️

Upstream docs at the exact tag

Next.js, Django or FastAPI ship no docs? `lockdocs fetch` pulls their docs folders from GitHub at your version's git tag, once.

🧰

Three obvious tools

resolve (which versions), docs (a question, optionally scoped to a package), api (the exact signature of z.object or tokio::spawn).

⚡

Rust, cached per version

Each package version is indexed once, in a fraction of a second, then cached. Warm queries take tens of milliseconds.

lockdocs demo: the same question about zod gets .strict() in a zod 3 project and z.strictObject() in a zod 4 project

One question, two projects: zod 3 gets .strict(), zod 4 gets z.strictObject(), each cited to the installed file and line.