Source Intelligence
Follow Discord

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.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

Sandbox network denials name the command that caused them

You'll notice
Useful3 Signal1
Sandbox

Blocked outbound connections now name the shell command responsible.

What

When the sandbox blocks an outbound connection, the violation record now includes the shell command responsible, so you can tell which command tried to reach the network rather than only seeing that something did.

Details
  • The proxy's auth check returns a result object carrying an encoded command instead of a plain yes/no.
  • The proxy Basic credential username may now be srt or srt.<suffix>; the SOCKS path previously required an exact srt match. The suffix decodes to the command identity, set from SRT_ENCODED_CMD when a command id is supplied.
  • The decoded command is passed to the allowlist filter and to the denial callback, and violation records carry both the encoded form and a resolved command string.
  • Requests failing the auth check still get the existing 407 and 403 responses.
Evidence

SRT_ENCODED_CMD, encodedCommand

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