Claude Code now has per-person spend caps: full setup and the math
Claude Code now has per-person spend caps with the Claude apps gateway. How to set them up, the math for a team of ten, and what breaks.
Claude Code now has per-person spend caps: with the Claude apps gateway, a service you host between your team's laptops and the model provider, you can set daily, weekly, or monthly limits per organization, per group, or per developer. A runaway coding agent can burn your whole company's AI money, and this is the brake. Here's how to set it up, what else changed, and the math for a team of ten.
What changed this week in Claude Code
The news isn't a single feature. It's consecutive Claude Code versions, 2.1.314 to 2.1.319, between October 30 and November 6, 2026, and nearly all of them push toward team use, with rules and spend caps. There are shared group budgets, a per-developer cost report, long tasks in the background, a setting to deny permissions instead of waiting, and security patches. Before, every laptop was its own island; now there's a control center. It's called the Claude apps gateway, it shipped June 29, 2026, and this week it received nearly everything new.
How it works inside
The gateway runs as a single container with a Postgres database, between the laptops and the model provider: Amazon Bedrock, Google Cloud, or the Claude API. People sign in with the company login (Google, Microsoft Entra, or Okta), with short sessions, so no long-lived key is left on laptops. The key piece: every request passes through it, which is why it can measure each person's spend and cut it off live. It also pushes managed settings from the server and sends usage metrics to a collector of yours.
The full walkthrough: how to set the cap
- Spin up the container with Postgres and, in the gateway.yaml file, name your identity provider.
- On each laptop, put two lines in the managed settings: the forced login method and the gateway address.
- Turn on the admin block: the gateway opens a spend-limits API.
- Set the cap with a single call, for example $500 a month per developer for the whole organization.
- Set a stricter one for a group, for example $100 a day for contractors.
- Each developer types /usage and sees their bar, how much they've used, and when it resets.
Here's where it snags the first time: the amount goes in cents, written as text. Five hundred dollars is written "50000"; if you send "500", you've just set a $5 cap.
The math: the ceiling for a team of ten
A team of ten developers with a $500 monthly cap each has a ceiling of $5,000, no matter what any agent does. With a contractor, using only the monthly cap a runaway agent can burn the $500 in one day. With a $100 daily cap, the most it spends in a day is $100 and reaching the monthly cap takes at least five days. You don't save money by magic: you gain five days to notice. The fair comparison isn't against zero spend, it's against a bill with no ceiling.
Three use cases (our own analysis)
- Software agency with ten developers on Bedrock: create an identity group per client and use the cost report, which returns spend per developer, per day, or per group. The group must be named exactly as in your identity provider.
- Agents working overnight: long MCP tasks move to the background and the deny-instead-of-prompting setting keeps the agent from waking up stuck on a question. What's denied isn't done, so check what's left pending.
- Consultancy with client data: a setting forbids writing outside the project folders in any permission mode, and Agent SDK hooks can block the action if the hook itself fails. It's a policy you write and maintain, not a button.
There's also shared budgets: the group has a monthly pool everyone uses, in addition to each person's limit.
How to apply it in your business?
- Set a monthly cap for the whole organization; $500 per person is a starting point.
- Add a daily cap per group for contractors or new accounts: $100.
- Create an identity group per client or project and use it in the cost report.
- Turn on deny-instead-of-prompting and the block on writes outside the project for agents that run on their own.
- At month end, compare the estimated spend with your cloud bill and adjust the multiplier.
For another guide to controlling agent costs, read the full breakdown of Claude Managed Agents: 300 contracts, cost and budget.
Who it doesn't fit and what you're not being told
It doesn't fit someone coding alone (a gateway with Postgres and an identity provider is more infrastructure than the problem), nor anyone without a company login or anyone to look after a container and a database.
And the caveat: everything the gateway shows is an estimate. The documentation says so: it's a circuit breaker, not an invoice. It calculates from list prices times a multiplier you configure and, if it doesn't recognize the model, applies $5 per million input tokens and $25 output. Compare the spend against your real Bedrock or Google Cloud bill at month end. Also, the announcement publishes no price or plan requirement.
What breaks: if Postgres goes down, the limit fails open by default (nobody has a cap), and you change that with fail_closed_on_error. Layered policies can end up looser than any single one, and groups are re-read on each session renewal, so removing someone takes a while. When the cap is exceeded the gateway returns a 429 error, but Claude Code warns at 75% and 95%. And update: 2.1.319 fixes a Bash permissions bypass and a sandbox escape.
Frequently asked questions
What is the Claude apps gateway?
A service you host between your team's laptops and the model provider, to control login, settings, and spend caps.
How do you write the cap amount?
In cents, as text: $500 is "50000".
What happens if someone exceeds the cap?
The gateway returns a 429 error and blocks until the period resets or an admin raises the limit.
Is the spend it shows exact?
No: it's an estimate; compare it against your cloud bill.
Conclusion
What changed this week isn't that Claude Code codes better, but that it can now be managed, with rules and per-person spend caps. The question is who on your team owns that cap. Set a monthly cap, a daily one for contractors, and check the estimated spend against your bill.