Nix Capture

Quick update: based on the feedback here, we just shipped a new safety layer in Nix Capture.When exporting requests or copying a cURL, the extension now detects sensitive headers (like Authorization, cookies, and API keys) and lets you choose whether to:include sensitive dataremove sensitive data before sharingThis was one of the most valuable discussions from this launch — really appreciate everyone who pointed it out 🙌

How does Nix Capture handle auth tokens and PII in captured requests? That's the blocker with most network recording workflows. Non-technical teammates capturing API context instead of just saying it broke fixes the biggest debugging bottleneck. The export format matters a lot here... if requests land as structured data that maps to issue tracker fields, engineers skip the manual repro step entirely. Auto-tagging failed responses or letting reporters mark the exact moment things broke would make captures immediately actionable.

Quick update — I’ve just added an English version of the demo video to make it easier for everyone to follow along.

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!

This is actually a good idea. Bug reports without context are the worst. Making it easy for QA or support to capture network requests without DevTools makes a lot of sense.
Curious how you handle sensitive data in the requests though? Nice work

Hey everyone 👋

I built Nix Capture after seeing the same problem over and over again:
bug reports arriving with screenshots… but no request context.

No endpoint.
No status code.
No response details.

Just “it’s not working.”

So I built a simple Chrome extension that lets you record network requests while reproducing an issue and export them in seconds — without opening DevTools.

The goal isn’t to replace DevTools.
It’s to make technical context accessible to QA, support, and product teams.

Right now, it’s focused on simple request capture.
Next steps may include structured ticket exports, smart filtering, and human-readable explanations.

I’d love honest feedback:

– Who do you think this is most useful for?
– What would stop you from using it?
– What would make this a no-brainer for your team?

Thanks for checking it out 🙏