Runtime FAQ
Issues you might hit while using Bom Agent day-to-day.
My CLI connection keeps dropping
- Expired CLI token — Settings → CLI priority → re-authenticate
- Network shift — corporate VPN/proxy may be blocking
- CLI self-update needed — Bom usually auto-updates but you can run manually
Memory usage is too high
- Settings → Tools — disable heavyweight tools you don't use (Blender, Fusion)
- Worker page — delete old threads
- Dashboard → "Clear Learned" — wipe accumulated memory
- Delete old logs in ~/.bom/logs/
Note
Typical resting usage is 400-600 MB. Take the steps above if you cross 1 GB.
Mobile app is not syncing
- Confirm the desktop Bom Agent is running (system tray)
- Check that Profile shows the same account on both sides
- Make sure mobile push permission is granted
- Verify your network is not blocking WebSocket connections
A Pack keeps failing
Packs auto-pause after 5 consecutive failures. Open the Pack on the Packs page and inspect its recent run logs. Common causes:
- CLI response timeout (default 120 s)
- Browser automation selector changed
- Input file format mismatch
- Missing capability declaration