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.246 Home All releases olderv2.1.245 v2.1.247newer
Claude Code v2.1.246

Artifact uploads report a refused proxy distinctly

You'll notice
Useful2 Signal1
Artifacts

Artifact uploads blocked by a network proxy now say so and confirm nothing was sent.

What

An artifact store request that fails because a network proxy rejected the connection now reports that specific cause and states that nothing was sent, rather than a generic request error. Relay requests through the artifact gateway also record whether the request went through a tunnel.

Details
  • The failure reason is proxy_refused; the tunnel marker is added alongside the existing runner marker on artifact frame relay events.
  • Both apply unconditionally on the artifact upload and store path.
Evidence

a network proxy refused the connection; nothing was sent

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