Connection Issues
Bridge Not Connecting to Factory
1
Verify Bridge is Running
First, check if Factory Bridge is running on your system:
- Look for the Factory Bridge icon in your system tray or menu bar
- If not visible, try launching Factory Bridge again from your applications folder
2
Check Pairing Code
Verify you’ve entered the correct pairing code:
- The pairing code should be 6 digits
- Make sure you’re using the most recent code shown in Factory
- Try generating a new pairing code in Factory
3
Restart Factory Bridge
If the connection still fails:
- Right-click the Factory Bridge icon in your system tray
- Select “Quit”
- Launch Factory Bridge again
- Enter the pairing code when prompted
4
Check Session Limit
Factory Bridge currently supports up to 6 concurrent connections:
- Close some Factory tabs if you have many open
- Try connecting from a new Factory session
If you’ve recently updated Factory Bridge, you may need to restart your computer for all changes to take effect.
Connection Drops Unexpectedly
Network Issues
Network Issues
Network connectivity problems can cause connection drops:
- Check your internet connection
- Ensure your firewall isn’t blocking Factory Bridge
- If using a VPN, verify it’s not interfering with the connection
- Try switching to a different network if possible
System Sleep/Hibernation
System Sleep/Hibernation
System sleep or hibernation can disconnect Factory Bridge:
- Check your system’s power settings
- Adjust sleep settings to prevent disconnections during active use
- Reconnect Factory Bridge after waking your computer
Factory Bridge Crashed
Factory Bridge Crashed
If Factory Bridge has crashed:
- Check if the Factory Bridge icon is still in your system tray
- If not, relaunch Factory Bridge
- Check system logs for error messages
- If crashes persist, try reinstalling Factory Bridge
Command Execution Problems
Commands Not Executing
1
Verify CLI Tools Are Available
Make sure you can see the CLI tools in Factory:
- Ensure you’re using Droid Mode (select from the model dropdown)
- Check if the MCP Bridge feature flag is enabled
- Refresh your Factory session
2
Check Command Format
Ensure your commands are formatted correctly:
- Verify the syntax of your commands
- Check that you’re providing all required parameters
- Make sure paths don’t contain special characters that need escaping
3
Check Working Directory
Ensure the specified working directory exists and is accessible:
- Try using an absolute path instead of a relative path
- Verify you have permission to access the directory
- Check for typos in the directory path
Command Returns Error
Command Not Found
Command Not Found
If you see “command not found” errors:
- Verify the command is installed on your system by trying it directly in a terminal
- Check if the command is in your system PATH
- Use the full path to the executable instead of just the command name
- For environment-specific commands, ensure you’re running in the correct environment
Permission Denied
Permission Denied
If you see “permission denied” errors:
- Check if you have permission to run the command
- For scripts, ensure they have executable permissions (
chmod +x script.sh) - Verify you have access to any files or directories the command is trying to access
- For operations requiring elevated privileges, you may need to use
sudo(with caution)
Incorrect Working Directory
Incorrect Working Directory
If the command is running in the wrong location:
- Specify an absolute path for the working directory
- Verify the directory exists before running the command
- Use
pwdcommand to check the current working directory
Process Management Issues
Can’t Find Process ID (PID)
1
Locate Process Information
When a process is started through Factory Bridge, the PID is returned in the response:Look for this information in Factory’s response after starting a process.
2
Check If Process Is Still Running
Verify if the process is still running:If the process has already terminated, you’ll need to start a new one.
Process Terminates Unexpectedly
Application Error
Application Error
The application may have encountered an error:
- Check the output for error messages
- Run the command with verbose or debug flags if available
- Try running the command directly in a terminal to see if it behaves differently
Resource Limitations
Resource Limitations
The process might be terminating due to resource constraints:
- Check if your system has sufficient memory and CPU
- Look for “out of memory” errors in the output
- Consider closing other applications to free up resources
Dependency Issues
Dependency Issues
Missing or incompatible dependencies can cause processes to terminate:
- Verify all required dependencies are installed
- Check version compatibility
- Look for dependency-related errors in the output
Installation Issues
Installation Fails
Insufficient Permissions
Insufficient Permissions
You may not have sufficient permissions to install Factory Bridge. On macOS, make sure you have permission to install applications
System Incompatibility
System Incompatibility
Your system may not meet the requirements:
- Check that your operating system version is supported
- Verify your system meets the minimum requirements
- Look for specific error messages that might indicate compatibility issues
Factory Bridge Won’t Start
1
Check System Resources
Ensure your system has sufficient resources:
- Check available memory and disk space
- Close unnecessary applications
- Restart your computer to free up resources
2
Look for Error Messages
Check for error messages:
- Look for error dialogs when launching Factory Bridge
- Check system logs for error messages
- On macOS, check Console.app for related errors
- On Windows, check Event Viewer for application errors
3
Reinstall Factory Bridge
If all else fails, try reinstalling:
- Uninstall Factory Bridge completely
- Download a fresh copy of the installer
- Install Factory Bridge again
- Restart your computer after installation
Feature Availability Issues
Missing CLI Tools
Terminal toolkit is not enabled
Terminal toolkit is not enabled
Terminal tools are only available in Droid Mode:
- Open the “Toolkits” selector inside of the chatbox input
- Select the “Terminal” toolkit
- Retry an existing message or send a new one
Version Mismatch
Version Mismatch
Your Factory Bridge version may not be compatible with the Factory platform:
- Check for Factory Bridge updates
- Download and install the latest version
- Restart Factory Bridge after updating
Session Limit Reached
1
Understand the Limit
Factory Bridge currently supports up to 6 concurrent connections due to network protocol limitations.
2
Close Unused Sessions
If you’ve reached the limit:
- Close unused Factory tabs or sessions
- Wait a few minutes for connections to fully close
- Try connecting again with a new session
3
Restart Factory Bridge
If closing sessions doesn’t help:
- Restart Factory Bridge completely
- This will reset all connections
- Reconnect with your most important session first
Advanced Troubleshooting
Check Factory Bridge Logs
Locating Log Files
Locating Log Files
Factory Bridge logs can provide valuable troubleshooting information:
- macOS: Look in
~/Library/Logs/Factory\ Bridge
bridge-YYYY-MM-DD.log or similar.Share Logs
Share Logs
Reset Factory Bridge
If you’re experiencing persistent issues, you can try resetting Factory Bridge:1
Quit Factory Bridge
First, completely close Factory Bridge:
- Right-click the Factory Bridge icon in your system tray
- Select “Quit” or “Exit”
- Verify the application has fully closed
2
Clear Configuration
Clear Factory Bridge configuration files: Delete
~/Library/Application Support/Factory Bridge3
Restart Factory Bridge
Restart Factory Bridge:
- Launch Factory Bridge from your applications folder
- You’ll be prompted to enter a new pairing code
- Enter the pairing code from Factory
Getting Additional Help
If you’re still experiencing issues after trying these troubleshooting steps, here are some ways to get additional help:Report an Issue
Report bugs or issues with Factory Bridge:
- Gather relevant error messages and logs
- Take screenshots of the issue if applicable
- Document the steps to reproduce the problem
- Contact Factory support with this information at support@factory.ai
Factory Bridge CLI Tools Reference
For detailed information on all available CLI tools, refer to the Factory Bridge CLI Tools Reference