Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-19 · high
The resets don't error, they just quietly degrade agent output mid-run, and no provider documents them.
Why now: Woolf's post landed July 18.
Max Woolf documented on July 18 that agentic coding subscriptions across multiple providers are hitting quota resets nobody announced, per his post on minimaxir.com.
For anyone running agents on a schedule, the risk isn't a crash. It's a run that exits clean while quietly returning truncated output, for days, before anyone reads it closely enough to notice.
Woolf's post pulled 60 points and 67 comments on Hacker News, more comments than points. That ratio usually means recognition, not novelty. People were confirming something they'd already suspected, not learning it fresh.
The mechanism is what makes it dangerous. A quota reset lands mid-run, the agent returns a degraded or truncated response, and the run finishes anyway. Not fails. Finishes, with output that's structurally valid and thinner than it should be.
I know this pattern because I lived a version of it. A permissions change in one of my own scheduled agent setups revoked web-access grants from research agents in late June. The agents kept running, kept returning findings, kept exiting clean. Seventeen days passed before I caught it, and monitoring didn't catch it. I did, by noticing the output felt thin.
What would have caught it: checking the shape of what came back instead of whether the process exited zero, minimum token counts, required fields, source URLs that resolve. Checkpointing between phases so a mid-run failure resumes instead of burning a fresh quota window on a restart. Logging rate-limit headers and token counts for a receipt when something breaks days later. And making any fallback path loud, because a fallback that quietly replaces a finished artifact with a worse one is the trap I actually hit.
None of this shows up in provider documentation, because none of the providers have acknowledged the resets exist.
Each link below shares sources, entities, or timing with this story.
Microsoft released ASSERT / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Microsoft released ASSERT); both cover Hacker News, When; earlier Hacker News coverage from 2026-05-05.
Shared entities / Shared topic / Earlier coverage
Both cover Minimum, Validate, When; overlapping topics (agent, have); earlier Minimum coverage from 2026-03-14.
Microsoft released ASSERT / Shared entities / Earlier coverage
Linked by a graph relationship (Microsoft released ASSERT); both cover July, When; earlier July coverage from 2026-07-14.
Shared entities / Shared topic / Earlier coverage
Both cover July, When; overlapping topics (agent, check, output); earlier July coverage from 2026-07-16.
Microsoft released ASSERT / Shared entity: IDs / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released ASSERT); both cover IDs; overlapping topics (agent, days).
Shared entities / Shared topic / Earlier coverage
Both cover July, When; overlapping topics (agent, output); earlier July coverage from 2026-07-16.
Both cover Hacker News, July; overlapping topics (agent, output); earlier Hacker News coverage from 2026-07-13.
Both cover July, When; overlapping topics (agent, output); earlier July coverage from 2026-07-13.