Troubleshooting
This guide covers common issues with Calmo Local Bridge and how to resolve them.Connection Issues
Bridge Shows “DISCONNECTED”
Check Internet Connection
Check Internet Connection
Ensure your machine has internet access and can reach
app.getcalmo.com.Test with:Verify Server URL
Verify Server URL
The Server URL should be
https://app.getcalmo.com/ (default). If you’re using a custom deployment, verify the URL is correct.Restart the Bridge
Restart the Bridge
- Quit the bridge completely (don’t just close the window)
- Relaunch from Applications/Start Menu
- Try connecting again
Check Firewall/VPN
Check Firewall/VPN
Some firewalls or VPNs may block WebSocket connections. Try:
- Temporarily disabling the firewall
- Disconnecting from VPN
- Adding an exception for Calmo Bridge
Pairing Code Expired
Pairing codes expire after 10 minutes. If your code expired:- Go to app.getcalmo.com/integrations/bridge
- Click Generate New Code
- Enter the new code in the bridge app
Device Not Appearing in Web Interface
If your paired device doesn’t show as connected:- Check the bridge app shows a green status with device code
- Refresh the web page
- Click the refresh icon next to “Connected Devices”
- Try unpairing and re-pairing the device
”Enter Code” State Persists
If the bridge is stuck showing “ENTER CODE” after pairing:- Close and reopen the bridge window
- Check the Logs tab for error messages
- Try generating a new pairing code
Command Execution Issues
Command Hangs / No Response
Check Pending Commands
Check Pending Commands
The command might be waiting for approval. Check the Pending Commands section in the Bridge tab.
Command Timeout
Command Timeout
Some commands may time out if they take too long. For long-running operations:
- Use commands with built-in output streaming
- Consider breaking into smaller operations
Process Stuck
Process Stuck
If a command process is stuck:
- Check the Logs tab for errors
- The bridge may need to be restarted
”Command Not Found” Errors
-
Verify installation
-
Check PATH
The bridge inherits your shell’s PATH. Ensure the command is in your PATH:
-
Use full path
Ask Calmo to use the full path:
Permission Denied
- Check file/directory permissions
- Commands run with your user permissions—not root
- For operations requiring sudo, the bridge will need appropriate setup
Command Denied But You Didn’t Deny It
This can happen if:- The web session timed out
- You denied it from another browser tab
- The bridge lost connection during approval
MCP Server Issues
Server Won’t Start
Check command path
Check command path
Verify the executable exists:Use the full path in your config:
Verify npm package
Verify npm package
Ensure the package exists and can be installed:
Check logs
Check logs
Look at the Logs tab for specific error messages:
Server Connected But Shows 0 Tools
- Wait for initialization - Some servers take 10-30 seconds to load
- Check stderr - Server may have logged initialization errors
- Reload servers - Click Reload Servers in MCP Tools tab
- Verify package name - Ensure you have the correct npm package
HTTP Server Connection Failed
For HTTP MCP servers:- Check URL format - Include protocol (
https://) and full path - Verify API key - Ensure key is valid and has correct permissions
- Test endpoint
Windows: npx Not Working
On Windows, npx needs shell access. Wrap withcmd /c:
UI Navigation Issues
Can’t Find Command History
If you can’t locate past executed commands:- Check the Activity tab - Bottom panel has two tabs: Terminal and Activity
- Switch tabs - Click “Activity” to see command history
- Expand commands - Click the arrow next to any command to see full output
- Scroll - History may extend beyond visible area
Chat Interface Missing
If the chat panel isn’t visible:- Check right sidebar - Chat should be in the right-most panel
- Expand sidebar - Drag the divider if it’s collapsed
- Restart bridge - Close and reopen the application
- Check window size - Ensure window is wide enough to show all panels
Workspace Tree Collapsed
If you can’t see your workspace files:- Expand Workspaces section - Click the arrow next to “Workspaces” in left sidebar
- Expand folders - Click folder names to expand subfolders
- Check if workspaces added - “3 workspaces” should show at bottom of sidebar
- Add workspace - Click + button if no workspaces configured
Terminal Panel Not Showing
If you don’t see the terminal:- Check bottom panel - Terminal should be in the center-bottom area
- Click Terminal tab - Ensure “Terminal” tab is selected (not “Activity”)
- Resize - Drag the divider between editor and terminal to expand
- Toggle - Use Cmd/Ctrl+` to show/hide terminal
File Editor Won’t Open
If the file editor doesn’t appear:- Click a file - Select a file in the workspace tree
- Check center panel - Editor should open in the center-top area
- Look for tabs - File name should appear in a tab
- Close other tabs - If too many tabs open, close some with ×
Terminal Issues
Terminal Output Not Showing
If commands execute but output doesn’t appear:- Check Terminal tab - Ensure you’re on “Terminal” (not “Activity”)
- Scroll down - Output might be below the visible area
- Wait for completion - Some commands take time before showing output
- Check Activity tab - Full output is always saved there
Command Stuck in Terminal
If a command seems frozen:- Check pending approval - Look at Command Approval panel (top right)
- Approve the command - Click Allow/Deny/Always
- Long-running process - Some commands (like
npm install) take time - Interactive prompt - Command might be waiting for input
Terminal Colors/Formatting Broken
If terminal output lacks colors or formatting:- Restart bridge - Close and reopen to reset terminal
- Check command - Some commands don’t use colors
- Environment - Ensure TERM environment variable is set
Can’t Scroll Terminal Output
If terminal output is cut off:- Use scroll bar - Right side of terminal panel
- Resize panel - Drag divider to make terminal larger
- Check Activity tab - Full output always available there
- Copy output - Click copy icon to get full text
File Editor Issues
Can’t Edit Files
If file editor is read-only or won’t save changes:- Check permissions - Ensure file is writable
- Verify workspace - File must be in a configured workspace
- Check file type - Binary files show preview instead of editor
- Restart bridge - Close and reopen the application
File Changes Not Saving
If edits don’t persist:- Save manually - Press Cmd/Ctrl+S
- Check disk space - Ensure you have free space
- Verify write permissions - File might be read-only
- Look for errors - Check Activity Log for save errors
File Changes Not Reflected
If saved changes aren’t visible:- Check auto-save - Changes should save automatically
- Refresh file - Close tab and reopen from workspace tree
- Check external edits - Another program may have modified it
- Verify save - Look for unsaved indicator (• dot in tab)
Syntax Highlighting Not Working
If code appears without colors:- Check file extension -
.js,.py,.yamletc. trigger highlighting - Reopen file - Close tab and open again
- Language detection - Some files may not be auto-detected
- Restart bridge - Reload language parsers
Too Many Tabs Open
If editor becomes cluttered:- Close tabs - Click × on each tab or Cmd/Ctrl+W
- Close all - Right-click any tab → Close All
- Close others - Right-click → Close Others
- Restart bridge - Clears all tabs on reopen
Workspace Issues
Workspace Not Appearing
If workspace doesn’t show in sidebar after adding:- Check permissions - Ensure directory is readable
- Refresh - Click refresh icon or restart bridge
- Verify path - Confirm directory exists
- Check logs - Activity Log may show errors
Can’t Add Workspace
If the Add Workspace dialog won’t accept a directory:- Check path - Ensure directory exists
- Permissions - You must have read access
- Already added - Check “Current Workspaces” list for duplicates
- Path length - Very long paths may cause issues
Files Not Visible in Tree
If workspace is added but files don’t appear:- Expand folder - Click arrow next to workspace name
- Permissions - Ensure read access to subdirectories
- Hidden files - Dot-files may not show
- Refresh - Restart bridge to reload file tree
Wrong Files Showing
If unexpected files appear in workspace:- Check workspace path - May have added parent directory
- Remove and re-add - Delete workspace and add correct path
- Git ignore - Some files may be filtered
Installation Issues
macOS: Terminal Features Not Working
If terminal functionality isn’t working after installation on macOS:Missing Build Tools
Missing Build Tools
The bridge requires XCode Command Line Tools for terminal support:Follow the prompts to complete installation, then restart the bridge.
Architecture Mismatch
Architecture Mismatch
On Apple Silicon (M1/M2/M3), ensure you’re running the native ARM64 version:
- Quit the bridge
- Download the latest
.dmgfrom the web interface - Look for
arm64oruniversalin the filename - Reinstall and restart
Reinstall
Reinstall
Sometimes a clean reinstall fixes native module issues:
- Quit the bridge completely
- Delete from Applications folder
- Clear application data:
- Download and reinstall from the web interface
Windows: Bridge Won’t Start
If the bridge fails to launch on Windows:Missing Runtime
Missing Runtime
Windows requires Visual C++ Redistributable:
- Download from Microsoft
- Install the package
- Restart your computer
- Launch the bridge again
Antivirus Blocking
Antivirus Blocking
Some antivirus software blocks native modules:
- Add an exception for
Calmo Bridge.exe - Allow network connections for the application
- Restart the bridge
Linux: Terminal Commands Fail
On Linux, ensure you have basic build tools installed:Workspace Issues
Workspace Not Accessible
If commands fail in a configured workspace:-
Verify path exists
- Check permissions - Ensure you have read access to the directory
- Remove and re-add - Delete the workspace and add it again
Changes Not Reflected
If file changes aren’t visible:- Calmo doesn’t cache workspace contents
- Changes should be immediately available
- Try running
lsin the workspace to verify
Performance Issues
Bridge Using High CPU
- Check running processes - A command might still be running
- Clear logs - Large log history can impact performance
- Restart bridge - May clear accumulated state
Slow Command Execution
- Check network latency - Commands route through the server
- Simplify commands - Break complex operations into steps
- Limit output - Use flags like
--tail=100to limit log output
Memory Usage High
- Clear command history - Click Clear in the Bridge tab
- Clear logs - Click Clear in the Logs tab
- Restart bridge - Releases accumulated memory
Browser Issues
Safari/Brave Compatibility
Safari and Brave have limited WebSocket support. For best experience:- Use Chrome, Firefox, or Edge
- Ensure browser is up to date
Commands Not Appearing in Chat
If approved commands don’t show results in the chat:- Check the browser console for errors
- Refresh the Calmo web page
- Verify the bridge still shows “Connected”
Recovery Steps
Full Reset
If nothing else works:-
Quit bridge completely
- macOS: Right-click menu bar icon → Quit
- Windows: Right-click tray icon → Exit
-
Clear configuration (optional)
-
Reinstall bridge
- Download fresh from the web interface
- Reinstall the application
-
Pair again
- Generate new pairing code
- Complete pairing process
Unpair and Re-pair
- Go to app.getcalmo.com/integrations/bridge
- Find your device under “Connected Devices”
- Click the delete icon to remove it
- Generate a new pairing code
- Enter the code in your bridge app
Getting Help
Information to Provide
When contacting support, include:- Bridge version - Shown in the app title bar
- Operating system - macOS/Windows version
- Error messages - Copy from Logs tab
- Steps to reproduce - What you were doing when it failed
Log Export
Copy relevant logs from the Logs tab to share with support.Contact Support
Email: [email protected] Include:- Description of the issue
- Screenshots if applicable
- Relevant log excerpts
For additional help, contact our support team at [email protected].