Your agent built a dashboard. Here is where to put it.

The step the agent leaves you with

The on-demand pattern is simple: ask an agent to gather the data and render an HTML dashboard to answer the question in front of you, instead of maintaining a standing dashboard nobody opens. It works. But it stops one step short. The agent produces a block of HTML, and HTML on its own is not something you can send to a colleague or a client. Someone has to open it, often away from your terminal, which means the page needs a URL.

That is the only gap, and it is small. The page has to be hosted somewhere that hands back a link. The question is just which host, because the obvious ones are built for a different job.

Why generic hosting is the wrong shape

You could drop the HTML on GitHub Pages, Netlify, or an S3 bucket. They will serve it. But their defaults are built for publishing a public website and keeping it up: the page is public, often indexable, and permanent unless you go and delete it. An agent-built dashboard is usually the opposite of all three. It tends to carry real data the agent pulled in, it is meant for specific people, and it is single-use. So the generic host leaves you manually setting access you do not have, and manually cleaning up pages that were obsolete an hour after they were built.

The shape this use case wants is private by default, gateable per link, and disposable on a timer. That is a different host, not a different bucket.

The private, disposable fix

Full disclosure: we build Stacktree, so read this as us describing where we fit. Stacktree takes the agent's HTML and publishes it to a private link with three properties that match a throwaway dashboard specifically:

• Private by default. The URL is unguessable and the page is served with a search and AI opt-out header, so it is not indexed and not discoverable by guessing. A page with client numbers stays between you and the recipient.
• It expires. Put an expiry on the page so a single-use dashboard removes itself. Anonymous publishes already default to a 24-hour expiry, so disposable is the default, not a chore.
• Gateable per link. Add a password, or restrict to a client's email domain with magic-link verification, when the page leaves your team.

The trade is that Stacktree hosts static HTML, so the page is a snapshot, not a self-refreshing dashboard. That is the right shape here: a throwaway dashboard is a snapshot by definition. If you need a standing view that re-queries live data for many viewers, that is a real dashboard tool's job, not this.

How an agent does it in one step

Because the publish step runs over MCP, the agent can finish the job without you leaving the conversation. It calls publish_html with the rendered page and gets back a private URL, setting an expiry in the same call so the page is disposable from the start. For a client, it adds a password or an email-domain gate. If a follow-up changes the view, update_site replaces the page in place at the same URL, so a link you already sent stays correct. We package this as an agent-run-report skill so the gather, render, and publish steps run as one move, but the primitive is just the publish call.