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.221 Home All releases olderv2.1.220 v2.1.222newer

Sandbox read config is cached and no longer fatal on failure

You'll notice
Useful2 Signal0
Sandbox

Sandbox file-read config is cached and no longer crashes when the native lookup fails.

What

getFsReadConfig memoises its result per config object, and a throw from the native call is logged and recovered from rather than propagated.

Details
  • result is cached keyed on the config object, so repeated calls skip the native work
  • on throw, deny/allow lists are synthesised from the raw filesystem deny lists plus credential file paths
  • the failure is logged rather than surfaced to the caller
Evidence

[sandbox] getFsReadConfig threw; falling back to raw deny lists:

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →