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.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

Cloud sessions withhold local plugins when the plugin store is somewhere the session could edit

You'll notice
Useful3 Signal4
Cloud Sessions

Cloud sessions withhold your local plugins when your settings folder is somewhere the session can write.

What

When a cloud session runs against a folder that also holds your Claude settings, it no longer loads your local plugins, and it tells you which folder is responsible: the one it was launched in, the one it syncs, another folder it may write to, or a location it could not resolve. The plugin choice itself lives in those settings, so a session with write access there could change it, which is why the location decides the outcome. Consent already given to share plugins is re-checked against that location and reset if the store turns out to sit somewhere the session can reach.

Details
  • The plugin store location is classified as in_launch_dir (the folder the session was launched in), in_sync_root (the folder it syncs), in_other_root (another folder it may write to), outside (beyond the session's reach), or unknown when the paths cannot be resolved to real locations.
  • The first four of those classifications, minus outside, each produce their own wording for why plugins were withheld, with unknown used as the fallback when resolution fails.
  • The message offered to the user reads: Your plugins are not used in this cloud session: the folder it syncs contains your Claude settings, where that choice is saved, so the session could change it. Sync a folder that does not hold them.
  • An accepted answer found to be untrusted is set back to unanswered and the caller is notified, so the question is asked again rather than silently honoured.
  • An answer given just now is left alone and not reverted, so a fresh consent survives the check.
  • If two answers race, the consent cache keeps the newer one rather than letting the older write overwrite it.
  • A session that has opted out prints a single notice line when its worker starts, not once per plugin.
Evidence

Your plugins are not used in this cloud session: the folder it syncs contains your Claude settings, where that choice is saved, so the session could change it. Sync a folder that does not hold them., in_sync_root

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.247 →