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 Replit. 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 Replit integration: BugSmash reviews the resulting browser page and does not connect to Replit itself. Review the published or deployed web output from this tool. The editor, private project workspace and native mobile app are separate from a publicly accessible browser page. https://your-app.replit.app Platform clarification: this is a generic BugSmash Website project workflow, not a native Replit integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your published Replit app
Paste the stable production URL, send one review link, and collect comments on the app your users will actually open. Every note stays attached to the page, browser, device and screenshot.
Loved by1,250+Agenciesand companies in 100+ countries
Replit can collect feedback. Client review often needs a wider workflow.
Replit has a native Feedback Widget for published web apps. Visitors can select elements, add text, screenshots and files, and the feedback lands in the Project Editor Inbox for Agent.
That is useful inside a Replit build. Four boundaries still matter:
01
The native widget requires reviewers to sign in.
Replit documents sign-in as part of submitting feedback. A BugSmash review link can be opened without a Replit seat or BugSmash account.
02
Feedback stays in the Replit Project Editor.
Native submissions are managed in the Inbox and can be sent to Agent. Client approvals, agency handoff and work tracked in Jira, ClickUp or Slack often need a record outside the build project.
03
A Development URL is temporary.
A .replit.dev URL is live only while you actively work on the app and can change when the app is reopened. Replit recommends publishing the app when you need a stable link to share.
04
The native Feedback Widget is for web apps only.
Replit does not offer that widget for other app types. A launch can also include PDFs, videos, images and presentations that need the same review record.
BugSmash complements the Replit workflow:
review the production release in a browser, keep approvals outside the build workspace, and route each item into the task tools your team already uses.
How it works
Three steps to a reviewed Replit app
11
Publish a production release
Use the generated .replit.app address or a connected custom domain. Replit keeps the editable project separate from the production deployment, so later edits do not change the live release until you republish.
22
Send one review link
Paste the published URL into BugSmash and send the resulting link to the client or QA team. They review the live app in their browser without project access.
33
Turn comments into tasks
Each comment includes the page, selected element, browser, device and screenshot. Assign it, set status, or send it to Jira, ClickUp, Monday, Asana, Trello or Slack.
Review the Replit app your users will actually open
Comment on the production release
Review the stable .replit.app URL or custom domain instead of relying on a temporary Development URL.
Check every responsive layout
Review desktop, tablet and mobile states from the same link and keep each comment tied to the viewport where it appeared.
Capture browser and device automatically
Every report carries the environment needed to reproduce a layout or interaction issue.
Keep feedback tied to a release
Replit keeps the editable project separate from production. BugSmash keeps each review round and approval attached to the release the client saw.
Review real app states
Use a test account for an ordinary username-and-password flow so feedback lands on the actual screen and data state.
Move work beyond the Project Editor
Turn client comments into assigned tasks in the delivery tools used by the wider team.
Will it work on my Replit app?
Use the production URL whenever possible. Replit documents published apps as stable, shareable deployments and Development URLs as temporary testing links.
Your URL
Review by URL
What to do
Public app on a .replit.app domain
Works
Paste the production URL and start the review.
Public app on a custom domain
Works
Paste the custom domain after Replit shows it as verified.
Password-protected published app
Works
Open the shared password gate inside the review window, enter the password, and continue.
Public .replit.dev Development URL
Temporary
It can work while the app is active, but the URL may change. Publish the app for a stable client-review link.
Workspace-only or invite-only deployment
Access-dependent
These modes require authorized Replit access. For external review, use public or password-protected access, or install the BugSmash Feedback Widget.
App login using a username and password form
Works
Sign in to a test account inside the review window. Social and SSO-only login flows need the BugSmash Feedback Widget.
Using the BugSmash Feedback Widget on a Replit app
Add the BugSmash script to the web app when reviewers must stay inside a stateful flow or an authentication path that the URL review cannot reproduce. This is separate from Replit's own Feedback Widget, which sends signed-in visitor feedback to the Replit Inbox and Agent.
The feedback workflow for teams using Replit
From preview reviews to production QA, keep founders, agencies and product teams aligned on the exact Replit app release being reviewed.
Turn Replit app feedback into work without retyping it
A comment on the published app becomes a task with the URL, selected element, screenshot, browser and device context already attached.
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 Replit app is one deliverable. Review the rest of the launch with it.
Keep the published app, pitch deck, product PDF, demo video, screenshots, launch email and mobile companion in one review project with one approval trail.
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.
Should I use my .replit.dev URL or publish the app first?
Publish first for a client review. Replit says Development URLs are temporary, are live only while you actively work on the app, and can change when the app is reopened. A production deployment gets a stable, shareable URL.
Does BugSmash work with a .replit.app URL?
Yes. Paste the public production URL and send the generated review link.
Can I use a Replit custom domain?
Yes. Replit routes the verified custom domain to the same published deployment and provides HTTPS automatically.
What if the published app is password protected?
Replit supports a shared-password access mode. Enter that password in the review window when the gate appears. Workspace-only and invite-only deployments still depend on the reviewer's authorized Replit access.
How is this different from Replit's Feedback Widget?
Replit's Feedback Widget is a native option for published web apps: signed-in visitors can submit text, select elements and attach screenshots or files, and the results go to the Project Editor Inbox or Agent. BugSmash keeps the review and approval record outside the build project, supports the rest of the campaign deliverables, and routes comments into external task tools.
Do reviewers need access to my Replit project?
No for a public or password-protected published app. They review the production URL, not the editable Project Editor.
Will my latest Project Editor changes appear automatically?
No. Replit keeps the editable project and production deployment separate. Test the change in Preview, republish it, and the same production URL will serve the new release.
Can I review a login-protected app?
A normal username-and-password form can be completed inside the review window with a test account. If the flow depends on social sign-in, SSO or a long-lived stateful session, use the BugSmash Feedback Widget.
Ship Replit apps without chasing feedback
Paste your published Replit URL and send the first review link in under a minute.
BugSmash complements the Replit workflow:
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