Notion pages can run HTML now. Here is the plain reading.

What Notion shipped

The announcement is one sentence long and carries a lot: "New block in Notion: HTML. Build interactive HTML right on your Notion page. Ask AI to turn your content into interactive explainers, prototypes, or diagrams. Share with your team to use and tinker together." The release notes for Notion 3.6 add the worked examples: Notion Agents can build a custom ROI calculator for a client presentation, a quiz with questions drawn from your content, or an org-chart visualization generated from your people database.

The mechanics, as documented, run through Notion Agents rather than a code editor. You describe what you want, the agent writes the HTML against your page's content, and the block renders it in place, interactive, not a screenshot. The same release also shipped External Agents, which lets Claude and Cursor work inside Notion, and wider file support for Office formats. Taken together, the 3.6 release is Notion positioning its pages as a surface agents write to, not just a place humans type.

Why this existed as a hack first

One reason to take the feature seriously: people were already doing this the hard way. Rendering real HTML in a Notion page previously meant third-party workarounds, code blocks with magic captions rendered by external site builders, embed services, converter libraries. A workaround ecosystem is the strongest demand signal a feature can have. Users wanted interactive things inside their docs badly enough to duct-tape them in; Notion just made it native and put an agent on the authoring side.

The fifth container this year

Zoom out and this is a pattern, not a feature. In the last year: Claude ships artifacts and then Live Artifacts, dashboards that re-query your apps. OpenAI ships Codex Sites, full apps on a workspace URL. Shopify ships Quick, an internal hosting surface. Slack starts rendering HTML attachments inline. And now Notion renders agent-built HTML as a first-class block. Five major products, one identical move: let the agent's HTML output render inside our own walls.

The shared premise is worth stating plainly, because it is the most important thing happening in this corner of software: HTML has won as the output format of AI. When an agent needs to hand a human something interactive, a calculator, a dashboard, a prototype, a report, it writes HTML, and every platform is now racing to be the place where that HTML lands. Each of them scopes it to their own container, because the container is the product they are defending. That is rational for them, and it is also exactly why the same gap keeps reappearing.

What is not documented yet

The launch material is a tweet and a release-notes entry, so a fair reading has to name what is not answered. As of launch day, Notion has not documented:

• Public-page behavior. Whether an HTML block renders on a page shared to the web, or only for workspace members.
• The sandbox. What the HTML can do: scripts, network requests, external resources. A block that runs against your workspace data presumably has real limits; they are not published.
• Bring-your-own HTML. Whether you can paste hand-written HTML, or only generate through the agent.
• API and external-agent access. Whether the block is writable through the public API, or by the External Agents that shipped in the same release.
• Plans and platforms. Which tiers get it, and how it behaves on mobile.

None of these are criticisms of a day-old feature. They are the questions to check before you rely on it for anything beyond a team page, and this post will be updated as Notion documents them.

The gap: a block is not a link

Full disclosure: we build Stacktree, a host for agent-made HTML, so read this section as us describing where we sit in the pattern rather than neutral advice.

The HTML block is scoped to a Notion page, and Notion's own framing is honest about it: share with your team. Who can see the block is whoever can see the page. That is the right shape for an internal calculator or a team quiz, and the wrong shape the moment the person who needs the thing is not in your workspace: a client who should not be invited into your Notion, a stakeholder who just needs a link, a report that should expire after the engagement, a page that needs a password rather than a workspace membership.

That job needs the HTML to exist as its own artifact, on its own URL, with its own access rules. Stacktree does that one thing: an agent publishes the HTML over MCP and gets back a private, unguessable link the viewer opens with no account, gateable by password or email domain, with an expiry if the page should clean itself up. The block and the link are complements, not competitors. Inside the workspace, the block is better; the moment the audience is outside it, the block has no answer and the link is the answer.

What to watch

1. The documentation filling in. Public-page rendering and the sandbox rules decide how far the block can stretch beyond team pages.
2. API and External Agents access. If any agent can write HTML blocks, Notion pages become a render target for the whole agent ecosystem, and the authoring side stops being Notion-exclusive.
3. Whether the pattern keeps repeating. Five containers now render agent HTML. Each new one strengthens the same conclusion: the output format is settled, and the remaining competition is over where it lives and who gets to see it.