Loading…
TL;DR: Claude Desktop defaults to Anthropic's API. When you hit timeouts or connection errors, Developer Mode lets you edit claude_desktop_config.json to point ANTHROPIC_BASE_URL at a custom endpoint — 5 minutes, MCP unaffected.
By default, Claude Desktop routes all API requests to Anthropic's official endpoint. For some developers, this results in:
unsupported_region errors when Anthropic's API is unavailable in your regionThe fix is to route Claude Desktop's underlying API traffic through a third-party aggregation gateway by pointing the client at a custom baseURL. This is done through Claude Desktop's developer mode — a configuration file you edit once, and the client picks up on the next restart.
The process takes about five minutes and does not require system-level proxy configuration. MCP tools, Projects, and Artifacts continue to work normally.
Claude Desktop provides two entry points to enable developer mode — use whichever is easier to find:
Entry point | Path |
|---|---|
Top menu bar | Help → Enable Developer Mode |
In-app settings | Settings → Developer → Edit Config |
Both paths lead to the same place: a JSON configuration file called claude_desktop_config.json.
This file controls three things:
ANTHROPIC_BASE_URL and ANTHROPIC_API_KEY for custom API routingDeveloper mode is not a separate runtime state — it's an entry point to edit this configuration file. Changes take effect after a full restart of the application.
https://api.codegateway.dev/v1)Two options — pick one:
This opens claude_desktop_config.json at its default location:
~/Library/Application Support/Claude/claude_desktop_config.jsonYou can also open it directly from Terminal:
open ~/Library/Application\ Support/Claude/claude_desktop_config.jsonAdd an "env" field to the JSON with your gateway URL and key:
{
"mcpServers": {},
"env": {
"ANTHROPIC_BASE_URL": "https://api.codegateway.dev/v1",
"ANTHROPIC_API_KEY": "your-codegateway-api-key"
}
}If you already have MCP servers configured, append the "env" block without replacing the rest of the file:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/yourname/Documents"]
}
},
"env": {
"ANTHROPIC_BASE_URL": "https://api.codegateway.dev/v1",
"ANTHROPIC_API_KEY": "your-codegateway-api-key"
}
}Save the file, then quit Claude Desktop entirely via Claude (menu bar) → Quit Claude. Closing the window is not enough — Claude Desktop stays resident in the menu bar. Restart the app after quitting.
Two options — pick one:
You can also navigate to the config file manually:
%APPDATA%\Claude\claude_desktop_config.jsonPaste this path into File Explorer's address bar and press Enter to jump straight to it.
Same structure as macOS:
{
"mcpServers": {},
"env": {
"ANTHROPIC_BASE_URL": "https://api.codegateway.dev/v1",
"ANTHROPIC_API_KEY": "your-codegateway-api-key"
}
}For Windows filesystem paths in MCP server args, use double backslashes:
"args": ["C:\\Users\\yourname\\Documents"]Right-click the Claude icon in the system tray → Exit, then relaunch.
If you manage multiple machines, or want to keep the API key out of the config file, you can set the variables at the OS level instead.
macOS / Linux (add to ~/.zshrc or ~/.bashrc):
export ANTHROPIC_BASE_URL="https://api.codegateway.dev/v1"
export ANTHROPIC_API_KEY="your-codegateway-api-key"Claude Desktop must be launched from the terminal to inherit these shell variables:
open -a "Claude"Launching by double-clicking the app icon bypasses the shell environment on macOS.
Windows (System → Advanced system settings → Environment Variables):
Add as system-level variables:
ANTHROPIC_BASE_URL = https://api.codegateway.dev/v1ANTHROPIC_API_KEY = your keyWindows environment variables are inherited by all processes, so a terminal launch is not required.
Priority: env block in claude_desktop_config.json takes precedence over system environment variables when both are set.
After restarting, send a message in Claude Desktop. Then check your CodeGateway Dashboard — a new request should appear in the usage log within a few seconds.
To verify the endpoint directly from the command line:
curl -s https://api.codegateway.dev/v1/models \
-H "Authorization: Bearer your-codegateway-api-key" \
| python3 -m json.tool | head -20A valid model list confirms the connection is working. If you get 401 Unauthorized, the key is wrong. If curl returns cleanly but Claude Desktop still fails, check the JSON for syntax errors — a trailing comma in the wrong place is the most common culprit.
Configuring a custom API endpoint does not interfere with MCP tools. The two are separate channels:
ANTHROPIC_BASE_URLThey coexist without conflict. A complete config using both looks like this:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/yourname/projects"]
},
"postgres": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
}
},
"env": {
"ANTHROPIC_BASE_URL": "https://api.codegateway.dev/v1",
"ANTHROPIC_API_KEY": "your-codegateway-api-key"
}
}In our own testing with four MCP servers active simultaneously while routing through CodeGateway, tool-call latency stayed effectively unchanged. The inference path routes through Cloudflare's global edge network, which improved time-to-first-byte versus a direct connection in our small-sample internal test (illustrative, not a formal benchmark).
The connection fails after configuring. What should I check first?
Run the curl verification command above. 401 Unauthorized means the key is wrong. A successful curl but a failing desktop client almost always means a JSON syntax error in the config file — open the file again and look for a trailing comma, mismatched braces, or missing quotes.
Does ANTHROPIC_BASE_URL need the /v1 suffix?
Yes. Claude Desktop appends the API path after the base URL, constructing requests like {ANTHROPIC_BASE_URL}/messages. Without /v1, the full path becomes api.codegateway.dev/messages, which returns 404.
Is it safe to store an API key in a local config file?
The file is readable only by the current user on a single-user machine. For personal development setups, this is standard practice. On shared machines, use the environment variable method instead — the key never touches the config file.
Can I configure different endpoints for different conversations?
Not currently. ANTHROPIC_BASE_URL is global to the Claude Desktop instance. Switching endpoints requires editing the config and restarting the application. If per-conversation model routing is important to you, Claude Code's ANTHROPIC_BASE_URL environment variable (set per shell session) gives you more granular control.
Will a Claude Desktop update wipe the config?
No. claude_desktop_config.json is user data stored separately from the application binary. Updates preserve it.
Which models does CodeGateway support in Claude Desktop?
All current Claude models — Haiku, Sonnet, and Opus — plus OpenAI GPT models. Claude Desktop's model selector determines which model each conversation uses. CodeGateway routes based on the model field in the request and does not override it.
Do Projects and Artifacts still work?
Yes. Projects and Artifacts data is stored on the Anthropic account side and does not pass through the API. The ANTHROPIC_BASE_URL configuration only affects model inference requests. Both features continue to work normally.
**Authoritative references:**Anthropic API getting started · Claude Code official docs