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?
- Choose a subdomainPick a subdomain for reports.
- Point the agentHave the agent install it, reviewing each change.
- Check accessConfirm only your team can view pages.
- PublishHave agents deploy each report as a static page.
- 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)
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?
Is it free?
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.