{"version":"2.1.178","anchor":"agent-proxy-replaces-egress-gateway","canonical_anchor":"agent-proxy-replaces-egress-gateway","heading":"agent-proxy Replaces egress-gateway","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/agent-proxy-replaces-egress-gateway","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### agent-proxy Replaces egress-gateway\n\n**What**\n\nInternal proxy component renamed from \"egress-gateway\" to \"agent-proxy\". All log messages now use the `[agent-proxy]` prefix.\n\n**Details**\n\n- All `[egress-gateway]` log strings are replaced with `[agent-proxy]`\n- No behavior change; this is a rename that aligns with the component's role in agent communication\n\n**Evidence**\n\nLog string comparison (search for `\"[agent-proxy] enabled on 127.0.0.1:\"`, `\"[agent-proxy] tunnel protocol v2 negotiated\"`)"}