Command Code's Ahmad Awais opens up a read tool built for 50 million reads a month

Awais rebuilt Command Code's read_file tool for its v1 release and benchmarked it capability by capability against nine other harnesses, including Claude Code, OpenCode, and Pi. By his own count, Command Code handles roughly 50 million file reads a month; his estimate, which he calls "napkin math," puts wasted context from unneeded content at around 25 billion tokens a month if a read tool has no limits. He describes three stacked size limits, a line window, a byte budget, and a per-line character clamp, each catching a different shape of oversized file that the others miss. A "self-expiring" cache deletes its own cached record the moment it is used, because a stale cache hit pointing at content the model can no longer see is worse than a cache miss. The tool also refuses to let write_file overwrite a file the model has only partially read, a bug class Awais says no per-field input validation could have caught since it lives in the relationship between two tools. The whole piece doubles as marketing for Command Code, positioned by name against Claude Code throughout, and its comparison table and token figures are self-reported and unverified by anyone outside the company.

Why it matters: vendor framing aside, the specific failure modes here, a stale cache pointing at deleted content and a write blocked by an unseen partial read, are the kind of bug that shows up in any harness built around file tools, and are worth checking for in your own.