Send a tiny test command first

Do not start troubleshooting with a complex file task. Send a simple command such as “reply online” or “tell me whether QClaw is active.” If that works, the WeChat connection is probably alive and the issue may be with the specific task.

If even the tiny test gets no response, move down the checklist: desktop app, sleep mode, network, permissions, and model availability.

Check whether the desktop app is still running

QClaw runs on the computer. Mobile WeChat sends commands, but the desktop app does the work. If the app was closed, crashed, blocked by the system, or waiting for an update prompt, WeChat messages will not have anywhere useful to go.

On macOS, check the menu bar, Dock, privacy permissions, and whether the app is still active. On Windows, check the taskbar, security prompts, firewall alerts, and whether the app was stopped by a cleanup tool.

Computer sleep is the boring but common cause

Many “QClaw not responding” cases are not mysterious. The computer went to sleep, changed power mode, or disconnected from the network. Since QClaw depends on the desktop side, a sleeping computer cannot execute WeChat commands.

For troubleshooting, temporarily extend sleep time and keep the computer on a stable network. This is not a promise of 24/7 automation; it is just a clean way to remove the most common variable.

Network and model service checks

QClaw may depend on network access for WeChat communication and for selected model providers. If you changed VPN, proxy, Wi-Fi, firewall, or DNS settings after binding, test again on a stable network.

If the desktop app is online but only AI-generated answers fail, the selected model service may be unavailable or misconfigured. Try a smaller prompt and check whether the model settings are still valid.

Permission problems show up as silent failures

Some commands require file, browser, automation, or accessibility permissions. If QClaw can answer a simple message but cannot touch a file, open a browser page, or read a folder, the problem may be task permission rather than WeChat binding.

Start with a harmless command, then increase scope: reply online, list a known folder, summarize one accessible file, then try the larger task. That order makes the failure easier to locate.

Not installed or not bound yet?

Start with the download page and the WeChat binding guide before troubleshooting command response.

View QClaw download guide →