SPACE ROUTER · Junie CLI
Junie CLI + Space Router
Install Junie CLI and use a custom model profile to connect directly to Space Router.
Before you start
| Field | Value | Check |
|---|---|---|
| Supported setup | Windows; macOS; current Junie CLI with custom model profiles | 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
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-junie.ps1 | iexOpen PowerShell and run the official installer:
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-junie.sh) && test -n "$script" && bash -c "$script"'Open Terminal and run:
Reopen the terminal and check the version and supported options. If your organization blocks script execution, use its approved installation method.
junie --version
junie --helpUse the CLI custom-model route below. The JetBrains IDE’s own Junie/AI settings are a separate configuration.
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 this custom-model example; 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
Create a custom model profile
In your scratch project, create .junie/models/space-router.json. The profile holds an environment reference rather than the key itself:
{
"id": "YOUR_GPT_MODEL_ID",
"displayName": "Space Router GPT",
"providerName": "Space Router",
"baseUrl": "https://space.stationine.com/v1/chat/completions",
"apiType": "OpenAICompletion",
"apiKey": "${SPACE_ROUTER_GPT_KEY}"
}Replace the model placeholder with an allowed GPT ID. Junie expects a full request endpoint in baseUrl; here it must include /v1/chat/completions. Do not select the built-in OpenRouter provider with a Space Router key.
Set the key and select the profile
Windows
$env:SPACE_ROUTER_GPT_KEY = 'YOUR_GPT_GROUP_KEY'
junie --model custom:space-routermacOS
export SPACE_ROUTER_GPT_KEY='YOUR_GPT_GROUP_KEY'
junie --model custom:space-routerEnter the real key only on your own device; use your credential manager for routine use. The profile filename determines custom:space-router. In the interactive picker, look under Custom. Leave fasterModel unset for this first test so it inherits the same route.
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. |
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.
If the custom profile is absent, check its JSON syntax and filename, the model search location and the named environment variable. If replies arrive but the agent loops or tool parsing fails, test a model with verified tool support before using a real repository.
Backup, update and recovery
Before editing an existing setup, copy .junie/models/space-router.json and private credential environment 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.
Keep the JSON profile and a copy of the previous selected model. Restore that selection or remove only this profile to stop using this route. Clear the test key from the process environment when finished; update through Junie’s official flow.