1. Step 1: Open the third-party inference panel

    macOS

    In the menu bar, choose Help → Troubleshooting → Enable Developer Mode.

    Windows

    Open the ☰ menu, then Help → Troubleshooting → Enable Developer Mode.

    Then choose Developer → Configure Third-Party Inference….

  2. Step 2: Enter the RouterHub gateway settings

    Under Connection, enter:

    FieldValue
    Inference providerGateway
    Gateway base URLhttps://routerhub.si
    Gateway API keyYour RouterHub API key
    Credential kindStatic API key
    Gateway auth schemeBearer

    Leave OIDC / SSO blank. Under Models, keep the Claude entries. If they’re missing, copy a Claude model ID with Messages support from the models and pricing page.

  3. Step 3: Save and restart

    Click Apply Changes → Save & Restart (older builds: Apply locally). Choose Continue with Gateway, then pick a Claude model.

    Desktop saves the settings for you. No JSON file or Claude sign-in is needed. Keep your saved key private.

Need to install Claude Desktop?

Install the current app from Claude’s download page on macOS or Windows. On a managed device, check with your administrator before changing providers.

Check the connection (optional)

When you’re ready to use credits, open an empty project and send this short test:

Reply with OK. Do not read files, run commands, or make edits.

Open RouterHub usage and check that the request appears under the right model. Keep auto-approval off while testing. A text reply checks the connection, not all coding features.

Troubleshooting

A gateway request times out

The documented Desktop Gateway panel has no equivalent user-configurable API request timeout. Claude Code environment settings are not Desktop inference settings, and claude_desktop_config.json is for MCP, not this connection. Update Desktop and share a redacted error and request ID with support. Check Usage before retrying.

There is no Developer or Gateway option

Update the app, enable Developer Mode, and fully quit and reopen after applying changes. You may need to enable Developer Mode again after the first provider switch. Managed devices can lock these settings.

No model appears

Add an exact Claude ID from the models and pricing page under Models. Use a Claude model with Messages support rather than an arbitrary catalogue entry.

Authentication fails

Check Static API key, Bearer, the origin-only URL, and your RouterHub key and balance. A Claude subscription token or direct Anthropic key is not a RouterHub key.

Chat works but Cowork or Code fails

Those features have additional device, streaming, and tool-use requirements. Do not disable sandbox protections. Follow official diagnostics and redact logs before sharing them.

Should I enable 1M context?

Only if RouterHub confirms it for your chosen model. Don’t infer context or other gateway features from the model’s name.

Still stuck? Contact support.

Common questions

Can I use MCP settings to change the model provider?

No. claude_desktop_config.json configures MCP tools, not inference routing. Use the third-party Gateway panel.

Are all Desktop features confirmed?

No. The upstream configuration flow is documented, but RouterHub streaming, caching, tool use, Cowork, and Code have not been tested end to end.