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 v0. 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 v0 integration: BugSmash reviews the resulting browser page and does not connect to v0 itself. Deploy the browser app before sharing its URL. The .vercel.app example is a Vercel deployment; a shared v0 chat is a separate collaboration surface from the published website. https://your-project.vercel.app Platform clarification: this is a generic BugSmash Website project workflow, not a native v0 integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your deployed v0 app
Paste the browser-accessible Vercel production or preview URL, send one review link, and collect contextual comments on the app version you want stakeholders to evaluate.
Loved by1,250+Agenciesand companies in 100+ countries
v0 chat sharing, sandbox previews and deployments are separate surfaces.
v0 builds inside a chat and deploys projects to Vercel. Choose the deployed browser URL when the goal is frontend review rather than prompt collaboration.
Four documented boundaries shape the review workflow:
01
Preview and production deployments have different URLs.
Working branches get preview deployments with unique URLs and do not change the project's stable production URL. Publishing updates the production deployment.
02
Chat sharing exposes the build conversation.
A shared v0 chat can show prompt history and generated components, with visibility and view/edit permissions controlled separately from the deployed application.
03
The sandbox is not the deployed app.
Each chat has its own VM-backed sandbox, and v0 says the sandbox is never the same machine as the deployed app. Production uses separate Vercel infrastructure and environment variables.
04
Deployment access is configurable.
The first-publish flow includes visibility, and the connected Vercel project can use Deployment Protection or Vercel Authentication. A deployment URL is not necessarily public.
BugSmash keeps stakeholder feedback on the deployed app:
share the selected production or preview deployment, leave prompt history and code collaboration in v0, and use the Feedback Widget when deployment or application access blocks pasted-URL review.
How it works
Three steps to a reviewed v0 app
11
Choose a Vercel deployment
Publish the current work to the stable production URL, or select the working branch preview when that exact pre-production version is the review target.
22
Send one BugSmash link
Paste the browser-accessible deployment URL into BugSmash and share the resulting review link instead of exposing the v0 chat and prompt history.
33
Publish the approved changes
Resolve comments in v0, select Publish Changes when the production version is ready, and verify the stable production URL before sign-off.
Review the deployed v0 app, not the build chat
Comment on the selected deployment
Keep every note attached to the exact production or working-branch preview URL under review.
Protect prompt history
External website review does not require sharing the v0 chat, its prompts or its edit permissions.
Check responsive layouts
Review desktop, tablet and mobile presentation from the same deployed browser app.
Capture technical context
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
Track the stable production release
Future production deployments update the Vercel project at its stable production URL, making it the durable address for release review.
Use the widget for protected states
Install the BugSmash Feedback Widget when feedback must be collected inside an authorized or stateful deployment.
Which v0 or Vercel link should I review?
Choose a deployment URL based on the version and access policy you want reviewers to use. Chat visibility does not determine deployment visibility.
Your URL
Review by URL
What to do
Public Vercel production domain
Works
Paste the stable production URL and review the release currently served there.
Public custom production domain
Works
Use the connected domain after the intended production deployment is live.
Public working-branch preview deployment
Works for that version
Use its unique URL when the review should stay on that pre-production branch build.
Deployment protected by Vercel access controls
Access-dependent
Vercel Authentication, Passport, Password Protection or Trusted IPs still apply. Confirm authorized access or use the widget inside the deployment.
Shared v0 chat or sandbox preview
Use a deployment URL
Chat sharing exposes the generation workspace, and the per-chat sandbox is separate from the deployed app.
App behind application login or SSO
Use the widget
A pasted URL does not bypass application login or SSO. Install the Feedback Widget inside the authorized app experience.
Installing the Feedback Widget on a v0 app
Add the BugSmash script to the deployed Vercel application when reviewers need to comment inside a protected, logged-in or stateful flow. v0 chat permissions and Vercel deployment access remain separate controls.
The feedback workflow for teams using v0
Keep generation, chat collaboration and deployed-app approval distinct while every comment stays attached to the selected Vercel release.
Route an actionable website comment to the delivery team with its deployment URL, selected location, screenshot, browser, operating system and viewport context preserved.
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 v0 app is one deliverable. Review the complete launch together.
Keep the deployed app beside product PDFs, videos, images, presentations and other launch assets, with feedback and approval in one project.
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.
Use the Vercel deployment for frontend review. v0 describes chat sharing as a way to expose prompt history or collaborate on generated components; deployment visibility is managed separately.
What is the difference between preview and production deployments?
Working branches receive preview deployments with unique URLs that do not change the project's stable production URL. Publishing updates the production deployment served by the project domains.
How do I update the production app from v0?
Open Publish, review the selected production deployment and domain, then select Publish Changes. GitHub-backed projects follow their configured pull-request and branch-protection workflow.
Is the v0 sandbox the same as the deployed app?
No. v0 says each chat has its own VM-backed sandbox and that the sandbox is never the same machine as the deployed app, which runs on separate Vercel infrastructure.
How do v0 versions affect deployment?
Each time v0 updates a code block from a message, it creates a new version; direct file edits do not. Deployment uses the latest code, so restore an older version first if that is the version you need to deploy.
Can I review a custom domain?
Yes. v0 provides deployments with a unique vercel.app URL and lets you add a custom domain. Use whichever browser-accessible domain serves the intended deployment.
Can BugSmash open a protected Vercel deployment or an app behind SSO?
Vercel Deployment Protection and application authentication still apply, and a pasted URL does not bypass application login or SSO. Confirm the reviewer has authorized access or use the Feedback Widget inside the app.
Does BugSmash change v0 or Vercel deployment settings?
No. v0 and Vercel continue to control publishing, domains, visibility, environment variables and deployment protection. BugSmash provides the separate review and approval workflow for the rendered app.
Ship v0 apps without chasing feedback
Paste the selected Vercel deployment URL and send a focused review link without exposing the v0 generation workspace.
BugSmash keeps stakeholder feedback on the deployed app:
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