Show HN: Pagecast – Publish Markdown/HTML Reports to Cloudflare Pages

▲ Show HN: Pagecast – Publish Markdown/HTML Reports to Cloudflare Pages(github.com)

32 points by amaldavid 3 days ago | 8 comments

I built this because I kept generating HTML/Markdown reports from Claude Code/Codex and needed a permanent share link instead of a localhost tunnel. Pagecast is a local CLI that publishes those files to your own Cloudflare Pages account.

It supports Markdown and HTML, stable URLs, renaming, republishing to the same URL, and watch mode for continuous updates to same file. It is MIT licensed.

The main design choice is that there is no hosted Pagecast account. It uses your Cloudflare account and deploys there directly and has claude code and codex integrations as skill/hooks.

Basically it can be used as a replacement for codex sites or claude artifacts

▲ mpeg 2 days ago | parent | next [-]

This is nice, but I don't see much of a difference between just asking claude to write a wrangler config to push to cf pages, which can be extremely simple

  name: my-cool-pages-project   
  pages_build_output_dir: ./html-files/

then npx wrangler deploy

	▲	amaldavid a day ago \| parent [-]
		publishing workflow yes, i wanted to have a way to manage published urls and update existing urls with a small dashboard as well since we end up doing it repeatedly.

▲ hbcondo714 2 days ago | parent | prev | next [-]

Is there by chance a way to password protect the generated site?

▲

DANmode a day ago | parent [-]

https://github.com/robinmoisson/staticrypt

and other worse ways

	▲	amaldavid a day ago \| parent [-]
		yes, it is possible. Will be adding that and full website above <25mb publishing also soon

▲ rolymath a day ago | parent | prev | next [-]

Maybe tell your agent that your readme doesn't need to be that long so humans can read it and understand it. The Github readme is ludicrously long winded.

What's the point of this vs telling the agent to just use the cloudflare CLI?

"Local tool for publishing agent reports and small static sites" - Aren't agent reports small static sites? Why do you need to mention both?

Your Good Fits vs Bad Fits section is just a good fits vs bad fits for cloudflare pages, not your specific application.

Creating a chrome extension to add the publish button on the page is quite possibly the single biggest piece of evidence I've ever seen that code is now cheap.

Readme needs screenshots.

-----

Edit: I've been emotionally triggered by this project because the overall feel of it reminds me of all the junior developers at work who've started vibe coding everything and presenting it with confidence that even the most senior developers lack.

	▲	amaldavid 19 hours ago \| parent [-]
		Thanks for the unfiltered feedback! Yes, the readme and no screenshot was something that I meant to cleanup and add and are already live now. Agent reports vs small static sites -> It was supposed to mean markdown files as plans gets shared between teams which is what CC mentioned as agent reports. Yes, code is definitely cheap. Built it as an utility for myself and dogfooding it with my team. Had put it out with the thought that others might find it useful. Point in time, a lot of it is available vanilla with cloudflare cli but natively enabling passwords, private team dashboard are something that am considering. Passwords are already live as we speak. Will improve this as i get more feedback and time to spend on this.

▲ ms_by_pd 2 days ago | parent | prev [-]

what has happened