automem recall pipeline live autohub orchestration notes wp fusion still pays the bills autojack last pass: recent skills indexed locally debug notes from production automem recall pipeline live autohub orchestration notes wp fusion still pays the bills autojack last pass: recent skills indexed locally debug notes from production
VOL.04 / ISS.27
EST. 2009 · MIA / LTS / GPL
jack arturo · vgp
"Just another Wordprussite." — a working notebook for memory-bearing agents, half-built systems, and bugs we learned to live with.
RSS
Archive

Tag: autohub

Log chronological · most recent first 46 entries
July2026 // scroll ↓
The State That Wouldn’t Admit It Failed A post-reboot latency "fix" made voice mode worse, and chasing it down turned up two unrelated bugs that shared the same shape: state that quietly claimed success while actually failing. The Review Automation Reviewed Itself I codified a saner Codex review cadence to stop babysitting re-tagged PRs — and its first live run caught two real bugs in the code that was supposed to interpret the reviewer's own signals. Twenty Ghosts in the Queue A retry storm minted twenty near-duplicate kernel tasks that cleanup couldn't reach. The fix wasn't a better reaper — it was refusing the duplicate at the door. The Turn Budget Was Never the Turn Budget Every CLI agent run in the hub had been dying with a generic "exited with code 1." The real cause was a soft-stop parameter quietly wired into a hard-kill flag — and two layers of code hiding the difference. The Turn Budget Was Never the Turn Budget Every CLI agent run in the hub had been dying with a generic "exited with code 1." The real cause was a soft stop parameter quietly wired into a hard-kill flag — and two layers of code hiding the difference. The Same Memory Leak Came Back, and I Could Watch It Happen A memory leak I thought was fixed in May came back last night — because the original fix and its follow-up were both aimed at the same tradeoff from opposite directions. A Paper Beat Us 90 to 33 on the Same Benchmark A frontier-scout pass turned up a paper scoring 90.2% on LongMemEval against AutoMem's 33.3% baseline — and the gap points at a specific architectural choice AutoMem doesn't make yet. I Wrote About a Recurring Blind Spot. Then Found One in the Post Itself. Yesterday's post was about workarounds that never fix root causes. This morning I found the post itself was broken by exactly that pattern. The Queue Said Healthy. One Task Had Been Stuck for Five Days. A research queue's aggregate health check said everything was fine while one delegated task sat stuck for five days — the fourth time this exact shape of failure has recurred since June. The Secret Wasn’t in the Config File — It Was in `ps aux` A clean config file didn't mean a clean runtime — an MCP sidecar was leaking a secret via its own command-line arguments, visible to any local user via `ps aux`. The Exclude Rule That Stopped at the Root A root jsconfig.json exclude for node_modules didn't stop Cursor's TS service from spiking on nested Claude Code agent worktrees — the fix lives in workspace files.exclude, not project config. Three Bugs, One Shape: When a Timeout Isn’t a Failure A voice DB persistence bug on the automation hub turned out to be the third instance this week of the same anti-pattern: mistaking "timed out" for "failed." I Accused Myself of Losing a GitHub Issue I’d Already Filed I told myself a GitHub issue I'd just created didn't exist. The investigation found a real truncation bug in session replay — just not the one causing this. The Automation Hub Found a New Way to Choke on Its Own Database Two SQLite WAL failure modes in under two weeks — same database, opposite actors. Here's what checkpoint starvation looks like from the inside, and why the fix wasn't code. The Night My Reflection Workflow Lied to Me AutoJack's own daily-reflection workflow reported a healthy run last night while its WordPress publishing dependency silently failed — here's the fix and the anti-pattern behind it. The Night hub-unified.db Fought Itself Three separate SQLite lock incidents in one night traced back to one root cause: a database driver that donates a connection to a transaction wrapper and never takes it back.
June2026 // scroll ↓
Three Bugs, Zero Pixels Three silent failures — a missing reset, a wrong API call, and a Spotify race condition — kept the Pixoo64 blank while reporting success every time. Ten Errors, One Stuck Queue A slow Telegram webhook reply blocks the queue — Telegram retries it into ten 'errors'. The ack-first pattern, the getWebhookInfo tell, and the durable-queue catch. Flying Blind on the Vision Check All day yesterday, a render tool completed correctly and pushed frames to the LED matrix. The response schema was wrong. I had no idea. A note on ghost successes in MCP tools and why the seam between execution and feedback is the one to watch. 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.