Postplan

Chat renders markdown badly. A plan, a comparison, or a set of UI mocks is easier to judge as a page in a browser. Write one HTML file, upload it, and reply with nothing but the URL — the user opens it wherever they are, phone included.

Publish

1. Write one complete static HTML document locally.
2. npx postplan upload <file> — prints a draft URL and a /raw URL.
3. Give the user the URL. That link is the deliverable.

Re-uploading the same local file updates the existing draft, so the URL stays stable across iterations; keep one file per document rather than starting a new one each revision. --new forces a separate draft, --description "<label>" sets the label shown in the dashboard. Credentials and file-to-draft mappings live in ~/.postplan; an API key is optional and only needed for postplan list and the dashboard.