-
Notifications
You must be signed in to change notification settings - Fork 18
Troubleshooting
This guide covers common issues and their solutions when using Claude Autopilot.
Before diving into specific issues, run through this quick checklist:
- ✅ VS Code Version: Ensure you're running VS Code 1.74.0 or later
- ✅ Claude Autopilot Version: Check you have the latest version installed
- ✅ Dependencies: Verify Claude Code and Python are installed and accessible
- ✅ Permissions: Check if Claude Autopilot has necessary permissions
- ✅ Configuration: Review your Claude Autopilot settings for any invalid values
Symptoms:
- Error message: "Claude CLI not found in PATH"
- Dependency check fails
- Cannot start Claude session
Solutions:
# Test if Claude is accessible
claude --version
# If not found, check your PATH
echo $PATH # macOS/Linux
echo $env:PATH # Windows PowerShellmacOS/Linux:
# Add to ~/.bashrc, ~/.zshrc, or ~/.profile
export PATH="/path/to/claude:$PATH"
# Reload shell configuration
source ~/.bashrc # or ~/.zshrcWindows:
- Open System Properties → Advanced → Environment Variables
- Edit PATH variable
- Add Claude installation directory
- Restart VS Code and terminal
- Uninstall current Claude Code installation
- Download latest version from official source
- Restart VS Code after installation
Symptoms:
- Error message: "Python not found"
- PTY wrapper fails to start
- Session initialization errors
Solutions:
# Check Python availability
python --version
python3 --version
# Check which Python Claude Autopilot is trying to use
which python # macOS/Linux
where python # WindowsmacOS:
# If using Homebrew Python
export PATH="/opt/homebrew/bin:$PATH"
# If using system Python
export PATH="/usr/bin:$PATH"Windows:
- Reinstall Python with "Add Python to PATH" checked
- Or manually add Python to PATH in System Properties
- Restart VS Code
Linux:
# Install Python if missing
sudo apt install python3 python3-pip # Ubuntu/Debian
sudo dnf install python3 python3-pip # FedoraSymptoms:
- "Permission denied" when starting Claude
- Cannot create queue files
- Workspace access issues
Solutions:
{
"claudeAutopilot.session.skipPermissions": true
}macOS/Linux:
# Fix workspace permissions
chmod -R 755 /path/to/your/workspace
# Fix Claude Autopilot data directory
chmod -R 755 ~/.vscode/extensions/benbasha.claude-loop-*Windows:
- Run VS Code as Administrator (temporary solution)
- Check folder permissions in Properties → Security
- Ensure your user has full control
Symptoms:
- Queue shows "Processing" but no progress
- Messages remain in "pending" state
- No output generated
Solutions:
- Open Claude Autopilot panel
- Check process status indicator
- Look for error messages in output
- Stop Claude Autopilot:
Claude: Stop Claude Autopilot - Wait 5 seconds
- Start Claude Autopilot:
Claude: Start Claude Autopilot
# Navigate to workspace
cd /path/to/your/workspace
# Remove queue state files
rm -rf .vscode/claudeloop-*- Monitor CPU and memory usage
- Ensure sufficient disk space
- Close unnecessary applications
Symptoms:
- Queue stops after hitting Claude limits
- No automatic resumption
- Manual restart required
Solutions:
{
"claudeAutopilot.session.autoStart": true,
"claudeAutopilot.queue.autoMaintenance": true
}# Test internet connection
ping google.com
# Test Claude API accessibility (if applicable)
curl -I https://api.anthropic.com- Check your Claude usage dashboard
- Verify limit reset times
- Ensure you have remaining quota
Symptoms:
- VS Code becomes slow
- System memory consumption high
- Extension host crashes
Solutions:
{
"claudeAutopilot.queue.maxSize": 100,
"claudeAutopilot.queue.maxMessageSize": 25000,
"claudeAutopilot.queue.maxOutputSize": 50000
}{
"claudeAutopilot.queue.autoMaintenance": true,
"claudeAutopilot.queue.retentionHours": 6
}- Open Claude Autopilot panel
- Go to History tab
- Clear old runs manually
Symptoms:
- Settings don't take effect
- Invalid configuration warnings
- Extension fails to load
Solutions:
- Open VS Code Settings
- Search for "Claude Autopilot"
- Check for red error indicators
// Remove all Claude Autopilot settings from settings.json
// Let extension use defaultsEnsure your settings.json has valid JSON syntax:
{
"claudeAutopilot.developmentMode": true, // ✅ Valid
"claudeAutopilot.queue.maxSize": 500 // ✅ No trailing comma
}# If Claude is blocked by Gatekeeper
sudo spctl --add /path/to/claude
sudo xattr -r -d com.apple.quarantine /path/to/claude# Update certificates
/Applications/Python\ 3.x/Install\ Certificates.command# Check current policy
Get-ExecutionPolicy
# Set policy if needed (run as Administrator)
Set-ExecutionPolicy RemoteSigned- Add Claude and Python to Windows Defender exclusions
- Add VS Code extensions folder to exclusions
# Ubuntu/Debian
sudo apt install build-essential python3-dev
# Fedora
sudo dnf groupinstall "Development Tools"
sudo dnf install python3-devel# Check SELinux status
sestatus
# Temporarily disable if needed
sudo setenforce 0{
"claudeAutopilot.developmentMode": true,
"claudeAutopilot.logging.enabled": true,
"claudeAutopilot.logging.level": "debug"
}- Open Command Palette (
Cmd/Ctrl+Shift+P) - Run:
Developer: Toggle Developer Tools - Go to Console tab
- Look for Claude Autopilot-related errors
macOS/Linux:
# VS Code logs
~/Library/Application\ Support/Code/logs/ # macOS
~/.config/Code/logs/ # Linux
# Extension logs (if logging enabled)
find ~/.vscode/extensions -name "*claude-loop*" -type dWindows:
# VS Code logs
%APPDATA%\Code\logs\
# Extension directory
%USERPROFILE%\.vscode\extensions\-
Uninstall Extension:
code --uninstall-extension benbasha.claude-loop
-
Clear Extension Data:
# Remove extension data rm -rf ~/.vscode/extensions/benbasha.claude-loop-* # Clear workspace data find . -name ".vscode" -type d -exec rm -rf {}/claudeloop-* \;
-
Reinstall Extension:
code --install-extension benbasha.claude-loop
Causes:
- Large message sizes
- Complex processing tasks
- System resource constraints
Solutions:
- Break large messages into smaller chunks
- Increase health check interval
- Close unnecessary applications
- Upgrade system resources if possible
Immediate Actions:
- Kill VS Code process
- Restart VS Code
- Disable Claude Autopilot temporarily
Long-term Solutions:
- Reduce queue size limits
- Enable auto-maintenance
- Monitor system resources
- Update VS Code and Claude Autopilot
| Error Code | Description | Solution |
|---|---|---|
CLAUDE_NOT_FOUND |
Claude CLI not in PATH | Install Claude, fix PATH |
PYTHON_NOT_FOUND |
Python not accessible | Install Python, fix PATH |
PERMISSION_DENIED |
Insufficient permissions | Enable skip permissions |
QUEUE_FULL |
Queue size limit reached | Increase maxSize or enable auto-maintenance |
SESSION_FAILED |
Claude session failed | Restart session, check dependencies |
PROCESS_TIMEOUT |
Operation timed out | Check system resources, increase timeouts |
- Review this troubleshooting guide
- Check Known Issues
- Search GitHub Issues
- Enable debug logging and collect logs
Include the following information:
System Information:
- OS and version
- VS Code version
- Claude Autopilot version
- Claude Code version
- Python version
Error Details:
- Exact error message
- Steps to reproduce
- Expected vs actual behavior
- Screenshots or logs
Configuration:
- Relevant Claude Autopilot settings
- Workspace configuration
- Environment variables
- GitHub Issues - Bug reports and feature requests
- GitHub Discussions - Questions and community support
- FAQ - Common questions and answers
If Claude Autopilot is completely broken:
-
Stop all Claude Autopilot processes:
# Kill any hanging processes pkill -f claude pkill -f python.*claude
-
Remove all data:
# Remove extension data rm -rf ~/.vscode/extensions/benbasha.claude-loop-* # Remove workspace data find . -name ".vscode" -type d -exec rm -rf {}/claudeloop-* \;
-
Reset VS Code:
# Close VS Code # Clear VS Code cache (optional) rm -rf ~/.vscode/extensions/extensions.json
-
Reinstall:
code --install-extension benbasha.claude-loop
Troubleshooting guide last updated: July 2025