publishportlisted

# Publishing with PublishPort PublishPort runs publishing commands **on the user's own machine, inside their own logged-in browser**. No platform API keys, no cloud account impersonation — every action comes from the user's real session, which is why platforms with no public write API (Xiaohongshu, Douyin, Zhihu, WeChat…) can be published to at all. Two rules matter more than everything else below: - **Never guess a flag.** Ask the CLI for its schema; it is the only accurate source. - **Never publish twice.** A command that errors may still have posted. Check, then retry. ## 1. Pick the channel Publishing always goes through PublishPort's relay, which runs the command on the machine where the user's desktop app is signed in. Two ways to reach that relay — try them in order: **a. PublishPort MCP tools are available** (`list_capabilities`, `local_bash`, `publish_guide`, …) — use them and follow their own instructions, which are authoritative and more detailed than this file. Call `list_capabilities` first: it returns the online devices, the live per-platform login state, and the `device` handle every other tool needs. Then call `publish_guide(<platform>, <device>)` before publishing — it returns that platform's fast path together with the live `--help` schema, saving you a round trip. **b. No MCP — use the official CLI**, which exposes the same tools over the same relay: ```bash npx publishport capabilities ``` It works whether or not you are on the user's machine, bec