Troubleshooting
Startup Issues
| Symptom |
Cause |
Solution |
| Stuck on initialization |
Environment initializing |
Wait ~30s; restart if >2 min |
| Repeated startup failure |
Corrupted config |
Safe mode auto-triggers; rollback available |
| Window off-screen |
External display removed |
Auto-corrects to default position |
Login Issues
| Symptom |
Cause |
Solution |
| QR scan no response |
Network/auth service unreachable |
Check network |
| Frequent login loss |
Refresh token expired |
Re-scan QR code |
| No org models |
Org hasn’t configured policies |
Contact org admin |
Channel Issues
| Symptom |
Cause |
Solution |
| Bot not responding |
WS disconnected or group policy |
Check connection status; verify group enabled |
| @bot no response in group |
Group not enabled |
Right-click > Conversation settings > Enable |
| Approval card expired |
660s timeout |
Re-initiate the operation |
Model Issues
| Symptom |
Solution |
| Model unresponsive |
Settings > Models > Test connectivity |
| Image upload no recognition |
Configure image recognition fallback model |
| Thinking level unavailable |
Only reasoning models show the selector |
| Symptom |
Solution |
| IME input delay |
Check for large attachments rendering |
| Session switch flicker |
Check system reduced-motion setting |
| Memory growth over time |
Close unneeded sessions; restart app |
Diagnostics
Settings → About → Diagnostic Report generates an environment info report for support.
What to Include When Reporting an Issue
Providing these dramatically speeds up diagnosis:
- Diagnostic report: Settings → About → Diagnostic Report, one click
- Session ID: right-click the affected session in the sidebar → Rename; the ID in the dialog title is the session ID (also findable in the diagnostic report)
- Reproduction steps: what you did from launch to the error; stable repro is best, note frequency for intermittent issues
- Error screenshots: include the error card in the message stream, not just the popup
No need to worry about sensitive data: API keys and tokens in diagnostic reports and logs are masked—safe to share.
Log Location
When you need to inspect logs manually (e.g., support asks). Logs are a single JSONL file with structured events from the main process, kernel, and tool calls; API keys, tokens, and message bodies are all masked:
| OS |
Path |
| macOS/Linux |
~/.lanmate/agent/logs/ |
| Windows |
%USERPROFILE%\.lanmate\agent\logs\ |