Claude Desktop in Russia: Configuring an Inference Gateway

What third-party inference means in Claude Desktop

Normally, Claude Desktop uses an Anthropic account and Anthropic services. Third-party inference changes the path of the model request: the application sends it to the configured gateway. This does not turn a third-party API into a Claude subscription or remove the application's own requirements for installation, updates, or feature availability.

Do not confuse an inference gateway with Desktop Extensions or MCP. Extensions give Claude access to local applications and data. The gateway routes requests to a model. A failure in one layer does not prove that another layer is broken.

Anthropic's current documentation says Claude Desktop is available for macOS, Windows, and Linux beta. The Help → Troubleshooting and Developer → Configure Third-Party Inference… menu paths below are confirmed by the current BetterToken macOS guide. On another operating system, first check that the installed application version exposes the same settings.

Choose a route based on the API key group

• Claude group: direct Anthropic-compatible gateway; Gateway base URL is https://www.bettertoken.ai; auth scheme is x-api-key.
• Codex group: BetterToken → CC Switch → local Claude route; Gateway base URL is the Service address from CC Switch; auth scheme is bearer.

For a Codex group, do not put https://www.bettertoken.ai/v1 directly into the Claude Desktop Gateway. That is an OpenAI-compatible Base URL, while the Gateway field expects an Anthropic-compatible route. CC Switch accepts the OpenAI Responses API, maps models, and exposes a local service address to Claude Desktop.

Direct setup for a Claude group

1. Install the current Claude Desktop

Download the application from the official Claude page. Anthropic's normal installation flow asks you to sign in. The BetterToken Gateway flow begins before the normal sign-in: follow the gateway guide's sequence so the two modes do not become mixed.

2. Enable Developer Mode

On macOS, open:

Help → Troubleshooting → Enable Developer Mode

Click Enable and quit Claude Desktop completely. After relaunching, a Developer menu should appear.

3. Open the gateway settings

Go to:

Developer → Configure Third-Party Inference…

Select Gateway and fill in:

Gateway base URL: https://www.bettertoken.ai
Gateway API key: ваш API Key из Token management
Gateway auth scheme: x-api-key

Do not put the key in an article, screenshot, public log, or repository. Once x-api-key is selected, the application should request the available models for the Claude group.

4. Apply the settings and restart

Click Apply locally, then Relaunch now. After launch, select Continue with Gateway. The Cowork 3P | Gateway label in the lower-left corner indicates the active route.

Local route for a Codex group

This route is longer: Claude Desktop connects to a local CC Switch address, and CC Switch sends requests to the BetterToken OpenAI Responses API.

1. Add BetterToken as a provider in CC Switch

Open Claude Code, click Add Provider, and enter:

Provider Name: BetterToken
Base URL: https://www.bettertoken.ai
API Key: ваш BetterToken API Key

Under Advanced Options, select OpenAI Responses API. Then click Fetch Model List and explicitly assign models to the available mapping fields. Use only current IDs from your Codex group; do not copy a model from an old article or someone else's screenshot.

2. Enable the local route

Save the provider, set it to In use, and enable the proxy. Under Settings → Routing, check the master switch and Claude route. Copy the displayed Service address; that local address is what Claude Desktop needs.

3. Fill in the Gateway fields in Claude Desktop

Return to Developer → Configure Third-Party Inference…, select Gateway, and enter:

Gateway base URL: Service address из CC Switch
Gateway API key: ваш BetterToken API Key
Gateway auth scheme: bearer

In Model list, add the current Model ID and Display name configured in CC Switch. Click Apply locally, agree to Relaunch now, and select Continue with Gateway.

How to verify the request and Dashboard record

Do not begin with workspace-directory access or a long task. Send a short request without personal data—for example, ask for the difference between a JSON array and object—then open the BetterToken Dashboard.

A successful check has two signals:

1. Claude Desktop displays the response and the active Cowork 3P | Gateway mode.
2. The Dashboard shows a matching record with its time, model, status, input/output/cache tokens, and charge.

If you get a response but no record, confirm that the application is actually using the Gateway rather than another mode. If a record appears with an error status, the route reached the API layer: check the key group, auth scheme, model, and balance. Do not use the Dashboard as storage for a complete prompt or response; remove keys and request contents from logs before contacting support.

What to check when Claude Desktop will not connect

• No Developer menu: enable Developer Mode again and quit Claude Desktop completely instead of merely closing the window.
• Your provider setup needs a fix: check Model list, current IDs, and all required mappings in CC Switch.
• 401 or 403: select x-api-key for a Claude group and bearer for a Codex group's local route.
• No response and no Dashboard record: confirm that the proxy, master Routing switch, and Claude route are enabled in CC Switch.
• A record appears but the request fails: check the key group, current model, available balance, and stray spaces in the key.
• Nothing changes after Apply locally: click Relaunch now, then select Continue with Gateway.

Do not diagnose the Gateway from one interface label. Correlate the Claude Desktop mode, local-route state, and Dashboard request record to see where the chain breaks.

Limitations of this method

BetterToken is an independent API provider, not an Anthropic product or a replacement for a Claude subscription. It is responsible for its own API endpoint and setup documentation. Download access, sign-in, updates, Cowork, Code mode, and other Claude Desktop features depend on the current application version, plan, and Anthropic's rules.

Connecting to the BetterToken API endpoint from Russia does not require a VPN. This statement does not cover the Claude website, application downloads, accounts, or external services. If your menu differs from this article, stop and compare the official Claude Desktop installation documentation with the current BetterToken setup guide.

FAQ

Can I put https://www.bettertoken.ai/v1 in the Claude Desktop Gateway?

Not for the workflow described here. It is an OpenAI-compatible address. A Claude group uses the direct Anthropic-compatible endpoint https://www.bettertoken.ai; a Codex group connects through the local Service address from CC Switch.

Do I need a Claude account for Gateway mode?

Anthropic's normal instructions ask you to sign in after installation. The current BetterToken Gateway guide takes the user through Continue with Gateway before the normal sign-in. Do not copy steps from one mode into the other; check the interface in your installed Claude Desktop version.

How do I know which auth scheme is correct?

Use x-api-key for a direct Claude group. Use bearer for a Codex group routed locally through CC Switch. After applying the settings, verify both the Desktop response and a new Dashboard record.