You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
New FeaturesKind: in v2.1.246,
What probably matters to youSection of the release
What
Changing into a directory Claude Code has not trusted now lists what that folder's .claude/settings.json and .claude/settings.local.json would give it: pre-approved tool permissions, extra accessible directories, hooks that run commands, and helpers that supply auth tokens or request headers. A second variant appears after the move when project grants are held back, ending with a note that they apply only if you trust the directory.
Details
The disclosure is built by reading the target's two settings files; if reading fails the error is logged and the prompt shows less rather than blocking the move.
Wording such as "This directory configures hooks that run commands, declared in" is new in this build.
Evidence
This directory configures hooks that run commands, declared in
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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 sinceAnthropic's documentation has since written up /cd, on Claude Code changelog.* Fixed `/reload-skills` reporting a skill count that disagreed with the slash menu after `/cd`changelogsee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /cd, on Claude Code changelog.
Anthropic's release notes agreeImproved /cd: the new directory's project settings, hooks, .mcp.json servers (behind the usual approval prompt), skills, and agents now take…
