Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Collect visual feedback on a website built with Claude Artifacts. Create a BugSmash Website project with a public URL or a site protected by Basic Auth, then share its review link for contextual comments. Other application logins, SSO, CAPTCHA, VPN and network restrictions may require the Feedback Widget or HTML workflow. This is not a native Claude Artifacts integration: BugSmash reviews the resulting browser page and does not connect to Claude Artifacts itself. Current shared artifacts require a Claude account, and artifacts that use Claude or connect to apps cannot use Anyone with the link. Use a legacy public artifact or export and deploy standalone HTML for an account-free website review. https://your-deployed-artifact.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Claude Artifacts integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your Claude Artifact
Turn a design, landing page, dashboard or interactive prototype into a reviewable deliverable. Use a public legacy artifact link, or export and deploy the web output, then collect contextual comments in one approval workflow.
Loved by1,250+Agenciesand companies in 100+ countries
Claude Artifacts can be shared. Access depends on the artifact type.
Anthropic now distinguishes current artifacts from legacy artifacts made in a chat before September 16, 2026. Their sharing and account requirements are not the same.
Choose the review path with these four rules in mind:
01
Current shared artifacts require a Claude account.
Even when access is set to Anyone with the link, viewers must sign in to Claude. Email invitees also need a Claude account using the invited address.
02
Some artifacts cannot be shared by public link.
Artifacts that connect to apps or use Claude cannot use Anyone with the link. Team and Enterprise owners can also disable external sharing.
03
A legacy artifact follows different rules.
On Free, Pro and Max plans, a legacy artifact published from a chat can be opened and used by anyone with the link without a Claude account. Legacy artifacts can also be embedded on allowed domains.
04
Sharing a Claude wrapper is not the same as deploying a website.
Artifacts can include single-page websites and interactive tools, while Claude Design can export standalone HTML. Exporting and deploying that output gives the review a normal web URL independent of Claude's account gate.
BugSmash works around the wrapper when needed:
review a public legacy artifact, or use the exported and deployed web output as the stable browser deliverable while keeping comments and approvals in the same project as every other asset.
How it works
Three steps to review a Claude Artifact
11
Choose a shareable output
Use a legacy artifact you can publish publicly, or export a Claude Design as standalone HTML and deploy it to a URL. Current shared artifacts keep Claude's sign-in and access rules.
22
Send one review link
Paste the public or deployed URL into BugSmash and share the resulting link. Reviewers comment on the output without editing the source conversation.
33
Track the decisions
Keep comments, statuses, screenshots and approvals with the deliverable, then send implementation work to Jira, ClickUp, Monday, Asana, Trello or Slack.
Review Claude-generated web output with the right context
Review a public or deployed surface
Use a public legacy artifact or exported standalone HTML deployed to a URL reviewers can reliably open.
Pin feedback to the visible output
Comments attach to the element or area being discussed instead of relying on descriptions copied from the Claude conversation.
Capture browser and device context
Every report includes the screenshot and environment needed to reproduce what the reviewer saw.
Keep the source conversation separate
Review the deliverable without making the Claude chat, its instructions or its working context the approval record.
Track versions and approval
Keep each exported or deployed iteration connected to its feedback, status and final sign-off.
Review more than the Artifact
Put the web output beside documents, images, presentations and video from the same project.
Which Claude Artifact link can I review?
Current shared artifacts require a Claude account, while a legacy published chat artifact can be opened without one. Exported and deployed HTML behaves like a normal website.
Your URL
Review by URL
What to do
Exported standalone HTML on a public domain
Works
Deploy the exported output, paste its public URL, and review it like any other website.
Legacy artifact published from a Free, Pro or Max chat
Public link
Anyone with the link can open it without a Claude account. Verify the artifact behaves correctly in the review window before sending the round.
Current artifact shared as Anyone with the link
Claude sign-in required
Every viewer must sign in to Claude. For an account-free client review, export and deploy the output instead.
Artifact shared by email invitation
Claude sign-in required
The invitee must use a Claude account with the invited email address.
Artifact that uses Claude or connects to apps
No public link
Anthropic does not allow Anyone with the link for these artifacts. Export a non-connected version or deploy a separate browser frontend.
Team or Enterprise artifact with external sharing disabled
Organization only
An owner must allow external sharing, or the output must be exported and deployed elsewhere for external review.
Using the Feedback Widget with Claude-generated output
Install the BugSmash script in the deployed frontend when the review depends on application state, authenticated flows or exact runtime behavior. The widget belongs in the deployed web output, not in Claude's hosted sharing interface.
The feedback workflow for teams using Claude Artifacts
From interactive prototypes to stakeholder reviews, keep creators, product teams and clients aligned on the exact artifact being shared.
Turn Artifact feedback into implementation work with context attached
A comment on the reviewed output becomes a task with the URL, selected element, screenshot, browser and device details ready for the team acting on it.
Context stays attached from comment to completion.
Comment captured
Hero section
Mobile
Context travels with it
Nothing gets lost in translation
Page URL
Clicked element
Screenshot
Browser and device
Task ready
Feedback with full context
Visual evidenceScreenshot attached
EnvironmentBrowser and device included
Send to your workflow
The destination changes. The context does not.
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
The Artifact is one deliverable. Review the full project around it.
Keep the deployed web output with its supporting document, PDF, presentation, images, video, email and mobile experience in one approval workflow.
Ship faster togetherThe all-in-one workspace for product teams.
Get started free
MayaMake this hero image full-bleed
Live WebsiteURL
product-launch.mp4
0:42 / 3:15
LeoTrim the intro to 0:03
VideoMP4
sneaker.glb
AvaSmooth these edges a bit
3D ModelGLB · GLTF
Quarterly Review
Q3 Performance
Revenue up 24%1.2k new usersNPS score 62Churn down 3%
BugSmash3 / 18
SamUpdate the Q3 numbers
Slide DeckPPT
Your summer sale starts now 🌞
A
Acme Store
to you
9:24 AM
Up to 40% off
Summer essentials, restocked
Shop the sale
NoahStronger CTA copy here
EmailHTML
9:41
Good morning
Dashboard
Balance
$4,280
ZoeAlign the chart legend
Mobile AppAndroid · iOS
Annual Report2025 in review
This year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.
Fig 1. Coastal expansion, 2025
Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.
Can anyone open a Claude Artifact shared as Anyone with the link?
For current artifacts, no: Anthropic says every viewer needs a Claude account, even with Anyone with the link. On Team and Enterprise plans, an owner must also allow external sharing.
What is the exception for a legacy artifact?
A legacy artifact published from a Free, Pro or Max chat can be opened and used by anyone with the link without a Claude account. Anthropic defines legacy artifacts as artifacts made in a chat before September 16, 2026.
Can an artifact that uses Claude be shared publicly?
Not through Anyone with the link. Anthropic says artifacts that use Claude or connect to apps cannot use that sharing option. Viewers of Claude-powered artifacts also use their own Claude account and plan limits.
Can I review an exported Claude Design?
Yes. Anthropic documents standalone HTML as an export option for Claude Design. Deploy that export to a public URL and review it as a normal website.
Do Claude Artifacts already support comments?
Current artifacts can offer Can view, Commenter and Can edit access, depending on artifact type. That collaboration remains inside Claude. BugSmash adds a browser-deliverable review record and connects it with task tools and the rest of the project's files.
Will reviewers see my Claude conversation?
A shared current artifact is shared through its own access controls. For legacy artifacts made in a chat, Anthropic warns that viewers may also receive access to attachments and files in that chat, so check for sensitive documents before sharing.
What is the safest external client workflow?
Export the web output, deploy it to a URL you control, and review that URL. This avoids requiring the client to enter Claude and keeps the original conversation and workspace access separate from approval.
Can I install the BugSmash Feedback Widget inside Claude's hosted artifact page?
No. Install it in web output you control after export or deployment. Claude's hosted sharing interface has its own access and collaboration controls.
Review Claude Artifacts without chasing feedback
Paste a public artifact or deployed output URL and send the first review link in under a minute.
BugSmash works around the wrapper when needed:
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
MayaMake this hero image full-bleed
product-launch.mp4
LeoTrim the intro to 0:03
AvaSmooth these edges a bit
SamUpdate the Q3 numbers
Up to 40% off
NoahStronger CTA copy here
ZoeAlign the chart legend
EllaTighten this paragraph
TheoBoost the warm tones
MiaCut the dead air at 1:12