Last month's update introduced FeedbackDots. This one is about everything that happened since, and it was a busy few weeks. The short version: reports now reach more of the tools your team already uses, AI coding agents can work on them directly, and the widget collects more than bug reports.
Reports go where your team works
FeedbackDots already sent reports to Linear and Slack. Now there's more:
- Connect your own Linear workspace. Owners and admins connect Linear from a project's Capture settings in one click, then pick a team and an optional project.
- GitHub Issues. Install the FeedbackDots app on the repositories you want and every new report becomes an issue with the page, severity and a link back. The app only asks for access to issues, not your code.
- Jira Cloud. Pick a Jira project and every new report becomes a Jira issue, filed as a Bug when the project has that type.
- Status sync. Close an issue in Linear or GitHub and its report moves to Done in FeedbackDots. Reopen it and the report moves back. It works the other way too.
- Webhooks. Send new reports, status changes and comments to any HTTPS endpoint, including Zapier, Make and n8n. Every request is signed.
Closing the loop with people
Two features came straight out of a post I wrote last month about closing the feedback loop:
- Comments and @mentions. Discuss a report on its page and bring teammates in with @. They get an email and a notification.
- Tell reporters when it's fixed. Turn on reporter updates and anyone who left an email gets one short note when their report moves to Done, whether you closed it in FeedbackDots, Linear or GitHub.
Built for AI coding agents
This is the part I'm most excited about. FeedbackDots now has a public REST API, JavaScript and Python SDKs, and an MCP server. Connect Claude Code, Cursor or VS Code, and your agent can read a report with its screenshot, pins and console errors, fix the bug, then mark it done and comment on what changed.
The API and MCP server are on every plan. Starter includes 1,000 requests a month and Pro includes 50,000.
There's also opt-in network capture. Turn it on and every report shows the last 50 requests the page made, with failed calls highlighted. It never records headers, cookies or request bodies, and token-like parts of URLs are redacted before anything is saved.
Feedback beyond bugs
The widget can now ask for more than bug reports:
- NPS surveys. Ask visitors how likely they are to recommend you, and see your score and every answer on the Product feedback page.
- Feature requests and votes. Visitors suggest ideas and vote on the ones you've reviewed, right from the widget.
- Guest review links. Send a client a link that opens your site with the widget ready, no account needed. You can show the widget only to people with a link.
- Client portal. A read-only board that shows clients what they reported, where each fix stands, and your public roadmap.
On Pro, your For You story now opens with the past week of product feedback: which ideas got upvoted, how many are waiting for review, and your latest NPS.
Plans and polish
- The paid plan is now called Pro, and plans have their own pricing page. Getting started is two steps: add the snippet, then approve your domain.
- Your dashboard opens on what changed since your last visit.
- The app follows your system's light or dark setting, or you can pick one under Account settings.
- New install guides for apps built with Lovable, Bolt, v0, Replit and Cursor.
- New pages compare FeedbackDots with BugHerd, Marker.io, Usersnap, Userback and Jam, with starting prices side by side.
What's next
One item on the roadmap is letting the widget recognize signed-in users on your site, so reports arrive with the reporter's name and account attached. You can always see every change as it ships on the changelog.
If something here is useful to you, or something you need is missing, tell me. I read every message.