OpenClaw WeChat Channel Response Repair

Problem Diagnosis

When an OpenClaw WeChat channel reports ON / OK but the bot still ignores incoming messages, the issue is often not the WeChat network itself, but a monitor that never started, a broken plugin import, or missing account configuration. Typical log symptoms include createTypingCallbacks is not a function, weixin not configured: missing token, plugins.allow is empty, or no inbound records at all. This skill is useful when a channel looks configured in the UI but does not actually process traffic.

How It Works

The skill follows a diagnostic and repair workflow for the OpenClaw WeChat plugin: check channel status, inspect live logs for known failure patterns, fix the known import-path issue for createTypingCallbacks, then add the required channels and plugins.allow entries in ~/.openclaw/openclaw.json so the WeChat account is explicitly enabled and the plugin is allowed to run. After restarting the gateway, it verifies monitor state, sends a test message, and checks channel health. It can also point to follow-up checks such as QR-code re-login, expired tokens, and per-account conversation isolation. The scope is limited to OpenClaw WeChat channel deployments; it does not replace general WeChat protocol debugging or apply to unrelated bot stacks.