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.
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 🙏
Report
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.
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.
@a_kuzov Hey! Just wanted to let you know we shipped an update based on your feedback.
Nix Capture now detects sensitive headers (like Authorization, cookies, and API keys) when exporting requests or copying a cURL, and lets the user choose whether to include them or remove them before sharing.
Really appreciate you raising that — it directly helped improve the product.
Report
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
@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.
Report
@victor_alves5 That makes sense. Giving teams visibility and control over what they share is important, especially when tokens are involved. Masking and redaction options would definitely make this more enterprise friendly over time.
Appreciate the transparency 🙌
@md_murtuza_ali Hey! Just wanted to let you know we shipped an update based on your feedback.
Nix Capture now detects sensitive headers (like Authorization, cookies, and API keys) when exporting requests or copying a cURL, and lets the user choose whether to include them or remove them before sharing.
Really appreciate you raising that — it directly helped improve the product.
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 data
remove sensitive data before sharing
This was one of the most valuable discussions from this launch — really appreciate everyone who pointed it out 🙌
Nix Capture
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
@a_kuzov Hey! Just wanted to let you know we shipped an update based on your feedback.
Nix Capture now detects sensitive headers (like Authorization, cookies, and API keys) when exporting requests or copying a cURL, and lets the user choose whether to include them or remove them before sharing.
Really appreciate you raising that — it directly helped improve the product.
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.
Nix Capture
@md_murtuza_ali Hey! Just wanted to let you know we shipped an update based on your feedback.
Nix Capture now detects sensitive headers (like Authorization, cookies, and API keys) when exporting requests or copying a cURL, and lets the user choose whether to include them or remove them before sharing.
Really appreciate you raising that — it directly helped improve the product.
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 data
remove sensitive data before sharing
This was one of the most valuable discussions from this launch — really appreciate everyone who pointed it out 🙌
Nix Capture
Quick update — I’ve just added an English version of the demo video to make it easier for everyone to follow along.