SPACE ROUTER · Claude Desktop
Claude Desktop + Space Router
Connect Claude Desktop through its Gateway settings, choose a Claude model, and confirm where requests are billed.
Before you start
| Field | Value | Check |
|---|---|---|
| Supported setup | Windows; macOS; build with Third-Party Inference settings | Choose the matching OS installer; keep your current configuration backup |
| Account | A Space Router account and matching group credit/subscription | The app’s own login and the router API key are separate |
Download stages are shown in the terminal. Direct downloads show a progress bar or received bytes; package managers use their own output. A percentage may be unavailable. Keep the terminal open until the final installation and connection results.
Space Router one-click scripts report INSTALLATION separately from CONNECTION. DONE means the app or command was checked; VERIFIED means the stated response test passed. SKIPPED / NOT CONFIGURED needs the connection steps. FAILED / INCOMPLETE needs the displayed error fixed. A CLI test does not verify a desktop app or editor panel.
Model examples and placeholders must be replaced with IDs allowed by your key’s group. You can install the app first, then create the key before the connection steps.
Gateway mode uses your Space Router Claude key for inference. This mode can use the configured provider without an Anthropic sign-in; your normal Claude account/subscription remains a separate route. The Space Router desktop connection still needs the real-response check below.
1 · One-click installation
Windows
Open the PowerShell app: press the Windows key, type PowerShell, and open it. Copy the command below, paste it into PowerShell, then press Enter.
irm https://stationine.com/setup-claude-desktop.ps1 | iexOpen PowerShell and run the setup command. It installs Claude if missing, checks the app, and prompts privately for your own Claude-group key. An empty key skips connection setup.
Download the Windows app from the official Claude download page. Run the installer and open Claude.
macOS
Open the Terminal app: press Command + Space, type Terminal, and open it. Copy the command below, paste it into Terminal, then press Return.
bash -c 'script=$(curl -fL --progress-bar https://stationine.com/setup-claude-desktop.sh) && test -n "$script" && bash -c "$script"'On macOS 14 or later, open Terminal, paste this command and press Return. No prior Claude download is needed.
Downloads the official universal app, checks its SHA256, bundle identity, code signature and macOS approval, then installs to ~/Applications/Claude.app and opens it. An existing installation is preserved. Read the final INSTALLATION result.
This Mac installer leaves existing accounts and settings intact. CONNECTION is reported as not configured by this installer. Complete the Gateway settings below, then verify a real reply. Normal macOS prompts may require your action. Official manual download.
Find the gateway configuration
At the sign-in screen, open the macOS menu bar or the Windows application menu. Look for Help → Troubleshooting → Enable Developer Mode, then Developer → Configure Third-Party Inference.Check whether your build allows local setup
If that menu is missing, update from the official app channel and check the official in-app instructions. An organization-managed configuration may be read-only; use your administrator’s approved configuration.
The app is installed when it opens normally. Connecting the gateway is a separate step below. A Claude Code or CC Switch installation does not configure this desktop panel.
2 · Create your API key
Sign in to Space Router
Open space.stationine.com and sign in to your own account. Confirm you have usable credit or an eligible subscription before testing.Create a dedicated API key
Open API Keys → Create API Key. Name the key after this tool. Select Claude / Anthropic; use the groups actually available to your account. A key for a different model family is not interchangeable.Copy the full key and the model ID
Save the full key in your password manager. Copy one exact model ID allowed by that key’s group from Available Channels. Keep any limits or expiry you need. A model shown in an app’s public list may not belong to your key.Keep the key private
Paste the key only into your own app or local credential store. Do not include it in shared screenshots, project files, import links or support messages. For two purchased groups, create two separate keys.

3 · Connect Space Router
Set the Gateway connection
In Configure Third-Party Inference, choose the following connection values. Keep your current configuration backup before applying changes.
| Field | Value | Check |
|---|---|---|
| Connection | Gateway | A custom inference gateway |
| Gateway base URL | https://space.stationine.com | Root URL; the app adds /v1/messages |
| Gateway API key | YOUR_CLAUDE_GROUP_KEY | Your own Claude-group key |
| Gateway auth scheme | bearer | Authorization: Bearer |
| Credential kind | Static API key | Leave SSO/OIDC fields blank for this route |
Add the Claude model
Use the Models / Identity & models section if discovery is empty. Add the exact Claude model ID allowed by your Space Router key, plus a display name if requested. Only claim extended context when confirmed for that model and group.
The desktop gateway requires Anthropic Messages with streaming and tool use. Model discovery alone does not prove compatibility with Chat, Cowork or Code. Test the mode you intend to use.
Test and apply locally
Use Test connection if shown. Apply Changes / Apply locally saves to this device. Do not export or share a configuration containing your key.Reopen in Gateway mode
Fully quit and reopen Claude. Choose Continue with Gateway / Local configuration when offered. Select your added Claude model and start a new conversation. An ordinary claude.ai session can continue to use its own account route.
Continue your previous chats
Import copies history into Gateway mode; later replies use your configured provider. It is not live sync with claude.ai, and originals remain there.
Enable the import wizard first
The deployment configuration must includeclaudeAiImportwithenabled: true. It is off by default. Ask your deployment administrator to merge this setting into the existing configuration; do not replace your Gateway settings.Open Settings → Import & export → Import…
Choose Sign in to claude.ai, authorize your own export, then Fetch export. Alternatively, export your data from claude.ai Settings → Privacy and choose the downloaded ZIP in the wizard. Keep that archive private.Review, import and resume
Select the chats and any local Cowork & Code sessions you need, review and import. Open an imported chat from the sidebar and accept Trust and resume / Continue after reviewing it. New replies use Space Router while Gateway is selected.
Import again to bring over later cloud history; already imported items are skipped. Team/Enterprise exports may require workspace-owner approval. Availability depends on your installed build and deployment policy.
4 · Verify a real response
Select Gateway mode first, then perform the response test in Chat. Verify Cowork/Code and a harmless file read separately if you need those modes. Space Router desktop acceptance requires the actual client reply plus a matching usage record.
Reopen the client
Save your settings, fully quit the app and reopen it. Start a new conversation. Select the Space Router provider and the exact model allowed by your key; do not leave the previous provider selected.Ask a small, checkable question
SendWhat is 17 plus 25? Reply with just the number.Expect a complete reply of42. This uses your account credit at the selected model’s normal rate. A speed check or HTTP 200 alone is not enough.Match the usage record
Open Space Router’s usage history. Match the request time, model and API key with this test. A client reply plus the matching record is stronger evidence than an “installed” or “connected” label.
Troubleshooting
| Symptom | What to check |
|---|---|
| 401 / 403 | Check the full key, its enabled/expiry/IP settings, and group permission. Re-paste privately; do not publish the key. |
| 404 / model not found | Match the API format, base URL and exact model ID. Do not add /v1 twice or enter a full request path into a base-URL field. |
| 429 / credit or quota error | Check account credit, key quota and rate/concurrency limits. Repeated retries do not add balance or remove a limit. |
| Timeout / incomplete reply | Check the network and channel status. Keep the time and request ID for support; do not treat a partially received reply as a successful test. |
| Still uses the previous provider | Reopen the client, start a new conversation, and check its selected provider and any environment/config overrides. Restore a backup instead of deleting the whole configuration. |
If you need help, send the app version, operating system, model ID, timestamp and request ID to Space Router support. Redact keys and private project content.
| Field | Value | Check |
|---|---|---|
| Gateway option missing | Check the official build, Developer menu and whether a managed profile controls the app; apply locally and fully relaunch. | Claude Code environment variables do not configure this panel |
| Empty model picker | Enter the exact Claude ID under Models; verify the key group. Auto-discovery only lists recognizable Claude IDs. | A model list is not a response test |
| Chat works, Cowork/Code fails | Check streaming/tool support and the mode’s network or workspace restrictions. Keep the error and request time for support. | Do not disable TLS verification or sandbox isolation |
Backup, update and recovery
Before editing an existing setup, copy Claude Desktop local third-party inference configuration and local data to a private backup. Keep the original provider name and model selection so you can return to them. Do not put credential backups in a project repository.
To recover, close the client, restore the specific file or select the previous provider, then reopen it. Keep conversations and other unrelated settings. Revoke an exposed key in Space Router and create a replacement only if it was actually exposed.
Use the application’s normal update flow. Recheck the provider selection and one real response after an update; do not rerun several installers together when one is still active.
To return to your previous route, use the app’s third-party configuration controls to restore the saved connection or return to its normal sign-in flow. Keep gateway conversations and cloud account history separate; back up local data before changing modes.