Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

Plugin file access is confined to the project and blocked from credential folders

Not switched on
Useful3 Signal4
Plugins

Plugin file reads stay inside the project and cannot touch credential folders.

The plugin file capability with swap-detection arrives with the off-by-default hook-module feature.

What

The plugin file capability refuses paths that escape the project root, non-regular files and hard links, and re-checks the opened file against what it saw before opening so a file swapped in mid-check is caught. It arrives with the plugin hook-module feature, off unless the server enables it.

Details
  • Writes additionally refuse the project's config and git directories, plugin and marketplace folders, the session config directory, and home tool folders including .ssh, .aws, .kube, .gnupg, .docker, .npm, .bun, .rustup, .m2, .gradle, and launchd/systemd/autostart locations.
  • Win32 short names and paths reached via relocation variables such as XDG_CONFIG_HOME, ZDOTDIR, BASH_ENV, GIT_CONFIG_GLOBAL, NPM_CONFIG_USERCONFIG and KUBECONFIG are refused too.
  • The refusals themselves are unconditional path checks, with no separate switch.
Evidence

the open landed on a file the check did not see

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

See this entry in the whole of v2.1.242 →