Stop Letting Your AI Agent Read the entire Repo: Introducing trail-docs

If you've worked with AI coding agents — Claude, GPT, Copilot, whatever — you've seen the pattern: Agent encounters a library it needs to use. Agent reads 15-30 files to "understand" the library. Your context window fills up. Your token bill goes up. Agent still gets the API wrong. I kept hitting this, so I built trail-docs : a CLI that indexes markdown documentation into a searchable, citation-backed knowledge base. It's designed primarily for AI agents. But wait — isn't this just grep? No. And this is the important distinction. grep answers "where is this string?" You get 14 matching lines across 6 files. No structure, no context, no sequence. The agent then opens each file, reads surrounding lines, and tries to synthesize an understanding. trail-docs answers "what do the docs say about this topic?" You get the most relevant documentation sections with extracted code examples and exact file + line citations. The agent can act on the results immediately. # grep: here are some lines th