Get every team member through the DOSIA → ByteSpike loop in 5 minutes: install, switch to enterprise mode, enterprise SSO, auto-pick up allowed models, start chatting / vision / image generation.
When this applies: your organization already bought ByteSpike, your admin already created your lark account + topped up balance. You got this doc and in ~5 minutes you’ll be calling every Claude / GPT / Gemini / DeepSeek / Doubao model the admin has allowed.
After DOSIA launches, top menu: DOSIA → Settings (shortcut ⌘,).
2
Switch Deploy Mode
In the left nav click Deploy Mode, switch the mode from “Personal” to “Enterprise”.
3
Fill in the enterprise service URL
Paste the URL your admin gave you — the default is:
http://122.51.0.230:3012
(If your admin provided an internal-network address or a self-hosted domain, use what the admin said.)
4
Click Save
The blue “Save config” button at the bottom of the page. DOSIA will prompt you to restart — go ahead and restart.
That URL is the DOSIA enterprise web backend (apps/web deployment on Tencent Cloud), separate from the ByteSpike LLM Gateway (https://llm.bytespike.ai) — two services, different hosts, different ports. The backend handles ByteSpike config sync, lark OAuth proxy, and enterprise workspace management; the LLM Gateway handles the actual model calls. Employees don’t need to care about the distinction — admin gives you the URL, you fill it in.If the service URL changes and admin sends a new one, employees just update Settings → Deploy Mode → save. No reinstall needed.
Ask the admin to add your lark employee ID / email to the ByteSpike allowlist. The admin does this in console.bytespike.ai or in the lark group admin backend — you don’t have to do anything.
2
DOSIA triggers lark OAuth automatically
After restart, DOSIA detects enterprise mode and pops the lark authorization page automatically. The first time it opens the browser; once authorized you come back to DOSIA.
3
Logged in
The top-right corner of DOSIA should now show your lark avatar + email.
No lark authorization page appeared / stuck on “initializing”? Jump to Section 6 FAQ to investigate.
Pick a model at the top of the main chat box → type message → hit enter. Same interaction across vendors — the ByteSpike gateway routes automatically.
Vision (image input)
Drag an image into the chat box (or paste it). DOSIA calls the image-tools MCP’s analyze_image tool, which invokes a vision model to recognize the image.
Image generation
Ask for an image in the chat (“draw a cyberpunk cat”) — the agent calls the generate_image MCP tool, routing through Nano Banana / Seedream / GPT-Image, etc.
Video generation
Same idea as images — ask for “generate a video”, the agent calls generate_video MCP, routing through Sora 2 / Veo 3.1 / Seedance, etc.
Billing is transparent: each model call’s USD cost shows in the “credits” hint below the chat box. Failed calls (5xx / network errors) don’t bill.
Enterprise service URL is wrong → go back to Settings → Deploy Mode, double-check the URL, save again
Lark grant hasn’t taken effect → ask admin to confirm your employee ID is on the ByteSpike allowlist
SSO authorization expired → DOSIA Settings → My Account, click sign out then sign in again
Chat box says "insufficient balance"
The org wallet ran out. Screenshot + ask admin — once admin tops up at console.bytespike.ai/billing, it recovers immediately.
A specific model returns "permission denied" / "model not allowed"
Admin hasn’t granted your group access to that model. Ask admin to go to llm.bytespike.ai/admin → Users → your account → Allowed Models, and tick the matching model group.
Image / video generation tab is missing
Multimodal capability is granted separately (independent of text models). Once admin adds image / video capability to your group in console, DOSIA picks up the tool after a restart.
After lark authorization DOSIA freezes / loops on login
Clear DOSIA’s local state:
rm -rf ~/Library/Application\ Support/DOSIA/auth
Then relaunch DOSIA. If still broken, screenshot + DM the admin on lark.