96Push Remote Control

Problem

Multi-account content workflows often stall around local clients, platform rules, and high-impact actions. Images may be local files, while WeChat, Douyin, and Toutiao have different cover and field requirements. A mistaken or repeated publish call can spawn many browser automation tasks.

How It Works

• Local control: drives the user's local 96Push client through the 96.cn HTTPS proxy; PUSH_API_KEY should stay in an environment variable or local .env instead of chat by default.
• Content management: supports query, create, update, delete, publish, and platform settings; thumb and files accept HTTP(S) URLs only, so local media must be uploaded or hosted first.
• Platform fit: reads the target platform rule before creating content, then validates required fields for article, graph_text, and video; video URLs belong to video, not article files.
• Safe publishing: presents exact content, accounts, draft/live state, and settings before running; multi-account batches need extra confirmation; publish is called once, waits for completion, and should not be retried on PUBLISH_ALREADY_RUNNING or HTTP 425.

Boundaries

• High impact: publishing, deletion, queue cancellation, and platform setting changes require explicit approval.
• No arbitrary local reads: a server runtime cannot read user-local paths directly; use uploaded/hosted URLs.
• Platform variance: covers, original flags, visibility, and tag fields vary, so target platform rules are authoritative.