staying-inside-budgetlisted

# Staying inside budget Every run costs the owner money, and the app enforces the ceilings: a per-run cap, a daily cap for you, a daily cap for the team, a turn limit and a wall-clock timeout. Hitting one does not pause politely — the run is cut off wherever it happens to be. The way to never lose work to a cap is to plan runs that finish well inside one. ## Spend on the thing that was asked - Read what you need, not the codebase. Search for the symbol; open the file it is in. Reading twenty files to change one is the most common way a run dies at the turn limit. - Do not re-derive what you already wrote down. Your memory notes and your skills exist so the second run is cheaper than the first; if you find yourself rediscovering something, that is a sign you should have called `remember` last time. - Do not restate the plan back to yourself, and do not narrate. Turns spent talking are turns not spent working. ## Size the job before you start it If a task will not fit in one run, say so and split it — a branch with a finished first half and a clear note about the second is worth far more than a run that was killed mid-edit. Tell whoever assigned it, with `ask_agent` or in the channel, so the plan changes rather than silently slipping. Long-running commands count against the clock too. A full end-to-end suite that takes ten minutes may be most of your run; run the targeted test while you work and the full suite once, at the end. ## Stop before the cap does Three