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 ·

Subagents can be locked to a fixed list of Bash commands

Workflow scripts can restrict a spawned agent's shell to a fixed list of allowed commands.

Use it now Notable 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
3Signal: worth watching, 1 to 5
SubagentsArea: what it touches
New FeaturesKind: in v2.1.227,
What probably matters to youSection of the release
What

Workflow scripts can pass agent(prompt, {bashCommandClamp: [...]}), a list of Bash(<command or prefix>) rules that the spawned agent's shell use is restricted to. Any Bash call not matching every clamp group is denied with "bashCommandClamp: no clamp rule matches this command", and a command whose structure cannot be taken apart (command substitution, control flow) is denied as unverifiable.

Details
  • The clamp becomes a permission layer of its own, merged into the tool permission context, on top of the usual allow and deny rules.
  • Malformed or inert clamp entries refuse the spawn outright rather than quietly running the agent unclamped.
  • None of this existed in 2.1.226.
Evidence

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

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