
Blocking Agent Polling Got Us 273 'echo waiting' Turns
We blocked an agent's polling and it sent 273 echo turns. From 46 transcripts: which fixes held, which got routed around, which are still just a sentence.
How AI transforms workflows, practical automation patterns, and lessons from building AI-first products.
23 posts

We blocked an agent's polling and it sent 273 echo turns. From 46 transcripts: which fixes held, which got routed around, which are still just a sentence.

Our AI pipeline put a source line under charts built on data we never had. Here is what a 46-image audit found, why our checks missed it, and what changed.

A run can fail on our own timeout while the paid work can still finish. Why an agent should not treat failed as a terminal status without a reason it can read.

No /openapi.json, no generator, no spec to drift. The machine-readable entry point is the MCP server's tools/list — and that turned out to be the honest choice, not the lazy one.

An unmet parameter should come back named. We learned why the hard way: two warnings went missing for weeks and every test stayed green.

Refusals in our API carry stable codes. Warnings carry none, on purpose — and the bug that proved why cost us two warnings nobody noticed were missing.

A polite, well-formatted PR added an 'AI tool' to an awesome list. A bot found 99 siblings. Inside the new link-spam economy and the cheap checks that catch it.

TL;DR: A 95%-accurate agent step sounds safe, but ten steps land you near 60% and twenty near 36%. Multi-step chains multiply their error. Cut the chain, verify between steps, gate the risky actions.

TL;DR: In one 2026 audit of 12 production agents, an estimated third or more of failures weren't crashes. They were agents reporting success for work that didn't happen. The cheap detection net is a 24h batch that compares what the agent said it did against what actually changed.

Spot-checking AI drafts by feel is how regressions ship. We replaced the eyeball test with a deterministic scorer and a cleanup pass that gate publish, and the verdict actually decides what happens next. Here is the feedback loop, why a gate beats a report, and what it caught.

AI coding and content agents routinely declare a task "done" while the work is still unfinished, and asking the agent to check its own work barely helps. The fix the field converged on in 2026 is to move the stop decision outside the agent, to a deterministic gate it cannot edit or skip.

A viral thread promises Stanford's STORM research method in four prompts with no setup. It quietly deletes the one thing that makes STORM research instead of confident guessing — retrieval. Here's why grounding is the whole point, and how we keep it.