Got Feedback?

Tell us how we could make the product more useful to you.

Localhost Tunneling Integration via SERVEO

Description: A Serveo integration would enable developers to share localhost demos directly through BugSmash without deploying to staging servers. Use Case: As a developer / vibecoder / web designer, it would be beneficial to share my local development environment for review so that I can get feedback faster without uploading/deploying first. How it works: Create project β†’ Select "Localhost" option BugSmash generates secure tunnel (via Serveo.net integration) Share BugSmash link with reviewers Reviewers access localhost through BugSmash's interface Time-limited access (auto-expires after review period) Benefits: Eliminates deployment bottleneck Faster iteration cycles No staging server costs Perfect for rapid prototyping Unique competitive advantage Technical: Serveo provides SSH/WireGuard tunneling without proprietary clients. BugSmash would manage tunnel lifecycle and integrate with existing access controls. Suggested Implementation: Start as opt-in beta feature for Pro users. Clear security warnings. Fallback to traditional upload method. Target Users: Solo developers, small agencies, teams doing rapid prototyping and internal QA. Contact information: 🌐 https://serveo.net πŸ‘€ Serveo founder: Trevor Dixon βœ‰οΈ trevordixon@gmail.com

FT 3 days ago

πŸ’‘

Feature Request

Planned

expose comment location data on the v2 REST API

Hi BugSmash team, We use the v2 API to automate processing of website review feedback (list comments, action the changes in code, post replies). It works well and v2 is a big improvement over v1. One gap is blocking us from fully automating website projects. The per-comment location data is not available on the REST API. Both GET /api/v2/comments?projectId=... and GET /api/v2/comment/{id} return the comment text, status, priority, screenshot URL and replies, but no information about which page or element the comment was pinned to. On website projects comment_by_name and any page reference come back null, so the API alone cannot tell us where a comment belongs. That same data does exist. Your new JSON export (Project > Export > JSON) includes a full location object per comment: "location": { "live_url": "https://example.com/for-professionals/#enquiry", "dom_selector": "main > section:nth-child(2) > ... > a:nth-child(1)", "dom_selector_fallback": "...", "closest_parent_selector": "...", "element_tag": "a", "element_text": "privacy policy", "pin": { "x": ..., "y": ... }, "element_bounding_box": { ... }, "viewport": { ... }, "device": { ... }, "browser": "Chrome", "platform": "Desktop" } With live_url, dom_selector and element_text on the API we could locate the exact element in source directly, with no manual export step. The export is great for a one-off batch, but it is a manual download and is not reachable with our API key, so it cannot drive an automated or scheduled workflow. What we would like: Add the location object to each comment in GET /api/v2/comments and GET /api/v2/comment/{id}, or Gate it behind a parameter such as ?include=location to avoid bloating the default response. Note: we tried ?include=location, ?expand=location and ?with=location on the comments endpoint already. They are accepted but ignored (the response is byte-for-byte identical), so there does not appear to be an existing flag for this. At minimum live_url, dom_selector and element_text would be enough for us, though the full object matching the export would be ideal. Additional improvements No way to mark a comment resolved via the API (the bigger one). PATCH /comment/{id} lists status as editable but only accepts an opaque internal UUID, so every value we can actually send gets rejected. Right now our reply is our own "done" marker, but the client still has to manually click Resolve in the dashboard to move it out of active. If they exposed a plain resolve/status endpoint, we could close the loop fully and stop depending on the client remembering to click. This is arguably more friction day-to-day than the location gap. Tags aren't on the API either (optional). The export has a tags field but GET /comments doesn't. Only worth asking for if you plan to actually use tags to flag "on-hold vs action now" β€” otherwise it's a speculative ask. Your call. Thank you. Chris

Chris 5 days ago

1
πŸ’‘

Feature Request

In Review

Automatically Save a Full Page Snapshot When Completing or Updating a Website Version

When a website project is updated, the new version is often first published on a temporary test domain. Once the website is transferred to the final domain, the temporary domain is usually no longer available. As a result, the previous website version can no longer be viewed inside the project. It would be very helpful if BugSmash could automatically create and save a full page snapshot when a version is completed, replaced or marked as complete. The snapshot should preserve the entire page as it appeared at that moment. This would allow users to review previous versions even when the original test domain has been removed, changed or is no longer accessible. Currently, I solve this by manually uploading a PDF of each website version. This allows me to document the different stages of the project, but it requires an additional manual step. An automatic snapshot feature would make the entire version history much easier to manage and would keep all previous website versions accessible directly inside BugSmash.

Elia Meierhofer 22 days ago

πŸ’‘

Feature Request