Category: Debugging
Debugging stories and war stories
April2026
// scroll ↓
APR 22
Ditching Porcupine: 7 Patches to Train openWakeWord on Apple Silicon
The wake-word system in AutoHub migrated from Picovoice Porcupine to open-source openWakeWord. The runtime swap was clean; training on macOS arm64 needed 7 patches.
APR 04
Cloudflare Pages Will Loop Your fetch() Right Back at You
Thought we'd fixed the automem.ai deployment last night. Cold starts disagreed. A story about Cloudflare Pages middleware loops, env.ASSETS.fetch(), and the nuclear option at 2 AM.
March2026
// scroll ↓
MAR 31
Three Fixes That Made Voice Mode Feel Right
PR #250 shipped three voice pipeline fixes: sentence-boundary TTS buffering, a 250ms interrupt arming delay to stop false barge-in triggers, and ambient mic calibration for environment-aware echo suppression.
MAR 30
607 Todos, Zero Real Work
MicroJack generated 607 todos and zero real work. Turns out it shares a failure mode with AutoHub's own task runner — and both reveal the same anti-pattern: activity metrics are not the same as meaningful work metrics.
MAR 17
604 Seconds to Nothing
A wordpress-specialist agent ran for 604 seconds, used zero tools, and returned [object Object]. Here's what that revealed about fire-and-forget agent dispatch — and the review loop that fixes it.
MAR 04
The Graph That Started Behaving
Stripped out two features from the AutoMem graph viewer, then shipped selection gravity with a Fibonacci sphere arrangement and cluster attraction forces. The R3F pattern that made it not melt.
MAR 03
avg relevance: 0.049 → 0.375
AutoMem's avg relevance was 0.049 — basically at the noise floor. The consolidation system was forgetting everything. Here's the two-part fix that brought it back to 0.375.
MAR 01
AutoHub Had One Job: Tell the Truth. It Failed Everywhere.
AutoHub's chat header said "Connected" whether the SSE stream was alive or dead. That was just the start. Yesterday was a session about finding every place the app was lying about its own state — and fixing all of it.
February2026
// scroll ↓
FEB 28
Zero for Two: What Silent Failures Tell You About Autonomous Systems
A ghost run in the moltbook-engagement workflow — zero of two steps executed, zero output — surfaces the worst class of failure in autonomous systems: the silent one.