Install it.
Just once.
Add the component to your Next.js layout, a validation route, and a server-side secret. You’re ready.
For the developer YOUR SITE. YOUR AGENT. FINALLY CONNECTED.
The bug is here.
Show it to
your agent.
One link to open your site. One pen to show what’s wrong. All the context your agent needs to figure it out.
No browser extension. Works in production, too.
FEEDBACK, IN CONTEXT INTERACTIVE DEMO
studio/Collection About Cart (1)
OBJECT Nº 014
A LITTLE LIGHTThe Sunday
The Sunday
lamp.
Brushed aluminum. Bright ideas.
€129.00 × 1
Total€129.00
↖You1
This button does nothing…I can’t complete my purchase.
▂▅▃▇▅▂READY FOR YOUR AGENT
↗The issue, the screenshot, and everything behind it.
Built to work with
Claude Code◉ Codex>_ Your favorite agent
All your agent needs is a terminal.LESS BACK-AND-FORTH. MORE FIXES.
From “it’s broken”
to “I see why.”
You show the problem.
Your agent gets the context.
You move forward together.
Install it.
Your agent
creates a link.
Ask for a link to the page you want to test. Your agent adds the recipient, version, or ticket. You share it.
One link, one sessionShow what’s
not working.
Open the link, circle something, type, or speak. Browse your site and collect your feedback in one report.
For everyoneLet your agent
investigate.
Send the report. Allow browser control so your agent can inspect, click, and reproduce the bug to fix your code.
With your permissionCONTEXT MAKES ALL THE DIFFERENCE.
One red circle.
The whole story
behind it.
Skip the “which page?”, “what screen size?”, and “can you open the console?” Your feedback comes with the clues that matter.
Give my agent the context ↗ checkout-feedbackREPORT #014
The problem, exactly as you see it
A page capture, drawings, notes, and voice recordings.
The technical clues
Console output, JavaScript errors, and network requests captured after activation.
The right context
URL, viewport size, DOM details, and metadata from the link.
SMALL COMPONENT. BIG DIFFERENCE.
Your next bug fix
starts with a link.
Next.js App Router or Pages Router.
A secret that stays on the server.
A quiet tool, activated on demand.
Terminal
↳
Early release. Version 0.0.2 is now available on npm. View on npm ↗
YOU STAY IN CONTROL.
It can click.
Because you said yes.
The report is enough to get started. If your agent needs to dig deeper, allow read-only access or browser control. It can inspect the page, take screenshots, click, and fill allowed fields. You can turn access off.
✓ Inactive without a valid link✓ Live control is off by default✓ Time-limited sessions
A FEW GOOD QUESTIONS.
Before you
draw that circle.
Does it work on my production site? +
Yes. Install the package and configure your secret on your Next.js server. Only a valid signed link activates the widget in the recipient’s tab. It does not replace your site’s authentication.
Does my user need to install anything? +
No. They open your link and the widget appears on your site. They can draw, type, and record a voice note after granting microphone permission.
How does my agent get the feedback? +
Your agent keeps the report link when it creates the invitation. Once the user sends the report, the CLI downloads screenshots, notes, and logs. With permission and the tab open, your agent can also interact with the page live.
Can I use it with Claude or ChatGPT? +
Any agent that can run the CLI can use it, including Claude Code and Codex. A chat without terminal access cannot control the browser through the CLI.
What gets collected? +
Annotated page captures, your notes, errors, and fetch/XHR activity after activation. No cookies, headers, or request bodies are collected. Captures use DOM rendering, so videos and some external content may be missing. Review your report before sharing.
Less explaining.
More bugs fixed.
Install Tiny Feedback ↗A tiny tool for better work together.