Troubleshooting
Fix common Arc0 issues including connection drops, pairing failures, missing notifications, agent detection problems, and CLI errors.
Connection Issues
Can't Pair Devices
Symptom: QR code scan fails or pairing times out.
Solutions:
- Internet access: Ensure both devices have internet connectivity
- Fresh code: QR codes expire after 5 minutes—run
arc0 pairagain - Camera permissions: Ensure the app has camera access
- CLI running: Verify Arc0 CLI is running
# Check CLI status
arc0 status
# Generate new pairing code
arc0 pairConnection Drops
Symptom: App shows "Disconnected" intermittently.
Solutions:
- Network stability: Switch to a more stable network
- Battery optimization: Disable battery optimization for Arc0 (Android)
- Background app refresh: Enable for Arc0 (iOS)
- Restart CLI: Stop and restart Arc0 CLI
# Restart CLI
arc0 stop
arc0 startTunnel Connection Issues
Symptom: WebSocket tunnel not connecting.
Solutions:
- Check internet: Both devices need internet access
- Firewall: Ensure outbound WebSocket connections aren't blocked
- Restart: Restart both CLI and mobile app
- Re-pair: Try pairing again with a fresh QR code
Notification Issues
Not Receiving Notifications
Symptom: Agent asks questions but no push notification.
Solutions:
- Check app permissions: Ensure notifications are enabled in device settings
- Check CLI config: Verify notifications are enabled
notifications:
enabled: true
on_question: true- Focus mode: Check iOS Focus or Android DND isn't blocking Arc0
- Connection: Verify app shows "Connected" status
- Battery saver: Disable battery optimization (Android)
Delayed Notifications
Symptom: Notifications arrive late.
Solutions:
- Background refresh: Enable background app refresh
- Battery optimization: Disable (Android)
- Network: Check for high latency networks
- Debounce setting: Reduce notification debounce time
performance:
notification_debounce: 500 # ms, default is 1000Too Many Notifications
Symptom: Getting notifications for everything.
Solutions:
- Filter notification types:
notifications:
on_question: true
on_error: true
on_diff: false # Disable diff notifications
on_complete: false # Disable completion notifications- Set quiet hours:
notifications:
quiet_hours:
enabled: true
start: '22:00'
end: '08:00'Agent Issues
Agent Not Detected
Symptom: Running agent in tmux but nothing shows in app.
Solutions:
- Verify tmux: Agent must be running inside a tmux session
- Check CLI is running: Arc0 CLI must be active
- Custom pattern: For unknown agents, add detection pattern
agents:
- name: 'my-agent'
pattern: 'my-agent-binary'- Check logs:
arc0 logs --tail 50Questions Not Detected
Symptom: Agent asks questions but Arc0 doesn't notify.
Solutions:
- Check question patterns: Arc0 may not recognize the format
- Add custom patterns:
agents:
- name: 'claude'
question_patterns:
- "\\?$"
- '^Should I'
- '^Do you want'
- '^Please (confirm|choose)'- Enable verbose logging:
arc0 start --log-level debugDiffs Not Showing
Symptom: Agent modifies files but diff viewer is empty.
Solutions:
- Check diff format: Arc0 expects standard unified diff format
- Add diff patterns:
agents:
- name: 'my-agent'
diff_patterns:
- '^diff --git'
- "^\\+\\+\\+ "
- '^--- 'App Issues
App Crashes
Symptom: Arc0 app closes unexpectedly.
Solutions:
- Update app: Ensure you have the latest version
- Clear cache: Settings → Clear Cache
- Reinstall: Delete and reinstall the app
- Report bug: Contact support with crash details
Diff Viewer Slow
Symptom: Large diffs take long to render.
Solutions:
-
Reduce context lines:
Settings → Diff Viewer → Context Lines → 3
-
Use unified view: Split view is more memory intensive
-
Clear cache: Large cached diffs can slow things down
Session History Missing
Symptom: Old sessions not appearing.
Solutions:
- Check retention settings:
storage:
session_retention: 30d # Increase retention- Sync status: Some sessions may not have synced
- Storage space: Ensure device has free space
CLI Issues
CLI Won't Start
Symptom: arc0 start fails or exits immediately.
Solutions:
- Check port availability:
lsof -i :3847If in use, change the port:
arc0 start --port 3848- Check logs:
cat ~/.arc0/arc0.log-
Permissions: Ensure you have write access to
~/.arc0/ -
Node version: Requires Node 18+ (for npm install)
node --versionHigh CPU/Memory Usage
Symptom: CLI using excessive resources.
Solutions:
- Check for runaway sessions: Multiple active sessions can add up
arc0 sessions- Reduce logging:
log_level: 'warn' # Reduce from debug/info- Limit history:
performance:
max_history: 500 # Reduce from default 1000Permission Denied Errors
Symptom: Can't write config or logs.
Solutions:
- Check directory ownership:
ls -la ~/.arc0- Fix permissions:
sudo chown -R $USER ~/.arc0
chmod 755 ~/.arc0Getting Help
If you can't resolve an issue:
- Check logs:
arc0 logs --since 1h > debug.log-
Search issues: GitHub Issues
-
Open issue: Include:
- Arc0 version (
arc0 --version) - OS and version
- Agent being used
- Steps to reproduce
- Relevant logs
- Arc0 version (
-
Join Discord: Community Discord