Chat App
Troubleshooting
Troubleshooting
This guide covers common issues you may encounter when using the Chat App and how to resolve them.
Common Issues
Issue: No Response from AI
Symptoms:
- Message sends but no response appears
- Streaming indicator spins indefinitely
- Connection seems to hang
Cause: Usually caused by API key issues, network problems, or provider service outages.
Solution:
- Verify your API key is correctly configured for the selected provider
- Check your network connection
- Verify the provider's service status:
- For LM Studio, ensure the application is running and the model is loaded
- Try switching to a different provider or model
Issue: Streaming Stops Mid-Response
Symptoms:
- Response starts streaming but stops unexpectedly
- Partial message appears then freezes
- No error message displayed
Cause: May be caused by token limits, network interruption, or server-side errors.
Solution:
- Wait a few moments - the stream may resume
- If using max tokens setting, try increasing the limit
- Refresh the page and the partial message should be saved
- Try sending a shorter prompt to avoid token limits
- Check if the provider is experiencing issues
Issue: LM Studio Not Connecting
Symptoms:
- LM Studio option shows but doesn't work
- "Connection refused" or timeout errors
- Model selection dropdown is empty for LM Studio
Cause: LM Studio server may not be running or is on a different port.
Solution:
- Open LM Studio application on your computer
- Load a model in LM Studio
- Start the local server (usually runs on
http://localhost:1234) - Verify the server is running by visiting the URL in your browser
- Check that no firewall is blocking the connection
Issue: Conversations Not Saving
Symptoms:
- Conversations disappear after page refresh
- Messages are lost
- New conversation button creates duplicates
Cause: Database connection issues or sync problems.
Solution:
- Check your browser's console for RxDB errors
- Verify you're logged into the correct organization/workspace
- Try clearing browser cache and local storage (last resort - may lose local data)
- Ensure the RxDB server is running if replication is enabled
- Check if you have sufficient storage space in the browser
Issue: Tool Calls Failing
Symptoms:
- Tool call indicators show error state (red border)
- AI mentions using a tool but results don't appear
- Tool execution hangs in "pending" state
Cause: MCP Gateway connection issues or tool configuration problems.
Solution:
- Verify MCP Gateway is running and accessible
- Check that the required tools are registered with the gateway
- Look at the expanded tool call details for specific error messages
- Ensure you have permissions to execute the requested tools
- Try refreshing tools by restarting the conversation
Issue: Markdown Not Rendering Correctly
Symptoms:
- Code blocks appear as plain text
- Markdown syntax is visible instead of formatted
- Syntax highlighting not working
Cause: May be a browser compatibility issue or rendering library problem.
Solution:
- Ensure you're using a supported browser (Chrome, Firefox, Safari, Edge)
- Try refreshing the page
- Check if the issue persists in a different browser
- Report the issue with the specific markdown content that fails
Issue: Model Selector Not Showing All Models
Symptoms:
- Expected models are missing from dropdown
- Only one provider appears
- Dropdown is empty
Cause: Missing API keys or configuration for certain providers.
Solution:
- Verify API keys are configured for all desired providers
- Check that keys have the correct permissions
- For enterprise accounts, ensure your plan includes the models you need
- LM Studio models only appear when the server is running
Performance Issues
Issue: Slow Response Times
Symptoms:
- Long delays before streaming starts
- Responses take much longer than expected
- Interface feels sluggish
Cause: Network latency, model choice, or prompt complexity.
Solution:
- Try a faster model (e.g., Claude Haiku instead of Claude Opus)
- Check your internet connection speed
- Reduce prompt length if possible
- For LM Studio, ensure your hardware can handle the loaded model
- Consider using a wired connection instead of WiFi
Getting Help
If you can't resolve your issue: