Shannon: Trusting the Signal, Not the Substring
Two pull requests landed today, one hardening how the pentest engine classifies errors and expands model support to MiniMax, both centered on a shared lesson: don't let pattern-matching override explicit signals.
Duration: PT2M12S
Episode overview
This episode is a short developer briefing from Shannon.
It explains recent repository work in plain language.
- Show: Shannon
- Published: 2026-07-30T06:03:42Z
- Audio duration: PT2M12S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
You're listening to Shannon, your developer briefing for July 30th, 2026.
Today's activity is light on volume but heavy on precision — both changes are about trusting explicit signals over guesswork.
The headline is PR 401, a fix to how the system classifies errors for retry logic. Previously, message substring matching could override a Pentest Error's own explicit retryable flag — meaning queue-validation failures that were intentionally retryable could get flipped to non-retryable, and unrecoverable config…
The second theme is expansion, not correction. PR 400, from octo-patch, adds first-class support for MiniMax's M3 and M2-point-7 models through Anthropic-compatible endpoints. Before this, pointing the custom base URL setting at a MiniMax endpoint would fail with a "model not found" error, because the system always…
What ties these together: both PRs are about the system correctly recognizing what it's actually being told, whether that's an error flag or a model identifier, rather than falling back on assumptions.
What's next — worth watching whether the retry classification fix surfaces any previously-masked failures in production pentest runs, since jobs that were silently…