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 now tell you why

You'll notice
Useful4 Signal1
Sandbox

Blocked network calls in the sandbox now tell you the host, port and reason.

What

When the sandbox blocks an outbound connection, it records a violation naming the host, the port and a reason instead of silently failing. Reasons include sandbox policy unavailable, malformed host, host is on the deny list, host is not on the allow list, user denied, and permission prompt failed.

Details
  • Blocked HTTP requests get their own violation line with the URL query string redacted.
  • A per-domain reason override can be supplied through deniedDomainReasons.
  • Domain rules can now carry a :port suffix, matched against the port of the connection.
Evidence

host is not on the allow list

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 →