# Workflows: what to have your agent publish as a link · Stacktree

Source: https://stacktr.ee/workflows

[Skip to content](#main) PFrom Product Hunt? Your first pages are free, no card. Code `PRODUCTHUNT` takes 50% off your first month of Studio.[Start free →](https://app.stacktr.ee/?join=1&from=producthunt)

×   A Stacktree customer sent you. Your first month is 50% off on any plan, taken off at checkout. [Start free →](https://app.stacktr.ee/?join=1&from=referral)

 ×    [Stacktree](/)[Developers](/developers)[Agents](/agents)[Docs](/docs)[Use cases](/use-cases)[Pricing](/pricing)[Blog](/blog)[Dashboard](https://app.stacktr.ee)[Sign in →](https://app.stacktr.ee)      By [ Steve Smith ](/about) · Founder, Stacktree  ·  Last updated October 7, 2026          workflows

#  What can I get my agent to publish to a link?

   Seven recipes, each ending in a prompt, a command or steps you can follow.  The weekly client report on one self-updating URL, the same report kept current by a ChatGPT Dot, the dashboard your agent just built, a Claude artifact worth keeping, an agent that reports its own runs, a morning report of who opened what you sent, and client comments sent to the tools your team works in. Every recipe works from a chat, a workflow tool, CI, or a terminal.

  [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_workflows)   install npx stacktree-install
Copy
      No card · 3 pages free · about a minute

##  What can I get my agent to publish to a link?

Anything it renders as a single HTML file: the weekly client report, the dashboard it just built, a Claude artifact worth keeping, or its own run report. Publish once and the link stays private and unguessable; when the agent re-runs, it updates the same URL instead of minting a new one. Once the link is sent, the agent can also tell you each morning who opened it, and each client comment can go straight to Slack, Linear or GitHub.

##  The seven recipes

   -  [  recipe   Publish a weekly client report to one link that updates itself  The most common real workflow: one URL the client bookmarks, refreshed in place every week by your agent, an n8n workflow, or CI. ](/workflows/recurring-client-report)
-  [  recipe   A ChatGPT Dot that sends your client the weekly report  Your Dot gathers the figures, rewrites the report and updates the private link the client already has, then tells you what changed. You hear when they open it. ](/workflows/dot-weekly-client-report)
-  [  recipe   Host an HTML dashboard your agent built  One self-contained file to one private URL: drag and drop, one tool call, or one curl. Refresh it in place or let it expire on its own. ](/workflows/agent-built-dashboard)
-  [  recipe   Move a Claude artifact to a private link that will not expire  Off the public claude.ai URL and onto a private page with a passcode, your own domain, and updates that keep the same link. ](/workflows/rescue-claude-artifact)
-  [  recipe   Have your agent publish its own run report as a link  End every run with a URL, not a wall of terminal text. One standing status page the agent itself keeps current. ](/workflows/agent-publishes-its-own-report)
-  [  recipe   Have your agent report each morning who opened what you sent  A scheduled prompt for Grok Bot, Claude, ChatGPT or any MCP client: who opened each page through their own link, and what they commented. It only reads. ](/workflows/who-opened-it)
-  [  recipe   Send client comments to Slack, Linear or GitHub  Paste a Slack or Discord webhook URL and each comment arrives as a message, or file it as an issue through n8n, Zapier or Make. ](/workflows/client-comments-to-slack-linear-github)

## Why these six

 They follow what people actually publish, not what a pricing page wishes they published. Across real Stacktree publishes, recurring client briefs are the single biggest category, reports and audits sit right behind them, and dashboards follow. Proposals and slide decks, the things delivery tools usually lead with, are around one percent, so they are not here.

 The first five are the same primitive wearing different clothes: a single self-contained HTML file goes in, a private unguessable URL comes out, and the next run replaces the content in place so the link you already sent keeps working. Gates layer on top when the audience is a client: a passcode on any plan, a company-email check from Solo, your own domain from $19 a month.

 The last two come after the send. A scheduled prompt reads which pages were opened, by whom through their own links, and what comments came in, then reports in your chat without changing anything. And each comment a client leaves can go straight to a Slack or Discord channel, or become a Linear or GitHub issue, through a webhook.

## The publishing recipes end with three doors

 You should not have to read a setup guide to try any of this. Each publishing recipe closes with three executable exits, in increasing order of commitment. The Dot recipe and the read report close with a prompt instead, and the comment hand-off with setup steps, because all three work on pages in your account.

  - One line pasted into any agent. Fetch and follow https://stacktr.ee/prompt.md, plus what to publish. Works in anything that can fetch a URL.
 - A one-time install. npx stacktree-install for CLI agents, or the Claude.ai connector at https://api.stacktr.ee/mcp.
 - A curl with no signup. POST https://api.stacktr.ee/sites publishes anonymously; the link lives 24 hours and can be claimed later.
  To see what the output looks like before you run anything, the [examples gallery](/examples) is a set of complete, fictional deliverables served as live Stacktree pages.

FAQ

## Frequent questions

     What can an AI agent publish to Stacktree? +  Anything it can render as a single self-contained HTML file: reports, audits, dashboards, status pages, diagrams, decks, one-off tools, Claude artifacts. The agent calls `publish_html` over MCP and gets back a private, unguessable URL; `update_site` replaces the content in place so the same link stays current.   Do these workflows need an account? +  Not to try them. An anonymous publish needs no account and the link lives 24 hours; the response includes a claim token so you can adopt the page later. A standing link needs an account: free keeps 3 pages for 7 days each, or once someone else opens one, for 30 days after their latest visit, up to 90 days in total. Pages stop expiring on paid plans from $19 a month. The read report and the comment hand-off are the exceptions: they work on the pages in your account, so they need one. Names and open counts in the read report start on Solo; a webhook for comments works on Free.   Which agents and tools do these recipes work with? +  Any MCP client (Claude Code, Cursor, Codex CLI, the Claude.ai connector at api.stacktr.ee/mcp), ChatGPT and ChatGPT Dots through the Stacktree plugin in ChatGPT's directory, the n8n-nodes-stacktree community node, the stevysmith/stacktree-actions GitHub Action, Grok Bot with no install at all, and plain curl against the REST API. Every recipe page ends with the exact commands or prompt.   Does the person opening the link need an account? +  Never. The unguessable URL is the credential; a passcode or a company-email check by magic link can sit on top. Viewers open the page in any browser with nothing to install and nothing to sign up for.
Keep reading

## Related guides

   -  [ Claude Code wants to publish an artifact The permission prompt says the tool uploads the file to claude.ai. ](/blog/claude-code-publish-artifact-private)
-  [ Example deliverables Live pages showing the finished form: reports, proposals, audits. ](/examples)
-  [ Share an HTML file with a client The handoff itself: publish, gate, send one link, revoke if needed. ](/share-html-file-with-client)
-  [ Publish from n8n The community node that gives any workflow a publish step. ](/n8n)
-  [ Publish from Grok Bot The zero-install path: the bot browses to Stacktree and publishes. ](/grok-bot)
-  [ All use cases The wider catalogue: notebooks, Storybook, diagrams, internal tools. ](/use-cases)
-  [ Every agent integration Claude Code, Cursor, Codex, Claude.ai, and any MCP client. ](/agents)
-  [ How to host a dashboard your AI agent built An AI agent builds a dashboard as HTML, but HTML is not a link. ](/host-ai-dashboard)

##  Pick a recipe and run the last block on the page.

 The first publish is anonymous and needs no account. It lives 24 hours, long enough to decide.

 [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_workflows)   install npx stacktree-install
Copy
       Private hosting for the HTML your agents make.

[](https://betalist.com/startups/stacktree?utm_campaign=badge-stacktree&utm_medium=badge&utm_source=badge-featured)[Featured on](https://devhunt.org/tool/stacktree)[](https://buildlist.io)[Get started free](https://app.stacktr.ee/?join=1)

## Product

- [Page video](/page-video)
- [Ask this page](/ask-this-page)
- [Client spaces](/client-spaces)
- [Templates](/templates)
- [Example deliverables](/examples)
- [Custom domains](/custom-domains)
- [Client feedback](/client-feedback-loop)
- [One-time links](/one-time-view-links)
- [See how pages get read](/page-engagement)
- [Made with Stacktree](/made-with)
- [Security](/security)
- [Watch the demo](/demo)

## Agents

- [All integrations](/agents)
- [Claude Code](/claude-code)
- [OpenAI Codex](/codex)
- [Cursor](/cursor)
- [Claude.ai connector](/claude-ai-connector)
- [Claude Cowork](/what-is-claude-cowork)
- [Meta Muse](/muse)
- [MCP server](/mcp-publish-html)
- [Deploy from Claude Code](/deploy-html-from-claude-code)
- [Skills](/skills)
- [Slack app](/slack)
- [n8n node](/n8n)
- [Agent payments (x402)](/x402)

## Alternatives

- [All comparisons](/alternatives)
- [Head-to-head comparisons](/compare)
- [Tiiny Host](/tiiny-host-alternative)
- [GitHub Pages (private)](/github-pages-private-alternative)
- [Vercel](/vercel-alternative-for-agents)
- [ngrok](/ngrok-alternative-for-html)
- [Display.dev](/display-dev-alternative)
- [Static.app](/static-app-alternative)
- [OpenAI Codex Sites](/openai-codex-sites-alternative)
- [here.now](/here-now-alternative)
- [Shippage](/shippage-ai-alternative)
- [Best private hosting](/best-private-html-hosting)

## Use cases

- [All use cases](/use-cases)
- [Share with clients](/share-with-clients)
- [Send a file to a client](/share-html-file-with-client)
- [Share Claude artifacts](/share-claude-artifacts)
- [Share Jupyter notebooks](/share-jupyter-notebook-html)
- [Host Storybook privately](/host-storybook-privately)
- [Architecture diagrams](/share-architecture-diagrams)
- [AI-generated reports](/host-ai-reports)
- [Internal HTML tools](/internal-tool-hosting)
- [Private HTML hosting](/private-html-hosting)
- [Vibe-coded page hosting](/vibe-coding-hosting)
- [Leave a website builder](/website-builder-migration)

## Learn

- [Blog](/blog)
- [Glossary](/glossary)
- [FAQ](/faq)
- [Where AI output should live](/where-ai-output-lives)
- [Agent-loop hosting](/agent-loop-hosting)
- [Why agents need a publish primitive](/blog/why-agents-need-a-publish-primitive)
- [MCP servers explained](/blog/mcp-servers-explained-for-developers)
- [What changed in the 2026-07 MCP spec](/blog/mcp-2026-spec-changes)
- [Sites in Codex explained](/blog/sites-in-codex-explained)
- [Private-by-default hosting](/blog/private-by-default-html-hosting)
- [An agent paid us $1 (x402)](/blog/agent-paid-to-provision-itself)
- [When a loop hits a paywall](/blog/loop-engineering-paywall)
- [Pricing](/pricing)
- [Self-host (new)](/self-host)
- [Changelog](/changelog)
- [Docs](https://stacktr.ee/docs)
- [About](/about)
© 2026 Stacktree · stacktr.ee

[Privacy](/privacy)[Terms](/terms)[Security](/security)[Dashboard](https://app.stacktr.ee)[npm](https://www.npmjs.com/package/stacktree-mcp)[Sitemap](/sitemap.xml)[llms.txt](/llms.txt)[API spec](/openapi.json)

---
Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt