Chrome extension · private beta

Point at the bug.
Not at a paragraph
describing it.

Your team leaves comments straight on the page. Each one stays anchored to the element it points at, and carries the browser, the screen size and the exact selector with it.

Start a projectSee how it works

Three steps, then it is out of your way.

  1. 1

    Install the extension

    One extension for the whole team. It stays asleep until you open the toolbar, and touches nothing on the pages you browse.

  2. 2

    Click where the problem is

    Switch to comment mode and click. The pin lands on the element you clicked, not on a copy of the screen.

  3. 3

    Discuss it in place

    Replies live next to the pin. Resolve it when it ships, and the pin fades instead of disappearing from the count.

« It works on my machine » ends here.

A screenshot tells you what someone saw. It does not tell you where they were, on what, at which size — nor what the page threw at the same second. Every Fydbak comment carries that with it: the browser, the viewport, the console errors, the requests that failed.

And when the page changes underneath, the comment is not lost. If its element is gone, it is marked unplaced and stays in the list instead of vanishing.

Comment #46 min

Théo Vasseur

The header button is 34px tall. Tap targets need 44 minimum, it is hard to hit on a phone.

Element
main > section:nth-of-type(2) > a
Viewport
1440 × 900
Browser
Google Chrome
System
macOS

Feedback that knows what it is talking about.

Stop translating a screenshot into a sentence. Put the remark on the element and let the context follow.

Anchored to the element
A comment sticks to the element it points at, not to a screenshot. It survives scrolling, resizing and most redeploys — and when the element is gone, it is marked unplaced instead of vanishing.
The page speaks for itself
Console errors, failed requests and the last actions taken travel with every comment, captured at the moment of the click. No one has to reproduce anything.
Show it, then say it
A screenshot or a tab recording opens an editor first: circle it, point at it, mask what nobody needs to see. The first stroke is also where the pin lands.
Works on any site
Staging, production or a page you do not own. The extension draws an isolated layer that never inherits the host page styles.
Threads, not tickets
Reply where the problem is and resolve it when it ships. Invite the team with a project code — everyone sees the same pins on the same pages.
Readable by an agent
Each card carries the selector, the markup, the React component and its source file. An agent reads the queue over MCP, works, and opens a pull request. It proposes; it does not merge.

Questions

Does it change the sites I visit?
No. The interface is drawn in an isolated layer, so it never inherits the styles of the page and never alters them. The page you comment on is the page your visitors get.
What happens when the site changes?
Comments are anchored to an element, not to coordinates, so they follow it when the layout moves. If the element is gone for good, the comment is marked unplaced and stays readable in the panel.
Can I use it on a site I do not own?
Yes. Staging, production, a competitor, a client deployment you only have a link to. Anything you can open in Chrome.
Who can see the comments?
Only members of the project. People join with an invite code, and comments are scoped to the project they belong to.
Is it available on the Chrome Web Store?
Not yet. During the beta the extension is loaded unpacked from a build you get with your account.

Stop describing the bug. Point at it.

Create a project, invite your team with a code, and start leaving pins on the pages you are shipping.

Start a project

Free while in beta. The extension is loaded unpacked for now.