{"version":"2.1.251","anchor":"bash-output-now-explains-agent-proxy-connection-failures","canonical_anchor":"bash-output-now-explains-agent-proxy-connection-failures","heading":"Bash output now explains agent-proxy connection failures","tier":"notice","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/bash-output-now-explains-agent-proxy-connection-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Bash output now explains agent-proxy connection failures\n\nBash output now explains egress proxy connection failures in plain English with a status URL.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- A per-host tracker snapshots failure counts at the start of the Bash tool's call and diffs them at the end.\n- 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.\n- A telemetry event is also fired when failures are appended.\n\n**Evidence**\n\n`[agent-proxy] While this command ran, ${n} ${C(n, \"connection\")} through the agent proxy failed:`\n\n- Area: Agent Proxy\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}