Your users report bugs. Your agent fixes them.
Drop in a widget, and the feedback your users send lands in a private queue your coding agent reads and resolves. No dashboard, no copy-paste.
npm i feedback-sdk-widget
<!-- one tag, anywhere in your markup --> <feedback-widget endpoint="https://your-service" token="fbk_public_..." ></feedback-widget>
# read the reports, newest first curl $SITE/feedback -H "Authorization: Bearer $ADMIN_KEY" # mark one handled curl -X POST $SITE/feedback/resolve \ -H "Authorization: Bearer $ADMIN_KEY" \ -d '{"id":"...","status":"done"}'
Right now, you're the middleman.
A bug gets reported somewhere you have to read, then retype for your agent. This cuts you out of the relay.
Three steps. Two lines of code.
Add one button
Drop the widget into your app. It stays in its own box, so it can't touch your styles.
Someone types what's wrong
A small panel in the corner. They pick idea, bug, or other, and send. It knows what page they were on.
Your agent reads it and fixes it
One request pulls the queue with a secret key. Tell your agent to work the top item.
Small, safe, and yours.
One custom element. No framework pulled in.
Renders in a shadow root. Your CSS and its CSS never collide.
A public key that can only write. A secret key that reads. Nothing else.
Read every line. Run it yourself. No account needed to start.
Add it to your app in two minutes.
Install the widget, point it at your service, and let your agent work the queue.
npm i feedback-sdk-widget