{"version":"2.1.227","anchor":"claude-gateway-now-identifies-itself-as-the-gateway-provider","canonical_anchor":"claude-gateway-now-identifies-itself-as-the-gateway-provider","heading":"claude gateway now identifies itself as the gateway provider","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/claude-gateway-now-identifies-itself-as-the-gateway-provider","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### `claude gateway` now identifies itself as the gateway provider\n\nRunning `claude gateway` now reports gateway as the provider regardless of credentials.\n\n**What**\n\nRunning the `gateway` subcommand, which starts the enterprise auth and telemetry gateway, now makes Claude Code report \"gateway\" as its provider. Previously that only happened when gateway credentials were present.\n\n**Evidence**\n\n`gatewayServerProcess`\n\n- Area: Elsewhere\n- Names: `claude gateway`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}