Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.227 ·

Spawned agents can be clamped to a fixed set of shell commands

Spawning an agent with a bad command clamp list now fails immediately instead of running unclamped.

Use it now No documentation found New Features
JSON All of v2.1.227
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SubagentsArea: what it touches
New FeaturesKind: in v2.1.227,
What probably matters to youSection of the release
What

The agent() spawn API gained a bashCommandClamp option: a list of Bash(...) permission rules that limits which shell commands the spawned agent may run. It is checked strictly at spawn time, so a malformed list, an entry that does not parse as a Bash rule, or one with empty or space-padded contents aborts the spawn instead of quietly running the agent with no clamp.

Details
  • Entries take the form Bash(<command or prefix>), matching the usual permission rule syntax.
  • Rejection message when the option is not a list of non-empty strings: agent() opts.bashCommandClamp must be an array of non-empty strings; got .
  • The option is now part of the serialized list of spawn options, alongside disallowedTools.
Usage
agent("audit the build", { bashCommandClamp: ["Bash(npm test)", "Bash(git log:*)"] })
Evidence

agent() opts.bashCommandClamp must be an array of non-empty strings; got

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundlebashCommandClamp

See this entry in the whole of v2.1.227 →

Feedback