Download WeChat Channels

Use the upstream wx_channels_download binary without copying its implementation. Only download videos the user owns or is authorized to save.

Choose the path

• If the user has a direct video URL and optional decryption key, use the direct CLI path. This does not require changing the system proxy.
• Otherwise use the interactive WeChat path. It starts a local HTTPS interception proxy, may install a root certificate, and may modify the system proxy.
• Do not claim that an ordinary WeChat share URL is sufficient. Upstream share-link parsing needs extra service credentials and is not the default local workflow.

Install or update

Run:

python3 scripts/wx_channels.py install
python3 scripts/wx_channels.py doctor

The installer downloads the matching asset from the latest GitHub release, verifies it against the release checksum file, and stores it outside the skill repository. It prefers the non-UPX safe Windows build. Do not redistribute the downloaded binary.

Direct URL download

Confirm the URL came from a source the user is authorized to download. Then run:

python3 scripts/wx_channels.py download --url "$VIDEO_URL" --filename "video.mp4"

Add --key NUMBER only when a decryption key was captured with the URL. The upstream command writes to the user's Downloads directory.

Interactive WeChat download

Before running this path, explain that it can install a local root certificate and change the system proxy. Obtain explicit user authorization for those system changes.

After authorization:

python3 scripts/wx_channels.py start --allow-security-changes

Keep the process running. Ask the user to open the authorized video in the desktop WeChat client, wait for playback, pause it, and use the injected download button. Report the download directory printed by the process.

Stop with Ctrl+C. Verify that the upstream process restored the previous proxy settings; if network access is abnormal, run its uninstall command:

python3 scripts/wx_channels.py uninstall --allow-security-changes

Do not run start or uninstall without explicit authorization. Do not expose captured URLs, cookies, tokens, keys, certificates, or log contents in chat or commits.

Troubleshoot

Run doctor first. Read references/upstream.md for architecture, supported platforms, ports, conflicts, and license constraints. Prefer upstream documentation and releases over remembered flags.