SPACE ROUTER · VS Code
VS Code + Space Router
Install VS Code and the Claude Code/Codex extensions, then connect and test each assistant separately.
Before you start
| Field | Value | Check |
|---|---|---|
| Supported setup | Windows; macOS | 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.
When this tool uses your Space Router endpoint and key, its model requests use your Space Router balance or eligible subscription. App sign-in, app subscriptions and cloud-only features are separate. Confirm the actual route in usage history after testing.
1 · One-click installation
The installer installs VS Code if missing, Claude Code and Codex tools, and their extensions. Each key prompt can be skipped. A skipped key leaves that assistant unconnected, not removed.
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-vscode.ps1 | iexOpen PowerShell from the Windows Start menu. Paste the command, press Enter, and leave the window open until it finishes.
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-vscode.sh) && test -n "$script" && bash -c "$script"'Open Terminal from Spotlight (Command + Space). Paste the command and press Return.
Respond to the key prompts
Paste your own purchased-group key when the installer asks. Press Enter to skip a group you did not buy. Test requests consume your account credit. Do not paste a customer or supplier administrator key.Reopen the terminal and confirm installation
If a command is not found, close the terminal completely and open a new one so it reloads PATH. Then run the version check below. If installation failed, read the last error before rerunning; do not start several copies together.
code --versionYou should see the tool’s version output. A version check proves the executable is reachable; the provider test comes later.
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 and/or GPT / OpenAI (separate keys); 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
Confirm both extension publishers
Open Extensions. Confirmanthropic.claude-codeandopenai.chatgptare installed if you want both assistants. Install only the one you need when using the manual path.Connect each client separately
The Claude extension uses Claude Code configuration; the Codex extension uses Codex configuration. Follow the Claude Code and Codex provider sections if configuring manually. The API key must match each assistant’s group.Open each sidebar
Reload VS Code, open your test folder and choose the Claude or Codex activity-bar icon. If hidden, open the command palette (Ctrl+Shift+P / Command+Shift+P) and search the assistant’s name. Start a new chat in each panel.Check environment boundaries
For a WSL/SSH/dev-container window, install/configure the tools in that remote environment. Local Windows configuration is not automatically a Linux/remote configuration. First verify a normal local window if you are new to this.
| Field | Value | Check |
|---|---|---|
| Claude route | Anthropic Messages · https://space.stationine.com | Claude-group key |
| Codex route | OpenAI Responses · https://space.stationine.com/v1 | GPT-group key |
Do not put real keys in a shared .vscode/settings.json. If a dedicated Claude config directory is used, the extension must see that same directory.
Claude extension still asks to sign in?
Open the command palette → Preferences: Open User Settings (JSON). Merge the extension environment setting below into private user settings. This reaches the extension’s own gateway login check; CLI settings alone may only reach its spawned process. Keep the key out of workspace .vscode/settings.json.
{
"claudeCode.environmentVariables": [
{
"name": "ANTHROPIC_BASE_URL",
"value": "https://space.stationine.com"
},
{
"name": "ANTHROPIC_API_KEY",
"value": "YOUR_CLAUDE_GROUP_KEY"
}
]
}Keep this private: user settings contain the entered key. Use a local user profile with Settings Sync disabled for this credential-bearing setting, or your organization’s approved credential delivery. Fully restart VS Code; test the Claude and Codex panels separately.
4 · Verify a real response
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.
Before using the agent in a real project, create a scratch folder with a harmless README and ask it to read and summarize that file. Check the proposed tool action before allowing it. Model text output alone does not establish tool-calling support.
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. |
| CLI works but sidebar fails | Check extension identity, local/remote window, active config directory and which environment launched the editor. |
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.
Backup, update and recovery
Before editing an existing setup, copy your VS Code user settings and the active Claude/Codex user configuration 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.