Claude Code v2.1.232 · 13 Aug 2026
Built-in agent selection is now a single three-way decision
One resolver now picks no agents, coordinator or default, and the disable env var works as before.
Use it now
No documentation found Internal Changes
Copy link
Copy markdown
JSON
All of v2.1.232
Use it now Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Subagents Area: what it touches
Internal Changes Kind: in v2.1.232, 13 Aug 26
What probably matters to you Section of the release
What
Two separate checks were folded into one resolver returning "none" when CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS
Evidence
CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.232 →
13 Aug 2026 · 405 entries, this one is #77.
43 209 41 112
Open the release →
Names in this entry
env CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS Set to 1 to disable all built-in subagent types such as Explore and Plan. Only applies in non-interactive mode (the -p flag). Useful for SDK users who want a blank slate. This also removes general-purpose, the subagent Claude Code runs when an Agent tool call omits subagent_type. Such a call then fails with subagent_type is required
Is this right?
0 0 Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 76 of 405
Storage layout reserves a place for per-day session logs
Nothing to try yet Internals
In v2.1.232 What probably matters to you release-page order
Next → · 78 of 405
Gateway sign-in config uses inferenceCredentialKind
Use it now Managed Settings
