Let your AI agent work through your feedback

From “it’s broken” to fixed, without the copy-paste

No pasting screenshots into a chat window. No re-typing which browser it happened on.

Skip the “which browser?” email

Your agent sees what the reporter saw: the screenshot, the page, their browser and screen size. It also reads the console errors they never saw. Nobody has to go back to the client with questions.

Know what to fix next

Ask what’s urgent on a project and get a short list back, right in your editor. No switching tabs, no scrolling through the board.

Don’t fix the same bug twice

Before it touches the code, your agent checks whether someone already reported it. Five clients hitting one broken button means one fix, not five.

Your team knows what changed

Your agent leaves a note on the report explaining the fix, so whoever picks it up next isn’t starting from zero. The client never sees it.

A board that keeps itself up to date

Your agent assigns reports, moves them to In progress and sets priorities as it works. The board stays current without anyone doing admin.

Hear what users are asking for

Suggestions and ratings come through too. Ask for a summary of last month’s feedback and walk into planning with the top requests.

Put your bug reports to work

Three prompts to steal on your first day connected.

Prepare for a client call

“Summarize this week’s feedback on the Acme site and group it by page. Flag anything that’s a change request, not a bug.”

Investigate a bug

“Read the checkout report from yesterday and find the likely cause in this repo.”

Sort the new pile

“Review the reports since Friday. Suggest priorities, owners and likely duplicates, then apply the changes I approve with an internal note on each.”

Twelve tools, one endpoint

Your assistant finds all of them the moment it connects, and picks the right one on its own. You never type a tool name.

• list_projects

  Every project you can reach in the team you connected.

• get_project

  A project’s statuses, priorities and types, so your own names work in a prompt.

• list_tags

  The team’s tags. They’re shared across every project.

• list_project_members

  Who on a project can take a report. Names and roles, never emails.

• list_feedback

  Find reports by status, priority, type, tag, assignee, date or text.

• get_feedback

  One report in full, with the page, the browser and a screenshot link.

• get_feedback_console_logs

  The reporter’s browser console: errors, warnings and stack traces.

• get_feedback_network_requests

  The fetch and XHR calls the page made, with status and timing. Never the bodies.

• list_comments

  The thread on a report. Author emails are never included.

• update_feedback Write

  Set status, priority, type and assignee. Add or remove tags.

• add_comment Write

  Leave an internal note on a report for the team.

• create_tag Write

  Add a tag to the team, without duplicating one you already have.

The nine read tools work on BASIC. The three that change a report need STARTUP or COMPANY, and so does recording network requests. Arguments and examples →