Your Dot talks to you in a thread. Your client needs a link.

Why a Dot's work leaves the thread as a link

A Dot is built to be talked to. OpenAI puts it in ChatGPT on desktop, web and mobile, in Slack and Teams, and on a voice call, with texting in a limited US beta. Each of those is a stream of messages. That is the right shape for "the venue confirmed" or "shall I send this?". It is the wrong shape for the thing the Dot was asked to make.

OpenAI's own examples of Dot work show it: keep a sales proposal current as the seat count and terms change, prepare revised launch copy and slides when the product changes, update a study's comparison chart and draft the findings. Each ends in a document someone else has to read, often someone who has never opened ChatGPT. Sending it as a message or an attachment goes wrong in predictable ways:

• A thread cannot hold it. A twelve-section proposal pasted into Slack or Teams is a wall of text, and worse on a phone.
• Attachments go stale. Keeping work current is the point of a Dot. Every revision sent as a file is another copy, and the reader has to work out which one is newest.
• ChatGPT's own sharing expects a ChatGPT user. Collaborators on a Space page each work with their own ChatGPT, and someone outside your workspace who is invited to a ChatGPT Site signs in with the account you granted access to. That suits a colleague more than a client.
• A file says nothing about whether it was read. An attachment in an inbox looks the same opened or not.

A link avoids those problems. The page opens in the browser the reader already has and stays at one address however many times the Dot revises it. Nobody needs an account to read it.

How a Dot reaches Stacktree

OpenAI's documentation gives a Dot two ways out to other services. It uses the supported plugins installed and enabled on your account, with the same connections and permissions as ChatGPT, Work and Codex. And it has its own cloud computer, with a browser, where it can run tools and reach the web. That gives three routes to Stacktree, and the first is the one to use.

1. The Stacktree plugin for ChatGPT: works with Dots

Stacktree is in ChatGPT's plugin directory as of 6 October 2026. Install it from Plugins in ChatGPT, connect your Stacktree account, and ChatGPT can publish and update pages on that account. A Dot uses the plugins installed on your account, with the same connections and permissions as ChatGPT, so your Dot can publish to a private link and update it at the same address. There is nothing to set up on the Dot itself. For a full example, see a Dot that sends your client the weekly report.

2. One request, no account: the route that needs no plugin

Stacktree's first publish needs no account and no key. One HTTP request sends the page and returns a private link:

curl -X POST https://api.stacktr.ee/sites -F file=@page.html

The response carries the link, an expiry 24 hours away, a keep_url for you, and a claim_token the agent can use to replace the page at the same address. The instructions an agent needs are at stacktr.ee/prompt.md and in stacktr.ee/llms.txt.

This is the route Grok Bot took on 20 August 2026. Given one sentence, it read our documentation and published unattended on the first attempt, with no plugin and no key. A Dot's cloud computer can browse and run tools, which is what this route needs. The plugin is still the simpler route, because the page lands in your account from the start and needs no claiming.

Two things could get in the way. An Enterprise administrator can switch off cloud browser use and cloud network access for Dots. And the Dot's approval checks may stop and ask you before it shares anything, which is why the wording in the next section matters.

3. A connector you add yourself: not documented for Dots

ChatGPT lets you add an MCP server yourself in developer mode, which OpenAI documents for testing: turn on Developer mode under Settings, Security and login, then add the server with the plus button in Plugins. Stacktree's server is at https://api.stacktr.ee/mcp, and connecting ChatGPT to Stacktree walks through it. OpenAI's Dots documentation does not say whether a Dot can use a connection added this way, and developer mode depends on your account and workspace policy. Now that the plugin is in the directory, install that instead, and treat developer mode as an experiment rather than a setup step.

What to say to your Dot

Whichever route you use, the request has the same shape. Ask for the page and the link together, and say who the page is for:

Turn the Q3 summary into one self-contained HTML page for
Dana at Northwind. Publish it privately to Stacktree, following
https://stacktr.ee/prompt.md, and send me the link before you
share it with anyone.

Naming the reader matters more with a Dot than with most agents. OpenAI says that before a Dot sends a message or shares a file, it seeks authorisation that covers the information and the type of recipient, and its auto-review check looks at actions that could share information before they run. A request that names Dana answers the question it would otherwise have to ask. Asking for the link back first keeps you as the person who sends it.

For changes, say "update the page you already published", not "publish a new version". Stacktree replaces a page at the same address, so the link Dana already has shows the new version and she never has two copies to compare. And keep passwords and keys out of anything you ask a Dot to publish.

For work that repeats, such as a weekly report, the weekly client report recipe has a full prompt: the Dot gathers the figures, updates the page the client already has, and tells you what changed.

When the client opens it, your Dot hears about it

Stacktree's plugin also sends MCP Events, OpenAI's way for an app to tell ChatGPT that something happened. OpenAI's guide says they work in Work chats and with Dots: you say what to watch and what to do when an update arrives, and ChatGPT subscribes. Stacktree sends six:

• First opened: someone opened the page for the first time.
• Opened by a named reader: the person on a named link opened it (names on Solo and up).
• Comment: a reader left a note on the page.
• Not opened yet: nobody has opened it 1, 24 or 72 hours after it went up.
• Signed off: a reader approved the page, with the name they gave.
• Expiring: the page is about to come down.

OpenAI's Gabriel Chua showed the pattern on 15 October 2026 with a ChatGPT Site that sends an event to his Dot, and suggested it for support requests and sales leads. For client work it reads like this:

Watch the Northwind proposal on Stacktree. When Dana comments,
fix the page at the same link and tell me what changed. If she
hasn't opened it after a day, draft a follow-up for me to send.

We have run the comment half in a ChatGPT Work chat: on 3 October 2026 a client's comment reached ChatGPT as an event in under half a second, and the page was fixed at the same link 50 seconds later. A connection to Stacktree made before it offered events may need its tools refreshed in ChatGPT's plugin settings before ChatGPT subscribes.

What the reader gets

• A page that opens in any browser, on any phone, with no account and no app.
• A link nobody can guess, never listed or indexed, with a passcode available on every plan, Free included.
• On Solo and up, a link with their name on it, so you see when that person opened it and get an email the first time they do.
• Comments on the page itself, with no account, when you switch them on.
• The current version every time, because revisions replace the page at the same link.
• A preview card when the link is pasted into WhatsApp, iMessage, Slack or Discord.

Keeping the link

A page published with no account lasts 24 hours. The keep_url in the response opens a page that shows when the link expires and how to keep it. Claiming the page into a Stacktree account replaces the 24-hour expiry with your plan's terms: on Free, 3 pages each live for 7 days, or once someone else opens one, for 30 days after their latest visit, up to 90 days in total; on Solo, at $19 a month, 25 pages with no expiry and a record of who opened what. Pricing has the rest.

Where this stands

Stacktree works with Dots. It has been in ChatGPT's plugin directory since 6 October 2026, and a Dot uses the plugins installed on your ChatGPT account, so once you install Stacktree your Dot can publish to a private link and update it at the same address. Dots are rolling out to Pro and Business Premium accounts first; until yours arrives, the same plugin works in an ordinary ChatGPT chat. The no-account route works for any agent that can make an HTTP request, and Grok Bot used it unattended. A connector added in developer mode is undocumented for Dots. If something does not work with your Dot, tell us.

For what Dots are, which plans include them and their limits at launch, see What are ChatGPT Dots?