Create the live deployment
Save the Cloud Agent work to a repository, connect Vercel, add the Vercel plugin when prompted, and publish the default branch to receive a deployment URL.
Deploy the frontend to a browser-accessible URL, send one review link, and collect contextual comments on the experience your users will actually open.












Loved by1,250+Agenciesand companies in 100+ countries
Cursor provides browser tools, Cloud Agent environments and a Vercel publishing workflow. Those tools support development, but they do not all create an external website-review URL.
Four documented boundaries matter before you share the work:
Agent can navigate, click, type, take screenshots, inspect console output and monitor network traffic while testing an app inside Cursor.
Cursor uses forwarded ports from a Cloud Agent environment to open the app on your machine in an internal browser. That preview is different from a live deployment URL.
A teammate needs both membership in the Cursor team and repository access to open another member's agent. Viewing is read-only unless team follow-ups are enabled.
After a repository exists, Cursor can add the Vercel plugin, link the repository to a Vercel project and deploy the default branch. Later commits to the default branch deploy automatically.
How it works
Save the Cloud Agent work to a repository, connect Vercel, add the Vercel plugin when prompted, and publish the default branch to receive a deployment URL.
Paste the browser-accessible deployment URL into BugSmash and share the review without granting access to Cursor, the repository or the Cloud Agent run.
Resolve the contextual comments in Cursor, commit the updates, wait for the deployment to update, and verify the live URL before approval.
Attach feedback to the rendered deployment rather than a code diff, agent transcript or internal preview.
External reviewers do not need Cursor team membership or repository access when the deployed site is public.
Review desktop, tablet and mobile presentation from the same browser-accessible release.
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
Use Cursor Browser for agent-led testing with screenshots, console and network inspection, and BugSmash for stakeholder comments and approval on the release.
Install the BugSmash Feedback Widget when feedback must be collected inside an authorized or stateful deployment.
Cursor is the development environment. Use the deployed web application URL when the goal is client or stakeholder review.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public Vercel deployment from Cursor | Works | Paste the deployment URL returned after Cursor publishes the repository. |
| Public deployment URL for the web app | Works | Paste the public website URL into BugSmash Website Feedback. |
| Vercel deployment with access protection | Access-dependent | Vercel Authentication, Passport, Password Protection or Trusted IPs still apply. Confirm authorized access or use the widget inside the deployment. |
| Cloud Agent forwarded-port preview | Use a live deployment | The forwarded port opens in Cursor's internal browser and is part of the development environment, not the published client URL. |
| Cursor Cloud Agent run link | Not a website review URL | The viewer needs Cursor team membership and repository access. Share the deployed frontend instead. |
| 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. |
Add the BugSmash script to the deployed frontend when reviewers must comment inside a logged-in, role-specific or stateful flow. Cursor team access, repository permissions and deployment protection remain separate controls.
Keep agent-led development, repository collaboration and stakeholder approval distinct while every comment stays attached to the deployed web app.

Receive page-specific feedback on the live result, then use Cursor Browser and code tools to reproduce and implement the change.
See how
Share the client-facing deployment and keep Cursor team membership, repositories and agent runs inside the delivery team.
See how
Review responsive screens and live flows with reproducible browser context, then retest after the deployment updates.
See howRoute an actionable website comment to the development team with its deployment URL, selected location, screenshot, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the deployed app beside product PDFs, videos, images, presentations and other launch assets, with feedback and approval in one project.

product-launch.mp4
Up to 40% offThis 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.

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.

Send the browser-accessible deployment URL for the frontend. Cursor documents a Cloud Agent publishing flow that deploys the repository through Vercel and returns that URL.
Paste the browser-accessible deployment URL and send a focused review link without exposing the editor, repository or Cloud Agent run.
