Last Tuesday I installed QClaw 2.1 on my office desktop, opened WeChat on my phone, and typed “organize desktop files.” Nothing. Tried “search PDF.” Nothing. Sent a plain “screenshot.” Still nothing. The frustrating part? A colleague sitting three desks away had the exact same setup, same network — and his commands went through instantly. It took nearly an hour of digging before I found the culprit. Here’s every step of that troubleshooting process so you don’t have to repeat it.

Is WeChat Actually Connected on Your PC?

This is the most overlooked check. QClaw requires the PC version of WeChat to be running and logged in — the mobile app alone isn’t enough. On Windows 11, look at the system tray in the bottom-right corner for the WeChat icon. On macOS 14.5, check both the Dock and the menu bar.

If PC WeChat shows “Logged out” or simply isn’t launched, commands sent from your phone never reach QClaw. One subtle gotcha: closing your laptop lid and reopening it can silently disconnect PC WeChat without showing any prompt. You think you’re still logged in, but the session died.

There’s another edge case. If you’ve logged into WeChat on both a tablet and your phone, the PC client gets kicked off automatically. Keep it to a phone + PC combo and the connection stays stable.

Is the QClaw Process Actually Running?

On Windows 11, press Ctrl + Shift + Esc to open Task Manager and search for QClaw. You should see QClaw.exe or QClawService in the process list. On macOS, open Activity Monitor and search the same keyword.

My issue that day was interesting — the process was running. But there were two of them. An old QClaw 2.0 background process had survived from a previous installation, and the new 2.1 instance was fighting it for the same local port. Neither could actually receive data.

The fix: kill all QClaw processes, then restart the application once. On Windows, right-click → End Task. On macOS, use Force Quit. Wait for the tray icon to turn green before sending any commands.

Permission Problems

Windows UAC can silently prevent QClaw from executing certain desktop operations. Right-click the QClaw shortcut → Properties → Compatibility → check “Run this program as an administrator.” This gives QClaw the elevation it needs to handle file operations and screen captures.

macOS has its own permission layer. Go to System Settings → Privacy & Security → Accessibility, and make sure QClaw is listed and enabled. Ventura and Sonoma tend to reset accessibility permissions after major OS updates, so check this again after any macOS upgrade.

Corporate environments add another layer. If your company uses MDM (Mobile Device Management), QClaw’s process might be restricted by policy. In that case, you’ll need IT to whitelist the application.

Command Format Issues

QClaw is fairly flexible with natural language, but certain formatting mistakes will cause commands to fail silently:

Try sending the simplest possible test command first: “get system info” or “take screenshot.” If that gets a response, the communication channel is fine and the problem lies in how your previous commands were phrased. The QClaw usage guide covers standard command patterns.

Version Mismatch Between Phone and PC

This catches more people than you’d expect. QClaw 2.1 on the desktop needs WeChat 8.0.x or later on the phone. If your mobile WeChat is still on a 7.x build, the message format may be incompatible.

Check your WeChat version: open WeChat → Me → Settings → About. Anything below 8.0.43 should be updated through your app store first.

The QClaw desktop client matters too. Grab the latest stable release from the QClaw download page — don’t rely on an installer you downloaded months ago. The command protocol changed between 2.0 and 2.1, so mixing versions almost guarantees commands won’t go through.

Firewall and Security Software Blocking

This turned out to be my actual problem. Windows Defender Firewall was blocking QClaw’s local communication port (default TCP 18923). The process was running, WeChat was online, but data packets couldn’t reach QClaw.

To fix on Windows: open Windows Security → Firewall & network protection → Allow an app through firewall → find QClaw and enable both “Private” and “Public” networks.

On macOS: System Settings → Network → Firewall Options → add QClaw to the “Allow incoming connections” list.

If you run third-party antivirus software — Norton, Kaspersky, Bitdefender, or Chinese tools like 360 or Huorong — check whether they have a separate network protection module that blocks unknown processes from using local ports. Huorong in particular has an aggressive default that silently drops local port traffic from unrecognized executables.

Quick Troubleshooting Checklist

When QClaw commands aren’t responding, work through this list in order — most problems resolve within the first three steps:

  1. PC WeChat online? — Check it’s logged in and not kicked off by another device
  2. QClaw process running? — Should be exactly one instance, tray icon green
  3. OS permissions granted? — Windows UAC / macOS Accessibility
  4. Simple test command works? — Confirms the communication channel
  5. Versions match? — WeChat ≥ 8.0.43 on phone, QClaw ≥ 2.1 on desktop
  6. Firewall allows QClaw? — Check OS firewall and any third-party security tools

About 90% of “QClaw not working” reports are solved by the first three items. If you’ve checked everything and commands still don’t go through, the cleanest path is to uninstall QClaw completely, download the latest installer from the download page, and do a fresh install. Leftover config files from older versions occasionally cause silent conflicts.

For additional troubleshooting steps, see the QClaw not responding guide or browse the FAQ page for more edge cases.

Ready to try QClaw?

Install on desktop, send commands via WeChat, handle tasks remotely — anytime.

Download QClaw →