{"slug":"amal-david-publish-report","name":"publish-report","description":"Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked — and whenever the user asks to publish, share, make a public link for, or send a local report/doc/dashboard/web project from terminal, Codex CLI, or Codex desktop.","long_description":"---\nname: publish-report\ndescription: Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked — and whenever the user asks to publish, share, make a public link for, or send a local report/doc/dashboard/web project from terminal, Codex CLI, or Codex desktop.\nversion: 0.7.0\n---\n\n# Publish with Pagecast\n\nPagecast turns a local **HTML or Markdown** file (a report, plan, doc, or\ndashboard) into a shareable public URL in the user's Pagecast Home. Execute an\nexplicit Pagecast request immediately; offer once when publishing would be\nuseful but the user did not request it.\n\n## Consent and intent\n\n- “Publish this as a Pagecast”, “Pagecast this”, or equivalent is sufficient\n consent. Run the publish command immediately and return the URL; do not ask\n again.\n- A proactive suggestion still asks once before publishing.\n- If the user asks only for the command, provide the command and do not run it.\n\n## When to offer\n\n**Default to offering.** Whenever you produce an `.html`/`.htm` or\n`.md`/`.markdown` file that a person could reasonably share, proactively offer to\npublish it — once, right after you finish making it. Do **not** wait to be asked,\nand do **not** stay silent because you are unsure whether it is \"worth it.\" If it\ncould be shared, offer.\n\nThis includes:\n\n- A report you generated — test/coverage/Lighthouse/Playwright output, a data\n dashboard, an analysis, a \"here's what I built/found\" summary.\n- A written plan, proposal, design doc, spec, release notes, or doc.\n- A static web project that was just built, with a generated entry file such as\n `dist/index.html`, `build/index.html`, `out/index.html`, or `public/index.html`.\n- Any time the user says \"share\", \"publish\", \"make a link for\", or \"send\" a doc.\n\n**The only files to skip** (don't offer): scratch/draft notes the user is clearly\nkeeping private, source code, config files, secrets, and repo-meta files (README,\nCHANGELOG, CONTRIBUTING, LICENSE, AGENTS.md, CLAUDE.md, TODO/tasks), or anything\nunder `node_modules`/`dist` build internals. When it is borderline, **offer** —\nthe user can just say no.\n\nAsk **at most once per file.** If the user declines or ignores the offer, drop it\nand don't re-ask for that file. Never nag across multiple turns.\n\n## The proactive question\n\n> \"Want me to publish this with Pagecast? It'll create a shareable public link.\"\n\nOnly a proactive suggestion needs this follow-up. An explicit instruction to\npublish with Pagecast already provides confirmation.\n\n## How to publish\n\nRun the headless CLI with the **absolute path** and `--json`:\n\n```sh\nnpx pagecast publish \"/absolute/path/to/file.md\" --json\n```\n\n(HTML and Markdown both work — Markdown is rendered to a clean page. If `pagecast`\nis installed globally/in the project, `pagecast publish \"\" --json` is the same.)\n\nNew links are **unlisted capability URLs**: a memorable prefix plus 128 bits of\nopaque entropy. Anyone with the URL can view it; unlisted does not mean private.\nThe user can rename a link, add password protection, or make a short, shareable\n\"drop\" link from the `npx pagecast` app. Existing word-only links remain valid.\n\nManaged links live in one user-level Home at `~/.pagecast/home/`, under\n`/p//`. The same item in the same agent context updates the existing URL;\na new item or context creates a new URL. Pagecast stores only a local hash of\nthe agent context identifier.\n\n### Publish options\n\nAdd any of these to a `publish` command:\n\n- `--expires <7d|12h|never>` — edge-enforced link expiry (default 30d). The page\n returns 410 once expired; `--expires never` keeps it live until revoked. The\n result JSON reports `expiresAt` (or none when never).\n- `--label \"\"` — set the page's display name in the Pagecast app.\n- `--context-id \"\"` — explicitly select the local agent context.\n- `--new-link` — force a fresh URL.\n- `--update \"\"` — update a known publication.\n- `--non-interactive` — never open browser authentication; return a structured\n authentication-required result instead.\n\n```sh\nnpx pagecast publish \"/absolute/path/to/report.html\" --expires 7d --label \"Launch report\" --json\n```\n\n### Password handling\n\nNever ask the user to provide a page password in chat and never place a secret\nin an agent-generated command or tool argument. Publish the page first, then\ntell the user to open the local `npx pagecast` app and set password protection\nthere. This keeps the credential out of the model and tool transcript.\n\n**Publishing a plan** (e.g. after plan mode): the plan lives in your context, not\na file yet. If the user wants it shared, first write the plan markdown to a file\n(e.g. `./plan.md`), then publish that path. Don't overwrite an existing file the\nuser cares about — pick a clear new name.\n\n## Live goal / progress page\n\nWhen you're working toward a **`/goal`** (a long autonomous run the user can't\neasily watch), the user often can't see what's happening. Proactively **offer\nonce**:\n\n> \"Want me to publish a live progress page for this goal? You'll get a public\n> link you can open anytime to see status and what's done.\"\n\nOn an explicit **yes**:\n\n1. Write a `pagecast-goal.md` in the working dir with the goal, status, a\n done/next checklist, and a one-line \"latest\", e.g.:\n ```markdown\n # \n\n **Goal:** \n **Status:** In progress · updated