Can't I just publish a Claude artifact and send the link?

Often, yes — for a page you want people to see, publishing the artifact is the fastest path there is. The link falls short when the reviewer is outside your Claude organization: people who open a public artifact link can't see or add comments, and on Pro and Max plans the only ways to share are private or public, with nothing in between.

Don't Claude Code artifacts have comments now?

Yes, since Claude Code v2.1.221 — for members of your Team or Enterprise organization. They can comment on an artifact shared inside the org, and Claude reads the threads and replies to the ones an editor sends to it. People whose only access is the public link don't see the comments and can't add any. Comma is for the reviewer who isn't in your Claude org — a client, an exec, a contractor — and for reports that didn't come from Claude.

What does Comma add on top of a Claude artifact?

A review layer and a lifecycle. Paste the artifact's HTML into Comma and reviewers can select any text or table cell and pin a threaded comment there after a free Google or email sign-in, with no Claude seat. The link can be public, password-protected, invite-only, or limited to your team or email domain. Regenerated versions land as revisions at the same URL, and any two revisions diff.

Does the artifact still run the same in Comma?

For HTML artifacts, yes. Comma renders the markup verbatim in a sandboxed iframe with scripts enabled, and loads scripts and styles from jsDelivr, unpkg, cdnjs and esm.sh — the CDNs generated pages usually use. React artifacts are source code rather than a page, so ask Claude for a self-contained HTML version before publishing.

Can Claude publish to Comma directly instead of me copying the HTML?

Yes. Claude Code, Claude Desktop and the Claude Agent SDK can attach Comma's MCP server; the agent publishes the page as a report, returns the URL, and on a later run reads the comments people left and replies or revises. Claude Code can publish its own artifacts too, but only from a session signed in to claude.ai — artifacts are off by default in the Agent SDK and GitHub Actions, and API-key sessions can't publish them. Comma's tools work the same from Codex, Cursor or a CI job.

Yes — unlimited reports, unlimited commenters and full MCP access on the free plan. You pay only for scheduled routines' AI compute, and you can bring your own AWS Bedrock key for that.

Comma vs Claude Artifacts

TL;DR

Claude Artifacts is where the page gets made. Comma is where anyone can review it. Claude publishes an artifact to a link in one step, and in Claude Code the people in your Team or Enterprise org can comment on it and have Claude reply. Comma picks up where that stops: comments from reviewers outside your Claude org with just a free sign-in, access that isn't all-or-nothing, and publishing from any agent or CI job, not just a signed-in Claude session.

They are not competing for the same moment. Most people who use Comma for AI-built pages made those pages in Claude.

At a glance

	Comma	Claude Artifacts
Made for	Reviewing HTML that already exists	Pages Claude builds in a chat or a Claude Code session
Input	Any HTML — from Claude, another model, a notebook, CI	What Claude generates in that conversation or session
Readers comment on it?	Yes — anyone you share with, anchored to text and table cells	Org members only (Team/Enterprise, Claude Code); public-link viewers can't comment
Agent reads the comments	Yes — any MCP client or the REST API	Claude Code reads and replies to threads an editor sends to it
Who can open the link	Public, password, invite-only, team or email domain	Private, org members (Team/Enterprise), or a public link
Reader needs an account?	No to read; free sign-in to comment	No, to read a public link; org sign-in to comment
Regenerate without new link	Yes — revisions at one URL, diff between any two	Yes in Claude Code — each publish is a new version at the same URL
Agent can publish	Yes — MCP server and REST API, scoped `comma_sk_…` tokens, CI	Claude Code signed in to claude.ai; not API-key sessions, off in Agent SDK and Actions
Pages from other tools	Yes — Plotly, Jupyter, Playwright, coverage, multi-file reports	One self-contained page Claude publishes; relative links don't resolve
Price	Free — pay only for routine AI compute	Included with Pro, Max, Team and Enterprise

Checked against the Claude Code artifacts docs in October 2026. Claude's sharing options change as the product evolves; check them for the current details of your plan.

What Claude Artifacts is good at

Zero-distance publishing. The page is generated, previewed and published in the same window, with no copy step and no second tool. For a calculator, a one-off visual explainer, or a small game you want to post somewhere, the published artifact is the right answer and Comma would be a detour.

Remixing. A viewer with a Claude account can open a published artifact and keep building on it in their own chat. That makes artifacts a good format for sharing a starting point — something you want other people to fork, not approve.

Review inside your org. In Claude Code on a Team or Enterprise plan, teammates comment on an artifact shared with the org, and Claude reads the threads sent to it, replies and republishes. If every reviewer has a seat in your Claude org and the page came from Claude Code, that loop already exists without a second tool.

What Comma is good at

Turning "here's a page" into "here's what we decided." The artifacts that end up in Comma are usually documents rather than toys — an analysis, a weekly summary, a migration plan, a design review — and the reason they were made is to get a decision out of someone. That takes a few things a public link doesn't give you:

Feedback on the specific line, from anyone. A reviewer — a client, an exec, someone with no Claude account — highlights the number that looks wrong and pins a thread to it. The next reader sees the question in place, not in a Slack thread three days later. See comment on HTML.
Access that matches the content. Internal numbers shouldn't sit at a public URL. Comma links can be invite-only, password-protected, or gated to your team or email domain — sharing options.
One URL across versions. Ask Claude to fix what the reviewers flagged, update the same report, and the link you already sent now shows the fixed version. Earlier revisions stay recoverable and diffable, and open threads carry across.
Any agent closes the loop. Over MCP, Claude Code, Claude Desktop, Codex or Cursor publishes the page itself — or a CI job does it over REST — reads the comments on its next run, replies in-thread, and marks them resolved when it has made the change — let an agent respond to comments.

Where each one wins

A page you want the internet to see

Claude Artifacts wins. One click, public by design, remixable. Use it.

Review where every reviewer is in your Claude org

Claude Artifacts, if the page came from Claude Code. Teammates on your Team or Enterprise plan comment in place and Claude answers. Bringing in Comma only pays off when someone outside the org needs to weigh in.

A document someone outside your org needs to sign off

Comma wins. Approval needs comments on specific content from the person approving, a record of what changed between the version they objected to and the version they approved, and a link you can restrict without giving them a Claude seat. That is the whole product.

Pages that came from somewhere other than a chat

Comma wins by default. Artifacts only hold what Claude generated in a conversation. The coverage report from CI, the notebook export, the Playwright run and the agent-written summary all go to the same place in Comma, reviewed the same way.

Work that repeats

Comma wins. A weekly report regenerated by a routine or a CI job updates one URL every run; the pinned message in the channel keeps working and last week's discussion stays attached.

Moving an artifact into Comma

In the artifact, copy the code. If it is a React component rather than HTML, ask Claude first: "Give me this as a single self-contained HTML file."
Paste it into Comma — or drop it into the free HTML viewer to check it renders, then hit Get a shareable link.
Send the URL. Reviewers can read it without an account and comment after a free sign-in.

Doing this more than once? Attach the MCP server and let Claude publish directly — setup for Claude Code and Claude Desktop.

Try Comma

Take the next artifact you were about to screenshot into a thread and send it as a page people can comment on instead.

Publish your first report →