Why running a general-purpose agent harness on a large model spent 1,000+ tokens to log a coffee, and how I balance autonomy and strict rules across my stack.
Running a general-purpose agent harness on a large model burned 1,000+ tokens just to log a coffee.
The first version of my personal expense tracker ran inside a general-purpose AI agent harness backed by a large model smart enough to pass a financial analyst exam, even though its entire job was to log "coffee, 120" .
When I first wired the bot up in a messenger, I took the obvious shortcut: I connected incoming messages straight to a full agent harness with tool calling. The problem was not just the size of the model. It was the combination of a heavy model and a broad, general-purpose agent harness.
Because a general-purpose harness is built to handle almost any task, it is not specialized for any single workflow. In practice, it burns roughly the same baseline token overhead on logging a coffee as it does on investigating a DevOps incident.…