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.265 ·

Bash permission check now lets a bare 'cd <safe-subdir>' (plus further safe commands) skip the outside-working-directory block

A bare cd <safe-subdir> followed by other safe commands no longer triggers the outside-working-directory permission check

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaPermissionswhat it touches
KindImprovementsin v2.1.265,
You'll notice

A bare cd <safe-subdir> followed by other safe commands no longer triggers the outside-working-directory permission check

What

When Claude Code checks whether a bash command needs extra permission because it runs outside your working directory, it now recognizes a specific safe pattern: a compound command (several commands chained together) that starts with cd, chdir, or pushd to a plain relative directory name. The directory can't contain wildcards, environment variables, .., or other shell special characters, and it must already be a directory you're allowed to read. Every command chained after it must also be safe and already permitted.

When all of that holds, Claude Code skips the extra "outside working directory" permission prompt entirely.

Why

This cuts down on unnecessary permission prompts for a common, harmless pattern: changing into a subdirectory you already have access to and then running further already-permitted commands there. It only applies on non-Windows systems.

Read from
Names in the bundlecd

See this entry in the whole of v2.1.265 →

Feedback