In-app bug reporting for teams that ship fast. Drop in one line of code and every report arrives with screenshots, console errors, network requests, and the user's last clicks captured automatically. Simple enough for anyone to report, complete enough for a developer (or your AI) to fix. One click turns any bug into a prompt for Cursor or Claude, or connect the MCP server and let your AI triage them. Flat pricing, no per-seat fees, no session replay. Free to start.
No reviews yetBe the first to leave a review for Miniback
Maker
📌
Hey PH 👋 i am the founder of Miniback.
!!! Contact support@miniback.io for Free trials !!!
Honestly I built Miniback because I was sick of one thing. Someone would message me "hey, it's not working" and that was it. That was the whole bug report. So I'd write back asking what page they were on, what browser, what they clicked, and half the time they'd never reply, or they'd send a screenshot of the wrong screen. Days would go by on a bug that took me ten minutes once I could actually see it.
So I made a little button you drop on your site with one line of code. When someone reports something, it quietly grabs the stuff I always ended up asking for anyway. The page, their browser and device, the console errors, the network request that failed, and the last few things they clicked before it broke.
The bit I personally use the most is a "copy as AI prompt" button. It bundles the whole report up so I can drop it straight into Cursor or Claude and get moving. And if you don't even want to copy-paste, there's an MCP server now, so your AI assistant can just pull the bugs and triage them for you.
It's flat pricing, no per-seat nonsense, and it starts free (1 project, 100 bug reports a month).
Since we just launched I'm looking after early adopters properly, so if you want to try it before committing to anything, DM me and I'll sort you out with a free trial.
Anyway, I'd love for you to break it and tell me what's rubbish about it. And out of curiosity, what's the worst bug report you've ever gotten?
Be sure to reach out for a 100% free trial!
!!! Contact support@miniback.io for Free trials !!!
worst one I ever got was 'it's broken, fix pls' with no screenshot and no page mentioned, had to guess which of our ten flows they even meant. so yeah, this would've saved me an afternoon or two. quick question on the auto-capture: does the last-clicks trail ever pick up text typed into a password or card field, or is that filtered out before it leaves the browser?
Report
Maker
@galdayan hey Gal! the answer is genuinely yes. masking runs at capture time, client-side, the raw value is never transmitted
@nikos_spiropoulos good to hear, that's the right default. one more angle on the same capture path - the network requests you log, do those ever include full response bodies (auth tokens, API keys in headers)? password fields being masked is the obvious case, but a failed request dumping a bearer token into a bug report is the kind of leak that's easy to miss because it doesn't look like a form field at all.
Report
Maker
@galdayan good eye, that's exactly the kind of thing that bites people. headers are covered both ways (request and response) , auth, cookies, api-key, etc get stripped by name before anything's sent. json bodies too, we redact known sensitive keys recursively
@nikos_spiropoulos recursive redaction on json bodies is the right call, most tools stop at the top-level keys and miss nested tokens. that covers the gaps I'd have worried about, good luck with the launch.
This solves a real pain — bug reports with screenshots, console errors, and last clicks auto-captured is exactly what devs need. One line of code too. Congrats on the launch!
Report
Maker
@zvonimir_sabljic1 thanks a lot! looking forward to getting some bugs resolved through miniback !
Dial
worst one I ever got was 'it's broken, fix pls' with no screenshot and no page mentioned, had to guess which of our ten flows they even meant. so yeah, this would've saved me an afternoon or two. quick question on the auto-capture: does the last-clicks trail ever pick up text typed into a password or card field, or is that filtered out before it leaves the browser?
@galdayan hey Gal! the answer is genuinely yes. masking runs at capture time, client-side, the raw value is never transmitted
Dial
@nikos_spiropoulos good to hear, that's the right default. one more angle on the same capture path - the network requests you log, do those ever include full response bodies (auth tokens, API keys in headers)? password fields being masked is the obvious case, but a failed request dumping a bearer token into a bug report is the kind of leak that's easy to miss because it doesn't look like a form field at all.
@galdayan good eye, that's exactly the kind of thing that bites people. headers are covered both ways (request and response) , auth, cookies, api-key, etc get stripped by name before anything's sent. json bodies too, we redact known sensitive keys recursively
Dial
@nikos_spiropoulos recursive redaction on json bodies is the right call, most tools stop at the top-level keys and miss nested tokens. that covers the gaps I'd have worried about, good luck with the launch.
Pazi
This solves a real pain — bug reports with screenshots, console errors, and last clicks auto-captured is exactly what devs need. One line of code too. Congrats on the launch!
@zvonimir_sabljic1 thanks a lot! looking forward to getting some bugs resolved through miniback !