Launched this week
BugProof
Executable bugs, not bug reports
13 followers
Executable bugs, not bug reports
13 followers
BugProof captures software failures as portable, reproduciblebug artifacts. Instead of sharing screenshots, logs, and lengthy bug reports, developers can package the exact failure including source state, environment metadata, execution context, and failure fingerprints into a single file that anyone can replay. Cross-platform, open source, AI-agent ready, and no Docker required.
SuperBrain
mailX by mailwarm
How do you share and store them safely, like can you redact secrets before exporting the file?
SuperBrain
@othman_katim Yes. Before BugProof packages the `.bug` file, it automatically scans your computer's environment variables for anything that looks like a secret — API keys, tokens, passwords. It catches them two ways:
1. By name — if a variable is named `API_KEY`, `SECRET`, `PASSWORD`, etc., it's flagged.
2. By pattern — if a value looks random and high-entropy (like `sk-proj-AbCdEf...`), it's flagged.
When you share the `.bug` file, the secret values are stripped out. The person on the other end can see that a secret existed and what it was named, but never gets the actual value. Your credentials stay on your machine.
Congratulations on the launch. Every bug report I've ever come across has missing steps. Every single one. How do you handle the environment state piece — that's usually where reproduction breaks down even when the steps are right.
I can definitely relate to this. Sometimes an AI agent is doing useful work and you don't want to be stuck at your desk waiting for it to finish. Being able to check in from your phone feels like a natural next step.