Cmd+Ctrl

Appearance

Troubleshooting ​

Common issues and solutions for Cmd+Ctrl.

Connection Issues ​

Daemon won't connect ​

Symptoms: cmdctrl-claude-code status shows "Disconnected" or daemon fails to start.

Solutions:

  1. Check registration

    bash
    cmdctrl-claude-code status

    If not registered, run cmdctrl-claude-code register -s https://api.cmd-ctrl.ai

  2. Check network connectivity

    bash
    curl -I https://api.cmd-ctrl.ai/health

    Should return HTTP 200.

  3. Check for firewall issues

    • Ensure outbound HTTPS (port 443) is allowed
    • Ensure WebSocket connections are not blocked

  4. Re-register the device

    bash
    cmdctrl-claude-code unregister
cmdctrl-claude-code register -s https://api.cmd-ctrl.ai

Device shows offline in app ​

Symptoms: Device is registered but shows as offline in the web/mobile app.

Solutions:

  1. Verify daemon is running

    bash
    cmdctrl-claude-code status

  2. Restart the daemon

    bash
    cmdctrl-claude-code stop
cmdctrl-claude-code start

  3. Check logs

    bash
    # If running as a service
tail -f /tmp/cmdctrl-claude-code.log

Authentication Issues ​

"Not registered" error ​

Run the registration command:

bash
cmdctrl-claude-code register -s https://api.cmd-ctrl.ai

OAuth login fails ​

  1. Clear browser cookies for cmd-ctrl.ai
  2. Try a different browser - some browser extensions block OAuth
  3. Check popup blockers - OAuth may open in a new window

Device code expired ​

Device codes expire after 15 minutes. Run register again to get a new code.

Agent Issues ​

Claude Code not found ​

Symptoms: "Claude not found" or "command not found" errors.

Solutions:

  1. Verify Claude Code is installed

    bash
    which claude
claude --version

  2. Install Claude Code

    bash
    npm install -g @anthropic-ai/claude-code

  3. Check PATH - ensure the npm global bin directory is in your PATH

Cursor IDE won't connect ​

Symptoms: Daemon can't connect to Cursor.

Solutions:

  1. Verify Cursor is running with debugging enabled

    bash
    # macOS
/Applications/Cursor.app/Contents/MacOS/Cursor --remote-debugging-port=9222

  2. Check if port 9222 is in use

    bash
    lsof -i :9222

  3. Restart Cursor with the debugging flag

Push Notifications ​

Not receiving notifications ​

  1. Check notification preferences in the mobile app settings
  2. Verify device permissions - ensure notifications are enabled for Cmd+Ctrl
  3. Check "Watch" status - only watched sessions send notifications
  4. iOS: Check notification settings in Settings → Cmd+Ctrl → Notifications

Notifications delayed ​

Push notification delivery depends on:

  • Apple/Google push services (usually instant, sometimes delayed)
  • Device network connectivity
  • Battery optimization settings (Android)

Getting Help ​

If you're still having issues:

  1. Check the logs - daemon logs often contain useful error messages
  2. GitHub Issues - Report a bug
  3. Community - Ask in our Discord (coming soon)

Copyright © 2026 Cmd+Ctrl