SPACE ROUTER · Cline / Roo Code / Kilo Code
Cline / Roo Code / Kilo Code + Space Router
Choose one extension, install it, and configure an OpenAI-compatible Space Router provider.
Before you start
| Field | Value | Check |
|---|---|---|
| Supported setup | Windows; macOS; VS Code or a supported editor | 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 · Install from zero
Install your editor
Install VS Code for Windows or macOS. On Windows run the installer; on Mac move the app to Applications. Open an empty test folder. If your existing editor supports the chosen extension, use it instead.Choose one extension
Open Extensions with Ctrl+Shift+X on Windows or Command+Shift+X on Mac. Search for Cline, Roo Code or Kilo Code; confirm the publisher on the linked official documentation and install only your chosen extension.Open its panel
Reload the editor if asked. Open the new extension icon in the activity bar. If hidden, use the command palette to search for the extension’s name. You should see its first-run/provider settings screen.
The three extensions store their own settings. Completing one does not configure the other two; choose the matching subsection below.
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 GPT / OpenAI for OpenAI-compatible setup; 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
| Field | Value | Check |
|---|---|---|
| Provider type | OpenAI Compatible / OpenAI-compatible | Use the custom provider, not the official-account login |
| Base URL | https://space.stationine.com/v1 | A base URL, not /chat/completions |
| API key | YOUR_GPT_GROUP_KEY | Your own GPT-group key |
| Model ID | YOUR_GPT_MODEL_ID | Copy the exact allowed ID; replace the placeholder |
Cline
Open Cline settings
Open the Cline sidebar, choose its gear/settings, then select OpenAI Compatible as the provider. Fill the three values above and save.Choose Plan and Act models
If the version keeps separate Plan and Act settings, configure the same intended provider/model in both before testing. Start a new task in the scratch folder.
Roo Code
Create an API configuration profile
Open Roo Code’s settings/API configuration. Add a named profile such as Space Router, select OpenAI Compatible and fill base URL, key and exact model ID. Save the profile.Select the saved profile
Select Space Router in the task panel before starting. If context/output limits are requested, use confirmed model values; do not copy arbitrary large limits from another model.
Kilo Code
Add a custom provider
Open Kilo settings → Providers and add an OpenAI-compatible provider. Enter the base URL and key. Fetch models if offered, or add the exact allowed ID manually. Submit/save.Select the model in a new task
Return to the task panel and pick the model from your custom provider. A detected model list does not establish group permission or tool support; finish the real-request check below.
Choose the model for this conversation
Provider settings and the current conversation’s model selection are separate. After saving a provider, start a new task/chat and explicitly select its model. If the app has separate planning, acting or helper models, keep each on an allowed Space Router route before testing.
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. |
| Chat works, tool action fails | Check model tool support, extension mode and project permissions. A text-only model test does not establish agent compatibility. |
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 the chosen extension’s provider profile/export 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.