spacedriveapp / spacedriveapp/spacebot
OpenRouter config: model id without openrouter/ prefix errors as unknown provider
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.4k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
Problem
When configuring Spacebot to use OpenRouter, setting the model to google/gemini-3-flash-preview fails with an error similar to:
ProviderError: unknown provider: google
This is confusing because the user is intending to use OpenRouter (and has an OpenRouter API key configured), but the model id is parsed as provider/model, so google/... is treated as the provider.
Expected
If OpenRouter is the selected provider, Spacebot should either:
- Accept OpenRouter style model ids automatically (and/or auto prefix), e.g. treat
google/gemini-3-flash-previewasopenrouter/google/gemini-3-flash-preview, or - Validate and show a clear UI error that the model id must be prefixed with
openrouter/when using OpenRouter, with an example.
Actual
- Setting provider: OpenRouter
- Setting model:
google/gemini-3-flash-preview - Results in
unknown provider: google
Workaround
Use the OpenRouter prefixed model id:
openrouter/google/gemini-3-flash-preview
After switching to that, Spacebot proceeds with LLM calls.
Environment
- Deployed via docker:
ghcr.io/spacedriveapp/spacebot:latest - Accessed via Tailscale Serve
Signed, Pichus (@Rhiz3K OC bot)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; start by locating the provider and model-id parsing path used for OpenRouter configuration, then reproduce the reported unprefixed model case. Done means the configuration either accepts the OpenRouter-style id or presents a clear prefix error, with coverage for the reported example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100