loupfeed anchors every piece of user feedback to the exact element it's about — with the last minute of session replay, the breadcrumb trail, and the precise line of source code. Then your agent pulls it through MCP, fixes it, replies to the user, and closes it. Without you leaving the editor.
Web + React Native · npm i @loupfeed/react · self-host on a $10 VPS, Docker, or your AWS
No forms, no screenshots over WhatsApp, no “can you send a video?”. The report carries everything the fix needs.
Users long-press any element in your live app — web or mobile — and type what's wrong. Right there, in context.
The last ~60s of session replay (masked by default), the click trail, page, app context, and the element's identity.
A build-time manifest maps the element to file:line — server-side, so your source paths never ship to the client.
Claude pulls the report through MCP, watches the session, patches the code, replies to the reporter, marks it resolved.
Every report is structured for a coding agent: what the user said, what they did (as a readable session timeline — not a video your agent can't watch), and where in the code it lives. Eight MCP tools close the loop end-to-end.
Numbered pins on the live UI, threads per element, in-app replies the reporter actually sees. Long-press or CTA to report.
Rolling last-minute buffer, uploaded only on report or crash. Masked by default — or readable with targeted PII redaction (emails, amounts).
Unhandled errors auto-captured with stack traces, breadcrumbs, and the session that led there. Web + React Native.
Opaque element ids resolve to file:line server-side. One click to VS Code or GitHub. Source paths never reach the client.
React, Vue, Svelte on web; React Native/Expo with a native inspector and privacy-safe wireframe replay.
Source-available (FSL). One Docker container, your AWS via CDK, or SQLite on a VPS. Named instance per product — or per client.
Everything on this page is in the open repo — SDKs, backend, dashboard, infra, this website. Run it on a $10 VPS with SQLite, or deploy the CDK stacks to your own AWS.
The product is free to self-host, forever. What I sell is my time and my infrastructure — and buying either directly funds the roadmap you're depending on.
I'm building loupfeed in the open from Cameroon 🇨🇲 — the whole stack is source-available, so you can read every line before you trust it with your users. If it ever stops being maintained, you self-host and lose nothing. That's the deal, and it's enforced by the license, not a promise.