# Pagecast

Preview local HTML reports, Markdown docs, and static mini apps, then publish them to shareable Cloudflare Pages URLs — from the terminal or your coding agent.

**Feature HTML:** <https://pagecasthq.pages.dev/>

<p align="center"> <img src="media/admin.png" alt="Pagecast admin UI: published reports with per-page password protection" width="900"> </p>

## About

Pagecast is a local-first publishing tool for agent-generated reports and small static web projects. Preview files, manage published versions, rename links, re-sync updates, password-protect pages, and revoke old URLs — from a local admin UI or headless `pagecast` commands.

**Good fits:** HTML reports and dashboards (Playwright, Lighthouse, coverage); Markdown plans, docs, and release notes; static mini apps from `dist`/`build`/`out`; coding-agent workflows that publish a finished artifact on request.

**Not a fit:** private scratch notes, or server-rendered apps that need a running backend (export static assets first).

## Quick Start

Requires Node.js 20+ and a Cloudflare account (for publishing). No global install:

```sh npx pagecast ```

This starts the local app and opens the admin UI:

- Admin UI — `http://pagecast.localhost:4173` - Local published-page preview — `http://pagecast.localhost:4174` (same `/p/<slug>/` shape it deploys) - Local data/config — `.pagecast/` in the current directory

Want Pagecast waiting in the background instead of keeping a terminal tab open?

```sh npx pagecast background start npx pagecast open ```

On macOS, you can also make Pagecast feel like a tiny local app that survives login/restart and opens without a visible port:

```sh npx pagecast setup-local-url ```

That installs a local-only `pf` redirect for `http://pagecast.localhost` and a user LaunchAgent that keeps the Pagecast server running after login. Pagecast still runs internally on its normal port; it does not run the app as root or occupy port 80 with a server process. Manage the pieces separately