Every developer who has shipped a product knows the moment: a teammate sends a screenshot in Slack annotated with a red arrow, a voice memo where someone says 'the button looks off', or a Loom recording that takes twelve minutes to communicate a two-second visual glitch. The information is there, but it is buried, lossy, and impossible to hand directly to a tool that can act on it.
We built LoopBack because we kept running into this exact problem ourselves. We were building a product, reviewing it on localhost, and finding dozens of small UI issues per session. Logging each one felt like busywork. Pasting a raw screenshot into Claude Code helped, but we had to repeatedly explain which element we meant, what the viewport looked like, and what the surrounding DOM context was. The AI was smart, but we were giving it dumb inputs.
The core insight that led to LoopBack is simple: a bug report is most useful when it carries the same information a browser developer tools panel would show you. The CSS selector of the target element, a screenshot of the viewport at the moment of capture, the page URL, the screen dimensions. All of that data exists in the browser at the moment you notice the bug. The problem is nothing captures it for you.
So we built a Chrome extension that sits quietly on localhost, lets you click anywhere on your UI to drop a comment, and automatically bundles the selector, screenshot, URL, and viewport into a structured object. You keep adding comments until your list is complete. Then you press one button and get a single prompt you can paste into any AI coding agent.
The early prototype was rough but the workflow felt immediately right. We stopped writing bug tickets. We stopped recording Looms. We stopped narrating screenshots. Instead we spent five minutes annotating a build, exported the prompt, and watched Claude Code work through the list systematically. Fix rates went up because the context was complete. Iteration cycles shortened because we could retest each item and mark it resolved without leaving the extension.
LoopBack is not a replacement for your AI agent. It is the layer between your eyes and your agent's input. It structures the visual information that already exists on your screen so your agent can act on it precisely. That is the job it does, and the only job it tries to do.