{"version":"2.1.251","anchor":"agent-proxy-failures-are-summarised-after-a-command-runs","canonical_anchor":"agent-proxy-failures-are-summarised-after-a-command-runs","heading":"Agent proxy failures are summarised after a command runs","tier":"notice","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/agent-proxy-failures-are-summarised-after-a-command-runs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Agent proxy failures are summarised after a command runs\n\nProxy connection failures during a command are summarised afterwards, grouped by host, with a curl pointer.\n\n**What**\n\nIf connections through the agent proxy fail while a command runs, Claude Code now appends a summary of them to the output, grouped by host and failure kind, with a `curl` URL for the full detail. It only appears when a proxy status URL is configured.\n\n**Details**\n\n- Failure kinds distinguished include TLS to the relay, a rejected CONNECT, a tunnel closed mid-exchange, and a blocked or timed-out destination.\n- Also emits a telemetry event `tengu_agent_proxy_failure_note` carrying the failure count and the most recent kind.\n- Silent when no status URL is set, so nothing is appended in setups without a proxy.\n\n**Evidence**\n\n`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"}