{"version":"2.1.251","anchor":"proxy-failure-records-now-carry-the-connection-target-consis","canonical_anchor":"proxy-failure-records-now-carry-the-connection-target-consis","heading":"Proxy failure records now carry the connection target consistently","tier":"internal","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/proxy-failure-records-now-carry-the-connection-target-consis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Proxy failure records now carry the connection target consistently\n\nProxy failure records now report the connection target consistently across every failure kind.\n\n**What**\n\nWhen a tool call goes through the agent proxy and the connection fails, the target host and port is now stored on the connection when it is opened rather than re-parsed from the request line, so every failure kind reports it the same way.\n\n**Details**\n\n- Affected failure kinds include websocket errors, direct dial failures and blocked peers.\n- These records are what the proxy's status endpoint returns, which the system prompt already points Claude at when a tool call breaks.\n\n**Evidence**\n\n`GET \/__agentproxy\/status on this proxy port shows proxy state and recent failures.`\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}