Documentation

BNLGit is Blue Note Logic's Git host. It is Gitea ↗ — the whole of it, unmodified in behaviour — plus one addition: a BNLRepo, a source repository paired one-to-one with a generated summary mirror that your AI agents can read, and that never claims to be more current than it actually is.

These pages are the single public source of truth for BNLGit. They are readable without an account, on purpose: you should be able to judge whether this is worth your money before you enter a card.

This documentation covers only what is different about BNLGit. It does not re-document Git or Gitea. Issues, pull requests, Actions, packages, organizations, webhooks, mirrors, the API — all of that works exactly as it does upstream, and Gitea's own documentation ↗ is the right reference for it.

Start here

What BNLGit adds, in one paragraph

Pair a repository and BNLGit creates <repo>-llm beside it — a real Git repository containing a <path>.llm twin for each of your source files. Each twin holds a readable summary and a block of typed, line-anchored facts: symbols, imports, API endpoints, database entities, side effects, security concerns, related files. Every fact points at a line span in a specific blob at a specific commit, and those spans are re-checked against the real file before anything is returned. Your agent asks a question over MCP and gets the summary excerpt plus the backing source lines at the recorded commit, with a link back into the web UI. When your source moves on, the summary is marked stale and down-ranked — never silently presented as current.

Honesty policy

We would rather lose a sale than be caught overstating. So, on these pages:

• Nothing is described as available unless it is in the shipped build. The authoritative answer for any running instance is GET /api/v1/bnlgit/capabilities, which needs no authentication — see Editions and capabilities.
• Where a feature has a real limit, the limit is written down rather than left for you to discover after paying. Search is the clearest example.
• We publish no performance benchmarks, because we have not run ones we would be willing to defend. The argument for BNLGit is a mechanical one, not a leaderboard.

If you find a page here that oversells, that is a bug. Mail docs@bnlgit.com and we will fix it.