Category: lean-coder

Sub-agents are a scalpel, not a speed knob. Here’s what we learned making them work, and the ways they quietly fail. A “worker” (or sub-agent) is a scoped assistant your main agent, the driver , dispatches to do a self-contained errand: scout a module, run a test suite, make a bounded edit, summarize a directory.…

On subscription plans the meter that throttles you counts tokens you thought were free. Here’s the trap, and the only lever that actually works. Prompt caching is one of the great wins of the modern LLM API: re-send the same prefix and the provider charges you a fraction, often a tenth, for the cached part.…

“Just parallelize the agents” is a trap when they share a GPU. Measure before you believe it. lean-coder can dispatch multiple workers, sub-agents that each take a task and run headless. The obvious next thought is: run them at the same time, get the work done faster. We tested that assumption. It was wrong in…