On August 9, 2026, Ahmad Awais shared a deep dive on X about the read tool in Command Code, his coding agent. The claim is big: the read tool saves billions of tokens a month compared to Claude Code. The full post now lives in the Command Code docs.
This article is my summary of that post, written in simple English. If you build agents, or just use them, the lessons are useful.
Coding agents read files all the time. Every edit starts with a read. Every search result becomes a read. A plan step opens three files. Command Code sees about 50 million reads a month.
Each read costs tokens. If one read brings in 500 useless tokens, that is 25 billion useless tokens a month. Worse, those tokens stay in the conversation, and they cost tokens again on every later turn.
That is why coding agents feel expensive. The bill is mostly reads, not clever reasoning.
Think of the read tool as a compiler. It turns your files into the model's context. Every small choice inside it is a token decision, repeated millions of times.
Claude Code's read tool is simple. Ask it to read a 3,000-line file, and it returns all 3,000 lines. Ask for a file with a 3,900-character minified line, and it returns the whole line. No limits at all.
That works for Claude Code because its models are strong enough to ignore the noise. It spends more tokens to succeed.
Command Code runs on open models. Those models cannot handle a messy read. Users also pay for every token. So Command Code had to spend less. That one constraint forced every design decision below.
Command Code compared its read tool with nine other harnesses: Claude Code, OpenCode, Cline, Kilo, Codex, Grok, Hermes, pi, and OpenClaw. Most have the basic limits. Very few have the extras: retrying filenames, clear recovery messages, or blocking dangerous files.
Those extras do not show up in a demo. They matter in hour nine of a long session, when a read fails and the model needs a way back.
One honest note: the page says the benchmark itself was produced by AI with little human review, and the authors expect some errors. The read tool itself was reviewed by a dozen engineers over a full release cycle.
My take: the read tool looks boring, but it is the most important part of an agent harness. This post is the best explanation I have seen of why.
Which tool in your agent's harness would you check first? I would start with the one that returns empty results.