Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.251 ·

Bash output now explains agent-proxy connection failures

Bash output now explains egress proxy connection failures in plain English with a status URL.

You'll notice New Features
JSON All of v2.1.251
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Agent ProxyArea: what it touches
New FeaturesKind: in v2.1.251,
New FeaturesSection of the release
What

When a Bash command runs while the hosted egress proxy is active, any proxy connection failures during that command are now summarized on stderr afterwards, naming the host, the failure kind and a plain-English reason, plus a curl -sS <statusUrl> pointer for details. Only failures that happened during that command are reported.

Details
  • A per-host tracker snapshots failure counts at the start of the Bash tool's call and diffs them at the end.
  • Requires the agent proxy relay to be active for the session, which is what sets the status URL; with no relay there is nothing to report.
  • A telemetry event is also fired when failures are appended.
Evidence

[agent-proxy] While this command ran, ${n} ${C(n, "connection")} through the agent proxy failed:

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

Feedback