Launching today
Nix Capture
Capture API requests for bug reports in seconds
51 followers
Capture API requests for bug reports in seconds
51 followers
Bug reports often arrive without request context — no endpoint, no status code, just “it’s not working.” Nix Capture lets you record network requests while reproducing an issue and export everything engineers need in seconds. No DevTools. No technical knowledge required. Built for QA, support, and product teams who want actionable bug reports.
Nix Capture
Congrats on the launch, Victor! As a fellow Chrome extension builder, I really appreciate how you've identified such a specific pain point. The "it's not working" bug report with zero context is something every dev has dealt with, and the idea of bridging that gap for non-technical team members is smart positioning. Making network request capture accessible without DevTools is a great angle — it removes the friction that stops QA and support teams from providing useful data. Curious about your approach to the Chrome extension review process — did you run into any challenges with permissions for intercepting network requests? That's always been a tricky area for extensions in this space.
Nix Capture
@roman_builder Thanks a lot — really appreciate that!
And yes, permissions were definitely one of the trickiest parts.
Since the whole idea is to make request capture accessible without DevTools, I had to be very careful about requesting only what’s strictly necessary and clearly communicating the purpose during the review.
Nix Capture
@roman_builder Feel free to share your extension with me, I’d love to check it out.
And yeah, the Chrome Web Store approval process is pretty strict — I’m going through that pain as well
Nix Capture
@md_murtuza_ali Great question — and yes, sensitive data is something I’m actively thinking about.
Right now, the extension allows capturing headers like tokens when needed for debugging, since in many real-world cases they are essential to reproduce issues.
That said, this is also why the focus is on making the data visible and understandable — so teams can decide what to share safely when creating reports.
Improving masking and redaction options is something I’m considering as the product evolves.
This hits a real nerve. I've lost count of how many bug reports I've gotten that just say "it doesn't work" with a screenshot of a blank page. Having non-technical team members capture actual request context without opening DevTools is a smart approach.
Question: do you plan to support auto-redaction of auth tokens/sensitive headers before export? That would make it much easier for support teams to share captures without worrying about leaking credentials.
Nice launch, congrats!
Nix Capture
@a_kuzov Appreciate the question!
Yes — auto-redaction is something I’m actively considering.
The goal is to make sharing captures safer for support teams without adding friction to the debugging process, especially when sensitive headers like auth tokens are involved.
Nix Capture
Quick update — I’ve just added an English version of the demo video to make it easier for everyone to follow along.