- Personal mode — install DOSIA, paste your own
sk-byts-...key, pick models. This page covers that path. - Enterprise mode — admin pre-provisions you via lark SSO, DOSIA auto-picks up the allowed model set, no manual key. See Employee onboarding for the enterprise flow.
Install
- macOS
- Windows / Linux
Download the latest dmg from
github.com/leave1206/dosia-releases:
- Apple Silicon (M1/M2/M3/M4):
DOSIA-x.y.z-arm64.dmg - Intel:
DOSIA-x.y.z.dmg
/Applications, then launch.Personal mode setup
Get a ByteSpike key
console.bytespike.ai/keys → Create key.
Pick the routing group based on what you want DOSIA to reach (
claude-default for Claude, gemini-default for Gemini, or default to route everything).
See Models for the group-vs-model map.Stay in Personal mode
Deploy Mode stays on Personal (the default). Enterprise mode is for SSO-managed accounts — see Employee onboarding if your admin gave you a backend URL.
Add ByteSpike as a provider
Settings → AI Models → Add Provider → “ByteSpike”.
DOSIA will hit
| Field | Value |
|---|---|
| Base URL | https://llm.bytespike.ai |
| API key | your sk-byts-... |
| Protocol | Anthropic Messages (or OpenAI Chat Completions — either works against the same key) |
/v1/models against ByteSpike to fetch the
list of models your key can actually reach. Wait a couple seconds
for the dropdown to populate.What works in DOSIA
| Feature | Backed by |
|---|---|
| Text chat | All text models (Claude / GPT / Gemini / DeepSeek / Kimi / GLM / MiniMax / Doubao) |
| Vision (drag image into chat) | DOSIA’s analyze_image MCP tool calls a vision model (Claude / GPT-5-4 / Gemini) |
| Image generation (“draw a …”) | generate_image MCP tool routes to Nano Banana / Seedream / GPT-Image |
| Video generation (“generate a video of …”) | generate_video MCP tool routes to Sora / Veo / Seedance |
| Agent (multi-step task) | DOSIA’s agent loop calls tool_use / function calling across providers |
| MCP plugins | DOSIA bundles 9 official plugins (Lark, browser automation, meeting analysis, knowledge base, etc.) — see github.com/leave1206/dosia-plugins |
Switching models
Each chat thread remembers the model it was opened with. Switch at the top of the chat box — the dropdown shows every model your key can reach. Image / video model picks happen inside the respective tool calls; you don’t need to set them per-thread.Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| ”Failed to fetch models” after adding provider | Key invalid or wrong group | Copy a fresh key from console; confirm group serves the models you expected |
| Model dropdown empty | Key has 0 allowed models | Check the key’s group_id in console; pick a non-empty group |
| Image / video tool button greyed out | The MCP plugin isn’t enabled in DOSIA settings | Settings → MCP → enable image-tools / video-tools |
| Vision drag-drop returns 400 | The chosen text model doesn’t support image input | Switch the chat to claude-sonnet-4-6, gpt-5-4, or gemini-3-1-pro |
| ”insufficient_balance” | Key (or org wallet) is out of credits | Top up at console.bytespike.ai/billing |
| Slow first token | Cold start on a cross-protocol translation route | Warm with a small request first, or stick to a native protocol for hot path |
Enterprise mode (lark SSO)
If your company runs DOSIA centrally: admin provisions the enterprise backend URL, DOSIA flips into Enterprise mode, lark SSO logs you in, the allowed model set syncs automatically — no per-user key. The full setup is in Employee onboarding. The admin side (granting employees, monitoring usage, configuring allowed groups) is documented in Admin operations.Next
Employee onboarding
Enterprise / SSO path.
DOSIA Agent mode
How DOSIA’s agent loop picks models per step.
MCP integration
The bridge between DOSIA’s tool plugins and the model side.
Configure your client
Wire any other client (Claude Code / Codex / Cursor / SDK).