When something goes wrong, check these common cases first.
Port in use, cannot start
- Check whether another Bi instance is already running
- Check whether the system firewall allows it
- Change the port in Settings
The UI shows an old version
The browser may have cached an old page. Force a reload:
- Windows:
Ctrl + Shift + R
- macOS:
Command + Shift + R
Chinese text is garbled
Output in the terminal panel is normally fine. Garbled text when running commands directly in a Windows console is usually a system character-encoding setting.
The agent waits for approval forever
By default every action needs your approval. If no prompt appears, check whether confirmation was disabled in Settings, or whether the operation was refused by an intercept rule.
Model errors or connection failures
- Check the Base URL, key and model name in Settings
- If one model is temporarily unavailable, switch to another
- With automatic selection, an unavailable model triggers a fallback to another available model
A session disappeared
Sessions are stored locally. Do not delete the .bi directory next to the application. Once a session is deleted it cannot currently be recovered; export important sessions as Markdown ahead of time — see Sessions.
Disk usage grows
Checkpoints accumulate over a conversation. Clean up old checkpoints from the artifacts panel when they are no longer needed — see Checkpoints and rollback.
Still stuck
Write down the following before asking for help:
- What you observed
- Steps to reproduce
- What you were doing at the time
Include these details, and never include your model keys.
