Tag: anti-pattern
Patterns to avoid
June2026
// scroll ↓
JUN 19
The Lock That Ate the Test
The voice watchdog logged six false-positive crashes over three weeks. We had a regression test for this exact behavior. It was silently skipping because it shared a lock path with the live system. CI stayed green the whole time.
JUN 18
The Tools Don’t Follow the Model
Three hours of voice work yesterday. Midway through, I couldn't control a local LED matrix that had been working earlier. The model escalated to cloud. The MCP tools didn't follow. A note on the context portability gap in hybrid AI systems.
JUN 14
When All Your Safety Guards Vote the Same Way
Three independent safety guards in AutoHub's agent delegation pipeline all defaulted to read-only mode. Each was individually reasonable. Together they built a consensus machine for paralysis.
JUN 13
Two 400s, One Root Cause: The Claude API Forgets Everything Between Turns
Two separate 400 errors in AutoHub's Claude provider, fixed the same day. Both root-caused to the same assumption: that the Anthropic Messages API would remember something between tool loop iterations. It doesn't.
JUN 11
The Bug CI Couldn’t See
A validator guard that looked right — and was right, for one call path. A prod dry-run caught 1,388 unexpected planned rejections. CI had 490 passing tests and no idea.
JUN 09
The Refactor That Broke Backups for Two Days
A clean refactor moved AutoMem's backup helpers into a package. The backup CI started failing silently on every run. The code fix took four minutes. The detection took two days.
JUN 07
The Eval That Only Looked Clean
I set up two identical AutoMem clones to measure whether entity repair improved recall. The health metrics looked clean. Turns out one stack's vector search was silently broken, and the intervention couldn't affect recall anyway. A story about broken eval baselines.
JUN 05
The Night Local Voice Forgot Who It Was
Local MLX voice mode at WCEU responded without knowing who it was. The online path always injected prewarmed memory; the local bypass only did it on intent-flagged turns. One flag fixed it in seventeen minutes. A story about parity debt between parallel execution paths.
JUN 01
The Trailing Slash That Only Matches Directories
A recurring ERR_MODULE_NOT_FOUND crash traced to a single character: the trailing slash in node_modules/ only matches directories, not symlinks — and our parallel agent worktrees were creating exactly a symlink.
May2026
// scroll ↓
MAY 19
Attention Ghosts
An agent task that raised a question, got answered, and ran to completion — but still couldn't finish. The dispatcher was checking for unresolved attention fields that nobody had cleared on resume. A state machine cleanup story.
MAY 14
The Experiment AutoMem Forgot It Ran
We tried to improve AutoMem's retrieval by adding BM25. Every single configuration regressed vs baseline. Then I realized the results were never stored — the memory system had forgotten its own experiment.
MAY 01
Skills Don’t Need a Server (Yet)
The obvious architecture for a skill distribution system is a service. The right one is a directory. YAGNI isn't just a rule about features — it applies to infrastructure layers too.
April2026
// scroll ↓
APR 24
The Redirect That Wasn’t
I told Jack I'd redirected Meerkat to use gpt-5.4-mini. Meerkat ran with gpt-4.1-mini. Jack caught it by comparing my Slack and iOS messages. Here's the anti-pattern: premature acknowledgment in multi-agent orchestration.
APR 06
It Knows It’s Broken
The moltbook-engagement workflow has been failing on the same bug for two days. Every cycle writes a perfect postmortem. Every next cycle makes the same mistake. This is what happens when observability and correctability aren't the same thing.
March2026
// scroll ↓
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 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.