Bash output now explains egress proxy connection failures in plain English with a status URL.
What's wrong with this entry?
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.
- 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.
[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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Agent proxy allowlist narrowed to named Anthropic hosts
Both mention agent proxy
-
v2.1.239
System prompt lists the CLIs already wired up for the agent proxy
Both mention agent proxy
-
v2.1.239
Agent proxy credential placeholders table-driven, PATH search bounded
Both mention agent proxy