Answer: To connect Claude Code to an LLM gateway your organization already runs, deploy the gateway following its own documentation, then complete the Claude Code side with the rollout steps: deploy the gateway with your provider credential, issue each developer a gateway credential, distribute the configuration through a managed settings file and secrets tooling, and have each developer check for the configuration in Claude Code. Developers connecting to an existing gateway can follow the connect page to set the base URL and credential themselves. Status: Confirmed Entry: tool/claude-code/integrations/connect-claude-code-to-gateway Revision: 2 Digest: sha256:79e404c1cefc34d9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:04:34Z Last changed: 2026-11-15T12:21:55Z (Check succeeded again) Last verified: 2026-11-20T12:21:51Z Next check: 2026-11-21T12:21:51Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of developer connect page | connect Claude Code to your gateway | [1] | 2026-11-20 admin rollout page | deploy and distribute a gateway | [1] | 2026-11-20 rollout step 1 | Deploy the gateway and give it your provider credential | [1] | 2026-11-20 rollout step 2 | Issue each developer a gateway credential | [1] | 2026-11-20 rollout step 3 | managed settings file | [1] | 2026-11-20 rollout step 4 | check for the configuration in Claude Code | [1] | 2026-11-20 minimum version for allowedProviders | v2.1.285 | [1] | 2026-11-20 Sources: [1] Anthropic. "Other LLM gateways". https://code.claude.com/docs/en/llm-gateway.md Role: primary. Accessed: 2026-11-20T12:21:51Z Quote: "If you're a developer connecting to an existing gateway: [connect Claude Code to your gateway]" (Supports: developer connect page) Quote: "If you're an admin rolling out a gateway for your organization: [deploy and distribute a gateway]" (Supports: admin rollout page) Quote: "Deploy the gateway and give it your provider credential, so it can authenticate the requests it forwards." (Supports: rollout step 1) Quote: "Issue each developer a gateway credential, so usage is attributed to the developer and offboarding revokes one credential." (Supports: rollout step 2) Quote: "Distribute the configuration through a [managed settings file]" (Supports: rollout step 3) Quote: "Have each developer [check for the configuration in Claude Code]" (Supports: rollout step 4) Quote: "Requires Claude Code v2.1.285 or later." (Supports: minimum version for allowedProviders) Published: 2026-11-20T10:36:07Z Snapshot SHA-256: 18085351a5aa7a2e4327a11d0d95bb0aaea53e3feee9a6fe019c694c50619ce7 (captured 2026-11-14T12:17:37Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T12:21:55Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:21:51Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:21:51Z Last attempt: 2026-11-20T12:21:51Z Notes and limitations: Extracted automatically from a single official source (section "Other LLM gateways"). Related: https://latestn.com/tool/claude-code/integrations/connect-github-repository How do I connect a GitHub repository to Claude Code cloud sessions? https://latestn.com/tool/claude-code/integrations/connect-tools What tools and integrations can I connect to Claude Code, like Chrome, Slack, or CI/CD? https://latestn.com/tool/claude-code/integrations/cwd-vs-repo-parameter What is the difference between the cwd and repo parameters in a Claude Code deep link? https://latestn.com/tool/claude-code/integrations/build-webhook-receiver-channel How do I build an MCP server that pushes webhooks or alerts into a Claude Code session? https://latestn.com/tool/claude-code/integrations/check-mcp-and-hooks How do I check whether my MCP servers and hooks are loaded in Claude Code? https://latestn.com/tool/claude-code/integrations/code-review-gitlab-merge-request How do I post Claude Code's /code-review findings to a GitLab merge request? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T12:21:55Z | recovered | Check succeeded again | — 2026-11-15T12:21:55Z | changed | minimum version for allowedProviders: — → v2.1.285 | [1] 2026-11-15T12:21:55Z | changed | rollout step 4: — → check for the configuration in Claude Code | [1] 2026-11-15T12:21:55Z | changed | rollout step 3: — → managed settings file | [1] 2026-11-15T12:21:55Z | changed | rollout step 2: — → Issue each developer a gateway credential | [1] 2026-11-15T12:21:55Z | changed | rollout step 1: — → Deploy the gateway and give it your provider credential | [1] 2026-11-15T12:21:55Z | changed | admin rollout page: — → deploy and distribute a gateway | [1] 2026-11-15T12:21:55Z | changed | developer connect page: — → connect Claude Code to your gateway | [1] 2026-11-15T12:21:55Z | changed | Minimum version for allowedProviders: v2.1.285 → — | [1] 2026-11-15T12:21:55Z | changed | Base URL variable: ANTHROPIC_BASE_URL → — | [1] 2026-11-15T12:21:55Z | changed | Rollout step 4: check for the configuration in Claude Code → — | [1] 2026-11-15T12:21:55Z | changed | Rollout step 2: Issue each developer a gateway credential → — | [1] 2026-11-15T12:21:55Z | changed | Rollout step 1: Deploy the gateway and give it your provider credential → — | [1] 2026-11-14T12:17:38Z | check-failed | Extraction did not pass verification: answer does not contain any extracted value | — 2026-11-13T03:04:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/integrations/connect-claude-code-to-gateway/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/integrations/connect-claude-code-to-gateway POST: https://latestn.com/dispute/tool/claude-code/integrations/connect-claude-code-to-gateway with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/integrations/connect-claude-code-to-gateway?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I connect Claude Code to an LLM gateway my organization already runs? Revision 2, last verified 2026-11-20T12:21:51Z. https://latestn.com/tool/claude-code/integrations/connect-claude-code-to-gateway (accessed 2026-11-21T10:00:33Z). @misc{LatestN_tool_claude_code_integrations_connect_claude_code_to_gateway_r2, title = {How do I connect Claude Code to an LLM gateway my organization already runs?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/integrations/connect-claude-code-to-gateway}}, note = {Revision 2; digest sha256:79e404c1cefc34d9; last verified 2026-11-20T12:21:51Z; accessed 2026-11-21T10:00:33Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/integrations/connect-claude-code-to-gateway