
Execution budgets don't just reduce tokens, they reduce unrequested features (847 → 423 tokens)
A couple of days back, I shared Token Sensei, a runtime that gives AI agents a fixed execution budget.
Here's another data point.
Task
Build a Python script that reads a CSV file and prints the average of a numeric column.
Unconstrained Claude
- Named function with a full docstring
- Two example usage blocks
- Interactive `input()` mode
- Warning messages for every skipped row
~50 lines, **847 tokens**
None of those were in the prompt
Token Sensei (budget 200)
40 lines, **423 tokens**- CLI using `sys.argv`
- Proper error handling
- No docstrings
- No examples
- No interactive mode
50.1% fewer output tokens (847 → 423), while still satisfying the requested specification.
I saw the same pattern in three different tasks last week: lower token usage, requirements met, and no unrequested features.
My assessment is that execution budgets don't just shorten outputs. They change what the model wants. With a hard budget, the model spends tokens on the requested task instead of adding features it predicts might be helpful.
Has anyone else observed similar behavior with constrained inference?