# Onlay vs Claude Code shared artifacts

> Claude Code can publish an HTML or Markdown artifact to a claude.ai link and read comments from your organisation. How that compares with Onlay, and when each is the better choice.

Claude Code can publish an `.html` or `.md` file as a shared artifact at a `claude.ai` address. Publishing again updates the same address, people in your Claude organisation can comment, and Claude can read those threads and reply. It is the closest thing to Onlay built into an agent, so the choice comes down to who your reviewers are.

Checked against [Anthropic's artifact docs](https://code.claude.com/docs/en/artifacts) in October 2026. If something here is out of date, tell us at hello@onlay.io.

## Side by side

| | Onlay | Claude Code shared artifacts |
|---|---|---|
| Who can comment | Anyone with the link, with no account (a name and email once), or only people you invite | Members of your Claude organisation it is shared with; people with only the public link cannot see or add comments |
| Plans that can share with others | Free and Pro | Organisation sharing is on Claude Team and Enterprise |
| Readers edit the text in place | Yes, when you turn editing on; the agent gets each edit as before and after | No |
| Which agents | Claude Code, Codex, Cursor, Copilot, T3 Code, claude.ai, any agent with a shell or an MCP client | Claude Code, signed in with a claude.ai account |
| What comes back to the agent | Edits, comment threads with quoted words, the block and the source lines, and page state, as a review or JSON | Comment threads Claude is asked to handle |
| More than one page | A whole folder or built app (Pro), or comments on an app you deploy yourself (Pro) | One page per artifact |
| Pages that ask a question | Yes: polls, choices and sliders whose answers come back on the pull | No |

## Choose Claude Code artifacts when

- Everyone who will review is in your Claude Team or Enterprise organisation.
- You only use Claude Code, and you want nothing else to install.
- Comments are enough; nobody needs to change the text themselves.

## Choose Onlay when

- Reviewers are outside your organisation, or don't have Claude accounts: a client, another team, friends.
- You want readers to fix wording in place and have the agent apply it to the source.
- You work with more than one agent, or with Codex, Cursor or Copilot.
- The thing to review is a whole site or a deployed web app.
- You want the answers to a question on the page (a poll, a choice), not only comments.

## Using both

They don't conflict. An artifact is a fine way to share inside your organisation; publish with Onlay when the page needs to go further.

---

This page as HTML: https://onlay.io/compare/claude-code-artifacts. Everything for agents: https://onlay.io/llms.txt