agent-wechat: Instructions file for Codex

Agent guide for agent-wechat

This repository provides a standalone native WeChat daemon, Rust CLI and OpenClaw channel. It communicates directly with WeChat and reads/writes supported official-format profiles without an official executable at runtime. Check implementation and validation before describing a capability as supported.

Repository map

Native routes/contracts live in packages/native-client-rust/crates/wechat-api/; run pnpm generate-types after exported Rust contract changes. The README is a concise user guide, not an exhaustive API specification. The former UI server, image, container CLI and Wechaty integrations are retired; Git history retains their implementation.

Working rules

• Use neutral, accurate technical language in code, comments, docs, commits, and PRs. Do not imply unauthorized access or conceal how a feature works.
• Keep account credentials, tokens, private infrastructure details, and research-only material out of this public repository. Do not link to private research repositories from public docs.
• WeChat protocol, profile-format and reverse-engineering research findings are not kept in this repository. If a dedicated internal research/documentation repository is available, read and record those findings there instead; do not add dev-notes/-style research or validation notes here.
• Use an isolated test container and test account for behavior changes. Do not send messages to a live bot or modify a production container unless the task explicitly calls for it. Confirm the intended destination before any send.
• Preserve existing container data, official profiles and backups unless removal is explicitly requested. Retiring runtime source does not authorize deleting deployed containers, registry tags or volumes.
• Use one writer per official profile. Stop the official app before takeover; a caller assertion is not proof that an unmanaged app stopped. Do not infer arbitrary official-build or live ARM64 compatibility from synthetic tests.
• Add a changeset for user-facing behavior or package changes. Documentation-only edits do not need one.
• Follow the official client's verified implementation and storage for existing WeChat features. Settled message/contact/group state belongs in the supported official profile; read or derive it there instead of creating a parallel settled-state model in a sidecar. Sidecars may track pending work, raw receipts, deduplication, idempotency and recovery. Keep those operational records separate from canonical state and document why each is needed. An API may derive additional information from existing evidence without persisting a second copy. Treat behavior or retention beyond the official client as a separate proposed feature, state that difference, and obtain user agreement before implementing it. Missing or incomplete analysis is not evidence that extra storage is necessary.