builders · review · first seen Oct 31, 09:32 UTC

Anthropic adds Claude Code controls and shared gateway budgets

Claude Code v2.1.316 shipped two configuration controls and two Claude apps gateway controls. Builders should check where defaults and shared limits affect their work before changing settings.

L0 · primary1 source5 claims checked4 min read

What shipped

Claude Code v2.1.316 shipped CLAUDE_CODE_DISABLE_ULTRATHINK. It turns off the ultrathink keyword. This is a targeted control, not a stated change to every effort setting. If your workflow uses that keyword, decide whether it should remain available before setting the new control. The release excerpt does not describe a broader replacement for the keyword or say how existing instructions that mention it will behave. [1]

The same release shipped CLAUDE_CODE_SUBAGENT_EFFORT. It sets the effort level subagents run at when no other setting names one, instead of inheriting the session's effort level. The condition matters: this is a default for an otherwise unspecified subagent, not a claim that it overrides an explicit setting. A team that has relied on session inheritance can now choose a separate default, but should first identify which subagent work has no effort setting of its own. [1]

The Claude apps gateway shipped two administrator controls. The spend limits admin API accepts pooled_budget for one monthly group budget shared by members on top of each member's own limit. It also accepts managed.policy_mode: layered. In that mode, every developer policy that matches applies, with each policy merged over those listed below it, rather than applying only the first match. Separately, fast mode for Opus 4.8 is scheduled for removal on November 30, 2026. After removal, its requests will error instead of falling back to standard Opus 4.8. [1][2][3]

Why it matters if you build

For someone running Claude Code, the decision is about making implicit behavior explicit. Disabling a keyword is useful only if you intend to stop using that keyword; otherwise it could conflict with how you currently direct work. A separate subagent-effort default matters when session-level effort is not the setting you want unspecified subagents to inherit. Neither control, on the supplied evidence, promises a particular result, cost change, or quality change. Treat those as things to check in your own workflow, not as release-note outcomes. [1][2]

For a gateway administrator, pooled_budget adds a group-level monthly boundary without replacing each member's limit. That makes the group and member limits separate decisions. Before adopting it, decide which group should share a budget and whether each member's existing limit still matches your intent. Layered policy mode changes a different boundary: a developer matching multiple policies receives all of them, merged in listing order, rather than only the first match. Review that order before enabling the mode, because the excerpt says policies higher in the list merge over those below. [1][2]

The scheduled fast-mode removal is the clearest deadline in this story. An integration that continues to request fast mode on Opus 4.8 after November 30, 2026 will receive an error, not a silent switch to standard Opus 4.8. That calls for an explicit choice wherever such requests are configured. The excerpt says to migrate to Opus, but it does not give migration steps here. Do not count on fallback as a way to keep those requests working after removal. [1]

How to try it today

1. Check whether your Claude Code workflow uses the ultrathink keyword. If you intend to turn it off, evaluate CLAUDE_CODE_DISABLE_ULTRATHINK.
2. Find subagent work with no effort setting of its own. Decide whether CLAUDE_CODE_SUBAGENT_EFFORT should supply its default instead of session inheritance.
3. Review member limits and the group that would share a monthly budget before setting pooled_budget through the spend limits admin API.
4. List the developer policies that can match together and inspect their order before choosing managed.policy_mode: layered.
5. Locate requests for fast mode on Opus 4.8 and plan to stop making them before the scheduled removal. Do not assume fallback.

What we checked

Every claim below was walked down the source ladder. The rung is how close the source is to the thing itself; the tense is the source's own.

1. shipped L0 · primary

   Claude Code v2.1.316 adds CLAUDE_CODE_DISABLE_ULTRATHINK to turn off the ultrathink keyword.

   per GitHub releases · anthropics/claude-code (L0)
2. shipped L0 · primary

   Claude Code v2.1.316 adds CLAUDE_CODE_SUBAGENT_EFFORT to set subagent effort when no other setting names one.

   per GitHub releases · anthropics/claude-code (L0)
3. shipped L0 · primary

   The Claude apps gateway adds pooled_budget for a monthly group budget shared on top of each member's limit.

   per GitHub releases · anthropics/claude-code (L0)
4. shipped L0 · primary

   The Claude apps gateway adds managed.policy_mode: layered to apply every matching developer policy.

   per GitHub releases · anthropics/claude-code (L0)
5. shipped L0 · primary

   Fast mode for Opus 4.8 is scheduled for removal on November 30, 2026; requests after removal will return an error rather than fall back.

   per GitHub releases · anthropics/claude-code (L0)

What is not confirmed

The supplied excerpt does not establish measured effects on output quality, usage, or spending from either Claude Code control. It gives no budget amount to choose, no example of how a pooled budget interacts with a member limit at exhaustion, and no worked example of a layered-policy merge. Those questions need checking against your own configuration before a broad rollout. It also does not supply a detailed migration procedure for fast-mode requests. [1][2][3][4][5]

Who should act, who should wait

Act now if you administer a gateway with shared group spending or developers who match multiple policies: the controls have shipped, and the limits and policy order warrant review before use. Act now, too, if you make fast-mode requests on Opus 4.8, because removal is scheduled and the stated post-removal behavior is an error. If you use neither the ultrathink keyword nor unspecified subagent effort, you can wait on those Claude Code controls. They are options to evaluate, not evidence that your current workflow needs changing. [1][2][3][4][5]

Sources

• v2.1.316 — GitHub releases · anthropics/claude-code L0 · primary