You sent a client the public link to a Claude Code artifact and asked them to mark up what to change. There's nowhere to comment. That's by design. Here's the rule, which plans it leaves without a comment option for outside viewers, and how to collect pinned notes anyway. Checked against Anthropic's docs on 15 September 2026.
You used Claude Code to build a prototype, a monthly report or a proposal page for a client. You shared it, sent the link and wrote "just mark anything you want changed right on the page."
The client writes back that there's nowhere to mark anything. Or you open the link yourself and see this at the top:
Comments aren't available while this Artifact is shared publicly.
This isn't broken and there's no setting to hunt for. It follows from how Claude Code sharing works, and which way around it depends on where your client sits.
Because the link is public. Here are the relevant lines from Anthropic's Claude Code documentation, as of 15 September 2026:
"You need Claude Code v2.1.221 or later and a Team or Enterprise plan, because only an artifact you share within your organization takes comments."
"If you share an artifact publicly, viewers can't comment on it: the page says
Comments aren't available while this Artifact is shared publicly.To switch an artifact that already has comment threads to a public link, delete the threads first."
So comments belong to organization sharing. A public link and a comment thread don't exist on the same artifact, and switching from one to the other means giving up the thread.
One more line from the same page:
"On Pro and Max plans, a public link is the only way to share an artifact."
Put that next to the rule above and you get a conclusion Anthropic doesn't state in one sentence but that follows from the two they do: on Pro and Max, no one can comment on a shared Claude Code artifact. The only way to share is a public link, and public links don't take comments.
Two caveats. First, this is our reading of two separate sentences, so if it decides something for you, look at the Share control in your own account. Second, Anthropic's own pages have disagreed about which plans get Claude Code artifacts at all. We covered that, along with who can open each kind of link, in Claude Code wants to publish an artifact. Who can open that link?
| Who needs to comment | Your plan | What works |
|---|---|---|
| People inside your organization | Team / Enterprise | Share within the organization and comment in Claude |
| People inside your organization | Pro / Max | No organization share on these plans, so move the page out (below) |
| A client outside your organization | Team / Enterprise | They'd need a public link, which has no comments, so move the page out |
| A client outside your organization | Pro / Max | Public link only, no comments, so move the page out |
When everyone who needs to comment is already in your organization. A colleague reviewing a dashboard, a product lead checking a prototype, a team going through an investigation write-up: they're signed in to claude.ai as members already, the thread sits on the same artifact the session built, and there's no second tool to explain.
For that case, don't move anything. An organization share with comments is designed for exactly this.
The table's other rows are about people who can't be in that thread: clients, outside stakeholders, anyone who isn't a member of your organization. For them, a Claude artifact on its own can't give you notes on the page.
Move the page somewhere that accepts comments from people without an account. With miinideck:
Notes are tied to the layout they were left on. The workspace has a desktop view and a mobile view, and a comment pinned on the phone layout stays on the phone layout rather than drifting onto a different element in the desktop one.
Upload the exported HTML, turn Review on and send the link. Your client clicks the spot they mean and types, with no account. Review and comments are free on every plan.
This is where the round trip closes, and where plans differ.
On Studio, export the thread. It comes out as markdown: each note numbered, grouped by desktop and mobile, tagged with the layout width it was left on and the text of the element it points at. Paste that into your Claude Code session and ask for the changes. Claude gets the same "this heading, on the phone layout" precision your client had, without you re-describing it.
On other plans, the comments are all there to read on the page. You brief Claude from them yourself, and tick each one resolved as it's done.
Then replace the file. The link stays the same, so the client reopens the address they already have and sees the new version. The six-step version of this loop, with what the export looks like, is in how to collect pinned feedback on a shared HTML page and send it back to your AI.
Our comments don't reach Claude by themselves. A note left on a miinideck page stays there until you export it or read it. Nothing wakes a Claude Code session when a client comments. If what you want is feedback that lives right next to the session that built the page, and your reviewers are in your organization, the Claude side is the better fit.
A page that reads live data doesn't travel as live data. Anthropic's documentation says an artifact that calls connectors can't be shared to a public link on any plan. To hand that kind of page to a client, ask Claude to pull the data now and put it into the page as a dated snapshot, then export that. The client comments on the numbers as of that date, not on a live view.
A page that needs a backend isn't a file. If the prototype saves what people type, handles sign-in or stores uploads, lifting out the HTML leaves a front with nothing behind it. That needs a real deployment on a platform that runs a server, such as Vercel or Netlify, not a static host.
Existing Claude threads don't come with you. If an artifact already has comments and you decide to make it public, the documentation says to delete the threads first. Copy out anything you still need before you do.
The permission prompt arrives mid-session and the honest answer is: by default, only you. What publishing actually does, when a link becomes public, and where Anthropic's own pages disagree — on which plans have it, and on whether a public link needs a Claude sign-in. Checked against their docs on 12 September 2026, sign-in rechecked 19 September 2026.
You sent a Claude Slides deck with 'anyone with the link' and your client got a sign-up screen. Why that happens, what Docs, Slides and Design actually export, and how to get the work in front of someone who will never make a Claude account.
Hit a ChatGPT Sites usage limit? Your Sites aren't gone. Here's how to tell the ones that are just pages, which travel, from the ones that need Sites underneath them.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.