{"version":"2.1.265","anchor":"tls-to-relay-warning-for-the-agent-proxy-is-now-deduplicated","canonical_anchor":"tls-to-relay-warning-for-the-agent-proxy-is-now-deduplicated","heading":"TLS-to-relay warning for the agent proxy is now deduplicated via a gate check","tier":"internal","area":"Agent Proxy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/tls-to-relay-warning-for-the-agent-proxy-is-now-deduplicated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### TLS-to-relay warning for the agent proxy is now deduplicated via a gate check\n\nTLS-to-relay warning for the agent proxy is now gated to avoid repeated logging\n\n**What**\n\nWhen a client sends TLS traffic directly to the agent proxy's relay port (instead of going through the normal path), Claude Code used to log a warning every single time this happened and also increment a telemetry counter. Now, the warning is only logged when an internal gate check (`agent_proxy_request_tls_to_relay`) returns true, and the separate telemetry increment for this case has been removed.\n\n**Why**\n\nThis reduces noisy, repeated logging for the same underlying condition, controlling whether and how often this particular warning appears.\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}