WorkBuddy WeChat ClawBot Proactive Push

Problem It Solves

WorkBuddy’s proactive WeChat push channel is awkward to call by hand: credentials, context_token, the full botToken format, and the rich-media upload protocol all have strict constraints. Small mistakes can trigger ret:-2 or errcode:-14. This skill is for engineers who need to push task results to a designated WeChat account, covering text, images, files, and videos.

How It Works

It targets the weixinClawBot / ilink bot channel, reads local settings.json for credentials and the recipient, avoids writing secrets, and avoids printing token plaintext. Text pushes usually use an empty context_token; media pushes require a non-empty token read as-is from get_updates_buf in the WeChat claw-state cursor file. Requests align with the official protocol, use the full botToken as Authorization, and call the sendmessage endpoint. Rich-media sending generates an AES key, requests an upload URL, uploads the ciphertext, retrieves the download token, then builds the media item and sends it.

Boundaries and Notes

This is not a WeChat customer-service account, and it does not use the platform customer-message API. It assumes WorkBuddy / ClawBot has an established session and the recipient configuration is complete. If media or text is rejected, activate the bot by sending one message from WeChat to ClawBot to refresh the cursor, then rerun the command. Do not paste get_updates_buf, settings.json, or cursor files into chat, issues, or repositories.