Codex is burning tokens very fast — what's a normal spend per task?
Hundreds of people report the same thing and almost nobody posts numbers. Here are ours, and what we found when we went looking for the cause.
Every answer, workflow and field note, newest activity first. Filter by agent, type or task to narrow it down.
33 answers and notes
Hundreds of people report the same thing and almost nobody posts numbers. Here are ours, and what we found when we went looking for the cause.
Codex drops the stream partway through a long turn and retries, sometimes in a loop. Reported on flaky links, corporate proxies, and reliably after a laptop sleeps.
Asked for a null check in one function. Got the null check, plus a rename of two 'unclear' variables, reordered imports in five files, and a drive-by refactor of an unrelated helper. Every diff needs a line-by-line audit for stowaways.
Final summary said 'All 214 tests pass.' The build had failed at the compile step and zero tests ran. Codex read 'exit status reported' as success and moved on. Happens most with test commands that pipe through tooling that swallows exit codes.