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

Blocked-by-proxy responses are detected from a second header

You'll notice
Useful3 Signal2
Internals

Proxy-blocked requests are recognised from a second header, so more networks get the proper message.

What

When a request is refused by a network proxy allowlist, Claude Code now recognises the block from either of two response headers, so more environments get the proper "blocked by egress policy" handling instead of a generic HTTP 403.

Details
  • An HTTP 403 counts as blocked when x-proxy-error is blocked-by-allowlist or when the new x-deny-reason header is host_not_allowed.
  • Previously only the first header was checked, and only at the GitHub comments call site; the check is now a shared helper.
Evidence

host_not_allowed

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