Netlify Adds a Kill Switch for Runaway AI Agent Spend

Netlify now lets Team Owners on Pro plans cap how many AI credits an individual team member can burn through Agent Runners, instead of only setting one limit for the whole team. The change, live in Team Settings under General > AI Enablement as of July 15, 2026, adds a per-member credit ceiling with overrides, including setting a member’s limit to 0 credits to shut off their Agent Runners access entirely (Netlify changelog).

What actually changed

Until now, the only spend control was team-wide: a Team Owner set one credit cap for Agent Runners and AI Gateway combined, and once the whole team hit it, every member’s agent runs stopped (Netlify changelog, March 2026). That protected the bill but did nothing to stop one person from eating the team’s entire allotment before anyone else got to use it.

The new Member Credit Usage Limit sits underneath that team cap. A Team Owner sets a default per-member limit, then overrides it for specific people: a higher ceiling for a power user, a lower one for someone who needs less room, or a hard 0 for someone who shouldn’t be running agents at all. Netlify also reworked the AI inference usage dashboard so owners can see which members are actually driving the spend (Netlify docs).

Why this is the fix, not just a feature

Netlify’s credit system converts $1 of AI model usage into 180 credits, and Agent Runners compute is metered separately from the model calls an agent makes. Model-dependent pricing means one expensive prompt to one expensive model can consume credits at a rate a fixed-price seat never would, and until this update, a team had no way to contain that to one account. Netlify’s own support forum has multiple recent threads from teams whose production deploys got blocked after a single agent run drained a shared balance (Netlify Support Forums). The complaint shows up outside the forums too: a Trustpilot reviewer described an agent that “sucked all of my usage credits in one prompt… and didn’t even generate the changes before disabling my site for one month” (Trustpilot).

That’s the gap this release closes. A per-member cap means one runaway prompt now hits a wall sized for one person’s budget, not the whole team’s.

The trade-off

The new control is opt-in and manual. A Team Owner has to notice the risk, open Team Settings, and set individual limits, there’s no default per-member cap and no automatic alert when one person is about to blow through a disproportionate share. Netlify’s forums also show a separate, ongoing bug pattern this release doesn’t touch: teams reporting a “run out of credits” banner blocking deploys while their dashboard still shows unused credits available, a mismatch several posted about as recently as this month (Netlify Support Forums). Spend controls only help if the balance they’re checking against is accurate.

Our take: per-member limits are the right shape for the problem, agent cost is a per-actor risk and the control should live at that level, not just the team level. But shipping it as an opt-in setting buried in Team Settings puts the burden on the owner to anticipate a failure mode they’ve likely never hit yet. A safer default would cap every new member automatically until an owner explicitly raises it, the same instinct that already governs how Netlify gates other billing-sensitive features.