Claude Code v2.1.316 adds pooled group budgets and an ultrathink kill switch
π 2026-10-31 β’ ΠΡΡΠΎΡΠ½ΠΈΠΊ GitHub anthropics/claude-code Claude Code v2.1.316 adds pooled group budgets and an ultrathink kill switch Claude Code, the command-line coding agent from Anthropic, released version 2.1.316 at
π
2026-10-31 β’ ΠΡΡΠΎΡΠ½ΠΈΠΊ
GitHub anthropics/claude-code
Claude Code v2.1.316 adds pooled group budgets and an ultrathink kill switch
Claude Code, the command-line coding agent from Anthropic, released version 2.1.316 at approximately 01:00 UTC on October 31, 2026, one day after v2.1.314. The release adds an environment variable named CLAUDE_CODE_DISABLE_ULTRATHINK that disables the ultrathink keyword.
The ultrathink switch
The ultrathink keyword is a prompt-level control that increases the reasoning budget the agent allocates to a task. Some users type it out of habit, and preferences differ, but on a shared team setup a single keyword can quietly change how much compute a routine request consumes. Set CLAUDE_CODE_DISABLE_ULTRATHINK in the shell or in a CI environment and keyword recognition is turned off, so the reasoning level no longer depends on prompt discipline. Until now, controlling this behavior depended on team conventions rather than configuration.
Pooled group budgets
The Claude apps gateway now supports pooled group budgets. A group can be assigned one shared monthly budget, configured through the pooled_budget field in the admin API for spending limits, and the pool operates on top of the individual limits of group members. In practical terms, an administrator can cap what a group spends in aggregate each month, separately from what any single member is allowed to spend.
Why it matters for teams
The two changes point in the same direction β cost and behavior control at the team level. Pooled budgets make aggregate spending visible and bounded per group, while the ultrathink switch prevents an individual keyword from silently raising usage. For organizations running Claude Code across many seats, both narrow the gap between individual defaults and organizational policy.
The one-day interval between v2.1.314 and v2.1.316 is consistent with the project's frequent release cadence. Teams that track versions should consult the release notes for the full changelog. Behavior can change between releases, so checking the notes for the exact tag remains the reliable reference for what a given build supports.
Sources
github.com β https://github.com/anthropics/claude-code/releases/tag/v2.1.316
github.com β https://github.com/anthropics/claude-code/releases/tag/v2.1.314
Continue the conversation: https://t.me/AIAutomationArchitecture Β· Bluesky
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.