{"version":"2.1.124","anchor":"egress-gateway-rename-was-upstream-proxy","canonical_anchor":"egress-gateway-rename-was-upstream-proxy","heading":"Egress gateway rename (was \"upstream proxy\")","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124\/e\/egress-gateway-rename-was-upstream-proxy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124","markdown":"### Egress gateway rename (was \"upstream proxy\")\n\nThe internal MCP-proxy infrastructure was renamed end-to-end:\n\n- New endpoints: `\/v1\/code\/egress\/gateway` (was `\/v1\/code\/upstreamproxy\/...`) and `\/v2\/session_ingress\/mcp\/ws\/`.\n- All log lines moved from `[upstreamproxy] ...` to `[egress-gateway] ...` (e.g. `[egress-gateway] enabled on 127.0.0.1:`, `[egress-gateway] relay listening on 127.0.0.1:`, `[egress-gateway] aws config write failed: ...`, `[egress-gateway] prctl unavailable: ...`, `[egress-gateway] no session token; proxy disabled`, `[egress-gateway] ws error: ...`).\n- The internal `initEgressGateway` \/ `getEgressGatewayEnv` \/ `registerEgressGatewayEnvFn` exports replace the `*UpstreamProxy*` names.\n- Init failures now log `[init] egress gateway init failed: ...; continuing without proxy`.\n\nIf you scrape Claude Code logs for the old `upstreamproxy` prefix, update your queries.\n\n**Evidence**\n\nRenamed prefixes (search for `\"[egress-gateway]\"` and `\"\/v1\/code\/egress\/gateway\"`)."}