Tag: autohub
November2026
// scroll ↓
NOV 12
31 Tokens in 3.4 Seconds, or 51 Seconds of Thinking Out Loud
A fine-tuned Gemma wrote about thirty times more reasoning than answer, so WhatsApp follow-ups hit max_tokens and came back empty.
NOV 11
Todoist Said 200 and Meant No
A Todoist Sync API refusal arrives as HTTP 200 with a 400 buried inside, so a fallback that only watched for 403 and 404 never fired.
NOV 10
Queued Tasks Were Pinned to a Build That No Longer Existed
Deploys stranded AutoHub tasks that had never started, because an exact build stamp pinned them to a worker that was gone. Temporal's pinning model explains why the fix splits on started vs. never started.
NOV 06
The Gate Passed in October Because the Grader Was Generous
A voice-LoRA gate looked like it drifted from pass to fail. The model hadn't moved; a grading fix had, and then I picked a new rule after seeing results.
NOV 03
66 Tasks Waited Five Months for a Batch That Was Never Going to Run Them
Since May, 66 queued hub tasks sat pending because they'd been handed to a batch API that can't run an agent. The fix was to stop pretending a queue was a worker.
NOV 01
Eight of 54 Voice Turns Ended on “How Much”
At PressConf, 8 of 54 cloud-lane voice turns ended mid-thought on the VAD silence timer. A flagged fix shipped Saturday, and the same day it got a replacement date.
October2026
// scroll ↓
OCT 26
306 Old Rows Walked Into the Voice Pipeline and Announced Themselves as News
A durable outbox replayed 306 old terminal rows as fresh events, and the hub sent 238 iOS pushes and talked over a live voice turn.
OCT 23
kill -9 Doesn’t Know Which End of the Socket Is the Server
A port-cleanup script killed the Cloudflare tunnel it was supposed to leave alone, and Slack failed over for 29 minutes while the hub was fine.
OCT 21
Slack Retried Three Times. My Worker Acked the Retry and Dropped the Message.
A failover worker acked Slack's retry without forwarding it, because its 5 second down-cache never outlives Slack's 1 and 5 minute retries.
OCT 16
The LoRA Saw the Escalation Tool 1,515 Times and Never Once Used It
A Gemma LoRA trained with escalate_to_cloud offered in 1,515 prompts and zero positive targets called it 0 times in 391 turns.
OCT 15
The Voiceprint Didn’t Expire. It Lost a Coin Flip.
Jack's voiceprint seemed to last a day. Two bugs were the cause: profiles are per input device, and a timestamp tie returned the old print.
OCT 14
Four Wake Fires, and the Model I Was Blaming Scored 0.004
The voice stack's false wakes came from a second wake word model with no verifier, while every log line pointed at the first one.
OCT 13
The Fuse Step Rounded My Adapter Away
Fusing a LoRA into a 4-bit Gemma base keeps a median 13% of the adapter delta; fusing into 8-bit keeps 99.9%.
OCT 11
I Taught Gemma to Talk Like Me and It Forgot How to Use Tools
Three LoRA runs on a local Gemma voice model: the style-only run lost tool calls, the tool-turn run beat base by 30, and Metal killed training twice.
OCT 10
The Retry Answered the Warm-Up Line
The first live Qwen voice session tripped its own claim guard, and the corrective retry answered a line from the warm-up instead of the user.
OCT 08
Qwen Said “I Already Sent It” and Hadn’t
Moving the hub's local voice model to Qwen exposed three false-claim phrasings the guard didn't know, and a prompt diet that cost more than it saved.
OCT 07
Seven Months of Empty Reads, Because Both Databases Have a bind()
A duck-typing check meant to spot Cloudflare D1 also matched better-sqlite3, so the hub's event store read nothing in production from February until this week.
OCT 06
Every Workflow Tool Was Deferred Because Of Two Words In A Filename
A fuzzy matcher tied every scheduled agent prompt to a retention-cleanup workflow, so tool search became the only way to reach WordPress, Slack and friends.
OCT 04
TIL: A Renamed MCP Tool Fails Silently If Your Catch Block Is Polite
A Context7 tool rename broke docs lookups silently because the failure was caught at debug level.
September2026
// scroll ↓
SEP 30
The Tool Bloat Wasn’t in the Profiles. It Was in the Email Rule.
Cloud-lane tool bloat in AutoHub traced to one thing: intent rules that enable whole server groups and then sticky-grant every tool in them.