Hosted by the chatbot / Five experiments

ChatGPT Sites
and Claude Artifacts.

ChatGPT and Claude will both host what you build and hand you a link. What you actually got shows up when other people use it. Open one team board as four different people, save a record and get it back, break a permission and repair it, and follow a summary to the account it draws on.

5 experiments · Every rule from OpenAI’s and Anthropic’s documentation · Sources read October 14, 2026

How to read a result

Each result has two parts: what happened in the simulation, such as Opened, Blocked, or Unresolved, and how well the sources support it.

Documented A reviewed source says so.
Not documented The sources are silent, so nothing is simulated: no record, no zero, no refusal.
Conflicting documentation Two official sources disagree. Both sentences are shown, and neither wins.
Illustration A choice made for this invented board, not a platform rule.

Experiments

01 Send the same link
02 What survives closing the tab?
03 Open the mechanism behind one click
04 Reverse who calls whom
05 Follow the usage attribution
Sources and limits

The cast, all invented: Priya owns a team board in the Northwind ChatGPT Business workspace and the Northwind Claude Team organization. Tomas is her teammate, Lena works for an outside agency, and the fourth visitor has no account at all.

The experiments, worked through

Every result below comes from the page’s model, the same rules the experiments run. Priya, Tomas, Lena, and their board are an illustration; the rules come from the sources.

01 · Send the same link

Priya shares the board with her workspace and her organization. Four people open the same link, then the Claude side switches to a public Code page.

ChatGPT Sites · Priya: Opened. Priya owns it, so it always opens for her. Documented [1] [3]
Current Claude artifact · Priya: Opened. Priya owns it, so it always opens for her. Documented [7]
ChatGPT Sites · Tomas: Opened. Tomas is a workspace member; ChatGPT identity enforces the setting. Documented [1] [3]
Current Claude artifact · Tomas: Opened. Signed in to the Northwind organization. Documented [7]
ChatGPT Sites · Lena: Blocked. Lena is not in the Northwind workspace. Documented [1] [3]
Current Claude artifact · Lena: Blocked. Lena is not signed in to the organization. Documented [7]
ChatGPT Sites · Anonymous: Blocked. Anonymous is not in the Northwind workspace. Documented [1] [3]
Current Claude artifact · Anonymous: Blocked. Anonymous is not signed in to the organization. Documented [7]
ChatGPT Sites · Anonymous: Opened. A public Site needs no workspace access. Documented [1] [3]
Claude Code artifact · Anonymous: Opened. The Code guide opens a public link with no sign-in; the admin guide says every artifact needs a Claude account. Conflicting documentation [7] [8] [11]Conflicting documentation: “People need a Claude account to open any artifact except a legacy artifact published from chat.” [8] and “Publicly: share a link that anyone on the internet can open, with no claude.ai sign-in required.” [11]

02 · What survives closing the tab?

Tomas adds a status, closes the tab, and reopens it; Priya opens it after him. Then the artifact switches to personal storage, and the Claude side to a Code page.

ChatGPT Sites · Tomas: Saved. Saved in the Site’s D1 database. Documented [1] [3]
Current Claude artifact · Tomas: Waiting for approval. Claude shows a confirmation that this data will be visible to others using the artifact. Documented [6] [7]
Current Claude artifact · Tomas: Saved. Saved where everyone sees it. Documented [6] [7]
ChatGPT Sites · Tomas: Reopened. 3 status lines come back from D1, the same for every visitor. Documented [1] [3]
Current Claude artifact · Tomas: Reopened. 3 status lines come back from shared storage. Documented [6] [7]
ChatGPT Sites · Priya: Reopened. 3 status lines come back from D1, the same for every visitor. Documented [1] [3]
Current Claude artifact · Priya: Reopened. 3 status lines come back from shared storage. Documented [6] [7]
Current Claude artifact · Tomas: Saved. Saved where only Tomas sees it. Documented [6] [7]
Current Claude artifact · Priya: Reopened. 3 status lines come back from shared storage. Tomas’s personal records stay with Tomas. Documented [6] [7]
Claude Code artifact · Tomas: Unresolved. Not established: the page is “one self-contained page with no backend”, and the docs describe no storage for it. Not documented [11]
ChatGPT Sites · Priya: Published. The deployment URL serves the new version. Documented [1] [3]
Claude Code artifact · Priya: Published. Open pages update in place. Documented [11]

03 · Open the mechanism behind one click

The path of Tomas’s status write. Paths are schematic: the participants are documented, the order between them is not.

ChatGPT Sites · Tomas: Saved. Saved in the Site’s D1 database. Documented [1] [3]
Claude Code artifact · Tomas: Unresolved. Not established: the page is “one self-contained page with no backend”, and the docs describe no storage for it. Not documented [11]

ChatGPT Sites path: Tomas presses the button. → Tomas’s request for the board, checked against its audience. → oai-authenticated-user-email and oai-authenticated-user-full-name for Tomas. → The Site’s server code decides what this request may do. → INSERT the status “Fixed the login redirect.”.

Claude Code artifact path: Tomas presses the button. → Tomas’s request for the board, checked against its audience. → The static page, served from *.claudeusercontent.com. → No backend to send it to: not established.

04 · Reverse who calls whom

First the Site reads Tomas’s connected issue tracker. Then a ChatGPT conversation reads the Site through a plugin, first without plugin access, then with it. Both tasks only read.

ChatGPT Sites · Tomas: Waiting for approval. Tomas reviews the app access the Site requests and chooses an account. Documented [1] [3]
ChatGPT Sites · Tomas: Loaded. Tomas’s issues replace the snapshot. Nothing is written. Documented [1] [3]
ChatGPT Sites · Tomas: Blocked. Sharing the Site does not share its plugin: Tomas needs plugin access too. Documented [4]
ChatGPT Sites · Tomas: Read. Status lines return to the conversation. Nothing is written. Documented [1] [3] [4]

05 · Follow the usage attribution

Tomas and Priya each press Summarize. On a current artifact the call counts against the viewer’s own plan, Priya’s included. On a Site and a Code page the sources do not establish a model call.

Current Claude artifact · Tomas: Summarized. A summary appears, drawn on Tomas’s plan. Documented [6] [7] [8]
ChatGPT Sites · Tomas: Unresolved. Access passed. The sources document no built-in model call for a Site; Sign in with ChatGPT documents plan usage for open-source and locally hosted apps only. Not documented [1] [3] [5]
Current Claude artifact · Priya: Summarized. A summary appears, drawn on Priya’s plan. Documented [6] [7] [8]
ChatGPT Sites · Priya: Unresolved. Access passed. The sources document no built-in model call for a Site; Sign in with ChatGPT documents plan usage for open-source and locally hosted apps only. Not documented [1] [3] [5]
Claude Code artifact · Priya: Unresolved. Access passed. The Code docs describe connector calls and downloads, not a model call, for a page with no backend. Not documented [11]

A compact comparison

Question	ChatGPT Sites	Current Claude artifact	Claude Code artifact
What you publish	A deployment with saved versions and a production URL.	An object in the Artifacts tab, with platform capabilities.	One self-contained page with no backend, updated in place.
Where a new one starts	Owner and workspace admins.	Private to its creator.	A private URL.
A viewer with no account	Opens a public Site.	Cannot open it, even with the link.	Opens a public link, in conflict with the admin guide.
Shared records	D1, written by the Site’s server code.	Shared or personal storage, text only.	No storage described.
Each viewer’s connected data	Workspace-private Sites, workspace members only.	Not with “Anyone with the link”.	Blank for viewers not signed in or outside the organization.
A model call for viewers	Not established by these sources.	On each viewer’s own plan.	Not established by these sources.

Access / 01

Send the same link

Priya sends one link to the board on each platform. Pick who opens it. A refusal replaces the board with the rule that stopped it; a permitted view shows the board that person actually gets.

Storage / 02

What survives closing the tab?

Add a status and watch where the record goes. Close the tab, reopen it, and look again as Priya: shared records come back for everyone, personal ones only for their owner, and a Code page has nowhere to put one.

Mechanism / 03

Open the mechanism behind one click

Trace any committed action. Play, step, or scrub it; the replay draws what already happened and never runs the action again. Select a station to see what the action carries there.

Direction / 04

Reverse who calls whom

A Site can sit on either side of a connection. First it reads Tomas’s connected app; then a ChatGPT conversation reads the Site through a plugin. Switch either permission off and send the token again.

Usage / 05

Follow the usage attribution

Each Summarize becomes a receipt in the stack of the account it draws on. Where the sources establish no model call, the receipt lands in a stack that says so, never in a free one.

Sources and limits

Every source was re-read on October 14, 2026. A date is given where the source states one; otherwise the entry says when it was read. The citation numbers are the ones every result uses.

OpenAI

Sites, ChatGPT docs . Read October 14, 2026.
“What’s new”, ChatGPT docs . Entries for June 1–5, 2026, August 17–21, 2026, and DevDay 2026. Read October 14, 2026.
Creating and using ChatGPT Sites, OpenAI Help Center . Read October 13, 2026; a bot check blocked the re-read on October 14, 2026.
Hosting a plugin with ChatGPT Sites, OpenAI Help Center . Read October 13, 2026; a bot check blocked the re-read on October 14, 2026.
Sign in with ChatGPT, ChatGPT plan usage overview . Read October 14, 2026.

Anthropic

What are artifacts and how do I use them?, Claude Help Center . Read October 14, 2026.
Share artifacts, Claude Help Center . Read October 14, 2026.
Artifacts admin guide for Team and Enterprise plans, Claude Help Center . Read October 14, 2026.
Build live dashboards and animate explainers with Claude , October 8, 2026. Read October 14, 2026.
Build and share AI-powered apps with Claude , July 25, 2025, updated July 31, 2025. Read October 14, 2026.
Share session output as artifacts, Claude Code Docs . Read October 14, 2026.

Dates the sources give

July 25, 2025: Claude artifacts that call Claude, in beta on Free, Pro, and Max; Team and Enterprise followed on July 31, 2025. [10]
June 1–5, 2026: Sites, to create, save, deploy, and inspect hosted websites. August 17–21, 2026: co-editing and editable Site URLs. DevDay 2026, with no day given: Sites with connected data. [2]
September 16, 2026: artifacts made in a chat before this date are legacy artifacts. [6]
October 8, 2026: Dashboards in beta on paid plans and Motion in beta on Team and Enterprise; Docs, Slides, and Design out of beta on every plan. [9]

Could not be re-read

Sources 3 and 4 answered with a bot check on October 14, 2026, and are cited from their October 13, 2026 reading. The three pages below have answered with a bot check on every attempt, most recently October 14, 2026. No statement on this page rests on them, and their dates and section numbers are left out rather than quoted from memory.

ChatGPT release notes
ChatGPT Sites Terms
DevDay 2026 recap

Invented for this page

Priya, Tomas, Lena, the anonymous visitor, their Northwind workspace and organization, the team board, its status lines, issues, announcements, and summaries. Nobody built either app.
The board’s own design choices, each marked Illustration where it decides a result: who may write a status, that opening the board makes no database query, and that the Site’s plugin has one read tool.
The order of the stations on each traced path. The participants are documented; the order between them is not.
Every count on the page: status lines added, summaries requested, and versions published. Each is a simulated count of button presses, never a quota, tokens, money, or platform cost.

Not established by the reviewed sources

The engine that runs a Site’s server code.
A built-in model call for a Site, or for a Claude Code page.
App storage for a Claude Code page.
Whether a Site shared with invited external viewers still counts as private to its workspace.
Whether artifact storage works for an invitee from outside the organization.
A creator payout program on either platform.
Launch dates for Claude Code artifacts.

Left out on purpose

Plan prices, Site and artifact counts, model quality, custom GPTs and the GPT Store, the Apps SDK as a product, Cowork, and Claude Tag.