# Wechat CLI

Read-only access to local WeChat chats through rion-wechat-cli, plus a guided...

- Repository: https://github.com/Rion-Wu-tech/wechat-intelligence-hub (2751 stars)
- Category: Data and ML
- License: AGPL-3.0
- Last updated: 2026-10-16
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add Rion-Wu-tech/wechat-intelligence-hub --skill wechat-cli -g -a claude-code -y`
Codex: `npx skills add Rion-Wu-tech/wechat-intelligence-hub --skill wechat-cli -g -a codex -y`
Cursor: `npx skills add Rion-Wu-tech/wechat-intelligence-hub --skill wechat-cli -g -a cursor -y`
Gemini CLI: `npx skills add Rion-Wu-tech/wechat-intelligence-hub --skill wechat-cli -g -a gemini-cli -y`

## Description

Read-only access to local WeChat chats through rion-wechat-cli, plus a guided first-access workflow when the user asks to connect their own account or obtain its local database keys. Use for chat search, contact history and unsent reply drafts; acquisition requires separate confirmation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Rion WeChat CLI

Use `rion-wechat-cli` as the single public interface for local, read-only WeChat evidence. The public package must use Rion's independently implemented Reader by default and must not silently discover or invoke an old `wechat-cli` installation.

Default public entrypoint:

```bash
"${CODEX_HOME:-$HOME/.codex}/skills/wechat-cli/scripts/reader.sh" <command> <args>
```

An independently installed compatible CLI may be selected only when the user explicitly sets `RION_WECHAT_CLI_BIN` (legacy `RION_WECHAT_READER_BIN` remains accepted). Never describe notification-only coverage as complete chat access.

## Core workflow

For key/import failures, prefer `scripts/access.sh diagnose` (helper revision 2026-09-22.1+). With an explicitly supplied `--source` and `--database-root`, it checks material in a disposable configuration without replacing an active setup. Preserve `material_error.code`: JSON encoding, raw-key format, salt mismatch, dependencies and schema support are different failures. `--jev-request` only prepares an allowlisted offline request; it never calls an API. External classification cannot establish valid keys or authorize acquisition. See [diagnosis upgrades](references/access-troubleshooting.md).

For Windows access feedback or onboarding, read [Windows staged access](references/windows-access.md). A community success report is not an integrated provider or authorization to run attached code. Diagnose dependencies, actual DLL identity, material conversion and ACLs separately; do not bypass platform checks or repeat macOS acquisition on Windows.

The rest: https://github.com/Rion-Wu-tech/wechat-intelligence-hub/blob/HEAD/skills/wechat-cli/SKILL.md