5 posts carrying this tag.
At a conservative 1,000 tokens per source file, 10 million files is roughly 10 billion tokens. A 1 million token window holds 0.01% of that, and a 10 million token window holds 0.1%. Closing that by scaling needs something like a 10,000x increase rather than a 10x one, and quality per token moves against you while you try.
Spec Kit spent a year and gathered well over 100,000 stars teaching several million developers that the specification, not the code, should be the source of truth. That is category creation at a scale no startup could have afforded, and it lands directly on our thesis. It also assumes a blank page, which is true exactly once in the life of a system.
Repomix is the leader in context packing, with 26,000 stars and 255,000 npm downloads a month, and its tree sitter compression genuinely cuts token count by about 70%. Apply that to 10 million files and you go from three orders of magnitude short of the context window to slightly less than three orders of magnitude short. Every tool in this category publishes a token reduction number. None of them publishes a correctness number.
Sourcegraph built the most complete cross repository code search anyone has shipped, and it did so on an assumption that held for fifteen years: a human is asking. Humans supply the meaning the index leaves out. An agent cannot, and at 10 million files a 1 million token window holds 0.01% of the estate, so the gap is not one model generation away.
Agent runtimes got very good very fast. The thing that decides whether a change is correct across your other repositories did not get built at all. On cross repository blast radius, why AI code review misses it, and what a check actually needs.
