Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

Bash tool's allowed_domains validation moved into validateInput

Bash tool now checks allowed_domains sandbox compatibility earlier, during input validation

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaBash Toolwhat it touches
KindBug Fixesin v2.1.269,
You'll notice

Bash tool now checks allowed_domains sandbox compatibility earlier, during input validation

What

The Bash tool's check that allowed_domains (a setting that restricts network access to specific domains) only applies to commands running in the sandbox now also runs during input validation, before permission checks happen, in addition to the existing check that runs at permission-check time.

Why

This surfaces the same sandbox-compatibility restriction earlier in the command-handling flow, which can catch invalid allowed_domains usage sooner.

Read from
Names in the bundleallowed_domains
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up allowed_domains, on Claude Code changelog. * Added per-command `allowed_domains` to Bash, PowerShell and Monitor in auto mode with sandboxing: the hosts a command needs are reviewed with it and opened for it alone; other hosts are refused changelog see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up allowed_domains, on Claude Code changelog.

See this entry in the whole of v2.1.269 →

Feedback