← Back to library

Publish agent HTML reports on your own domain

vitorbaptistaa values the HTML reports models generate but switches models often and wanted to avoid tying them to one vendor's share links. So they built getonup, which uses Cloudflare Workers to host static pages under a domain you control. You hand an agent the repository and it sets up the account, Zero Trust protection and a chronological index.

  • OutcomeSet up a small open source tool that publishes agent-made HTML on a domain you control, behind a login, with a dated index of everything published.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditvitorbaptistaa on Hacker News
View original
Works with
Claude CodeCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Your team shares HTML reports from agents
  • You switch between model vendors
  • You have a domain on a hosting account

Not for: Public marketing sites; Teams with no domain

What do you need, and what do you get?

You need

  • Hosting account and domain
  • Repo for the tool
  • Access rules

You get

  • Private pages on your domain
  • Dated index
  • Access controlled by login

How does it work, step by step?

  1. Choose a subdomainPick a subdomain for reports.
  2. Point the agentHave the agent install it, reviewing each change.
  3. Check accessConfirm only your team can view pages.
  4. PublishHave agents deploy each report as a static page.
  5. Use the indexBrowse reports by date.

The prompt

Our own prompt, inspired by vitorbaptistaa on Hacker News and written to work in Claude Code and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Set up a private report site on {subdomain} using {tool_repo}. Before changing my hosting account, list every change you will make and wait for my approval.
Require login for all pages, keep a date-ordered index, and show me how to confirm a page is not public.

Inspired by vitorbaptistaa on Hacker News: Comment in Sites in ChatGPT. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Agent setup touches your hosting account; review its changes.
  • Reports may hold private data; test access before sharing links.
  • Clean up old pages you no longer need.

Our take

vitorbaptistaa's tool fixes a small but persistent mess: useful reports from different models end up scattered across vendor share links that expire, get reorganized or disappear when you cancel a plan. Publishing to a domain you control, with one dated index, means every report stays findable and switching models changes nothing about where they live. The access control step is the one to check personally rather than trust. Reports often contain customer names, revenue figures or internal plans, and a page accidentally left public is a leak with a URL. After setup, open a report in a private window to confirm it asks you to sign in. Because the agent configures your hosting account, read what it changed: routes, DNS records and policies, and remove anything you did not expect. The author's team publishes several reports a day, which is the payoff once it becomes routine. Add a short rule for retention, such as archiving or deleting pages older than a quarter, so the index stays useful.

Where the time goes back: Reports from any model end up in one private, dated place your team can find.

FAQ

Why not built-in sharing?
The developer wanted pages that do not depend on one model vendor.
Is it free?
The developer says it is free and open source.

Source and credit

Inspired by vitorbaptistaa on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Comment in Sites in ChatGPT
Creator
vitorbaptistaa on Hacker News
Published on
Hacker News
Original date
Oct 3, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminPrompt✓ AI dry run

Check saved agent skills hold up on a messier second run

Have your lead agent list every private skill it can reach, check each one for a clear purpose, required inputs, decision rules, a way to verify results, a defined output, approval points, failure handling and protection against duplicate actions, then draft improved instructions and a tougher test for your approval.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminRoutine✓ AI dry run

Draft a weekly recap post from your GitHub activity

Start Monday with a ready draft of what you shipped last week, plus a stats page, instead of trying to remember.

Credit: Yash Kumar Saini

An afternoon+
Operations & AdminRoutine✓ AI dry run

Triage only the new arXiv papers each week

Spend reading time only on fresh papers that pass your own criteria, with promising ones already filed in Zotero.

Credit: Jonas Wiedermann-Möller

An afternoon+