Flake Hunter is a free prompt. Paste a test that passes locally but fails in CI one run in five, plus the failure log. Get the likely causes ranked and a real fix, not another retry.
It is not always the right tool. Here is when something else wins, and when it does not.
Dedicated tool
CI flaky-test detection (BuildPulse, Trunk)
Pick it if
You need to find which tests are flaky across hundreds of runs.
Pick Flake Hunter if
You already know the flaky test and need the cause and a fix.
0:00The evidenceSupport ticket prompt. Wanted JSON for the on-call engineer. Got four friendly paragraphs and no severity.
0:08Bug 1: rules that fight'Be concise' vs 'cover everything the customer said'. The model picks 'everything' and writes four paragraphs.
0:16Bug 2 and 3'Always be friendly!!' outranks the format, so it writes to the customer. 'Output JSON' has no schema and no example.
0:24Fixed promptReader named, friendliness rule cut, JSON schema with one filled example, and a 'no prose outside the JSON' line. Each change tied to a bug.
No daily video for this drop yet. The in and out lines above are the preview.
0:00The callPOST /api/refunds returned 401 bad signature twice. The body says the prefix should be sha256=. They may have signed with the example placeholder.
0:08What brokeThe server rejected the signature. The status is not a transient outage. The prefix note is a hint about the header format.
0:16The changeSign the raw body with the real secret, prefix the header with sha256=, and keep the same idempotency key so a later success does not double-apply.
0:24RetryDo not retry the same bytes. Retry once after the header changes. Forging a signature for someone else's API is out of scope.
No daily video for this drop yet. The in and out lines above are the preview.
0:00Done vs stuckInstall and help worked on ledger 1.4.0. Step 3 points at a dashboard they do not have. Step 4 returns 401 bad signature.
0:08The gapThe tutorial never says the secret in .env must be the same bytes the signature is computed over, or what header the local tool expects.
0:16The lessonPut the placeholder secret in the env name the help text would show, restart the command, and compare the 401. No repeat of npm install.
0:24StopIf it still 401s, the next paste is the header name from --help, not another install step.
No daily video for this drop yet. The in and out lines above are the preview.
Questions
What are the alternatives to Flake Hunter?
CI flaky-test detection (BuildPulse, Trunk) (dedicated tool); Re-running until green (by hand). On One Agent a Day, Test Plan from the Prompt, Prompt Debugger, API Error Explainer, Tutorial Gap Finder do a similar job.
When is CI flaky-test detection (BuildPulse, Trunk) better than Flake Hunter?
CI flaky-test detection (BuildPulse, Trunk) is the better pick when you need to find which tests are flaky across hundreds of runs. Flake Hunter is the better pick when you already know the flaky test and need the cause and a fix.
When is re-running until green better than Flake Hunter?
Re-running until green is the better pick when you are shipping a hotfix right now. Flake Hunter is the better pick when it has happened three times this week.
Tomorrow's drop
Get tomorrow's agent in your inbox
One email when the drop goes up. No digest, no course. Unsubscribe from the beehiiv email whenever you want.
Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.