IT ATE5,000CREDITS.

One ambitious Agent Runner session munched through more than 5,000 credits—with no deployment to show for it. This is a builder's cautionary tale, not a swipe at Netlify. Somewhere in the logs, something green still burped.

Know your monster before it knows your balance

CREDITS REMAINING5,000

EXHIBIT A / ACTUAL RUN

The receipt has teeth.

This screenshot is the real punchline: an 85-minute Agent Runner session used 5,221 credits and stopped at the credit limit.

For the record: Netlify is the workshop, not the villain. The lesson is to scope agent tasks, review progress, and keep an eye on usage before a run becomes an all-you-can-eat buffet.

Netlify Agent Runner screenshot showing a Claude Agent run that took 85 minutes 49 seconds, used 5,221 credits, and reached the credit limit. — 85m 49s · 5,221 credits · credit limit reached · no successful deployment

FIELD GUIDE / VOL. 01

It sneaks up
from time to time.

Usually right after you type
“one more small thing...”

The prompt grows legs

“Quick tweak” becomes twelve pages of context, six tools, and a philosophical debate about button radius.

The runner keeps chewing

You hear the tiny whirr of tokens becoming tasks becoming more tokens. The deploy remains imaginary.

Your balance looks bitten

You refresh the usage page. A suspicious green tuft disappears behind the billing chart.

SURVIVAL TIP

Keep prompts
snack-size.

Break the epic into chapters. Check in between runs. Keep one eye on usage and the other on that rustling shrub.

01 Define one clear outcome DONE

02 Run the smallest useful task DONE

03 Review before continuing SAFE