Sandbox credential restrictions no longer lost when settings are…

Sandbox credential restrictions no longer lost when settings are merged

Managed limits on which AWS credentials the sandbox may use survive settings merges now.

You'll noticeTier: how much it should matter to you

3Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

SandboxArea: what it touches

Bug FixesKind: in v2.1.224, 07 Aug 26

Bug FixesSection of the release

What

Restrictions on which AWS credential forms the sandbox may use now survive merging of managed settings into child settings, instead of being dropped at the merge boundary.

Details

Inheritance now carries the sandbox.credentials.sigv4 deny list, whose values are streaming, presigned and sigv4a.
A normalized awsPairs list of allowed AWS key pairs is carried through the same merge.

Evidence

sigv4a

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

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeAdded sandbox credential-masking options: extract and onExtractNoMatch for structured env values, decode: "jwt" with maskClaims for…

See this entry in the whole of v2.1.224 →

The build it came inv2.1.224

7 Aug 2026 · 352 entries, this one is #234.

Use it now44
You'll notice168
Nothing to try yet41
Under the hood99

Either side of it

v2.1.223Older
v2.1.225Newer

Open the release →

Names in this entry

settingsigv4
Managed limits on which AWS credentials the sandbox may use survive settings merges now.
settingstreaming
Managed limits on which AWS credentials the sandbox may use survive settings merges now.
settingpresigned
Managed limits on which AWS credentials the sandbox may use survive settings merges now.
settingsigv4a
Managed limits on which AWS credentials the sandbox may use survive settings merges now.
settingawsPairs
Managed limits on which AWS credentials the sandbox may use survive settings merges now.

Anthropic's note

Upstream's own release notes for v2.1.224 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Added sandbox credential-masking options: extract and onExtractNoMatch for structured env values, decode: "jwt" with maskClaims for JWT-aware masking, and awsPairs/sigv4 for AWS SigV4 re-signing; these need network.tlsTerminate and are honored only from user, managed, or --settings settings

Is this right?