{"version":"2.1.280","anchor":"gateway-base-url-now-resolved-from-stored-gateway-auth-crede","canonical_anchor":"gateway-base-url-now-resolved-from-stored-gateway-auth-crede","heading":"Gateway base URL now resolved from stored gateway auth credentials","tier":"notice","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/gateway-base-url-now-resolved-from-stored-gateway-auth-crede","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Gateway base URL now resolved from stored gateway auth credentials\n\nBase URL lookup for the gateway provider now returns the stored gateway auth URL instead of nothing\n\n**Unclear.** The finding does not say what previously happened downstream when this lookup returned undefined, so the practical impact of the earlier gap is not stated.\n\n**What**\n\nWhen Claude Code resolves the base URL to use for the `gateway` provider (a setting for routing requests through a gateway server rather than directly), it now reads that URL from the stored gateway authentication credentials on the machine. Previously this lookup returned nothing for the `gateway` case.\n\n**Why**\n\nWithout a URL being returned, requests relying on this lookup for the `gateway` provider had no base URL to use. Pulling the URL from the stored gateway auth state means the correct address is now actually supplied.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}