A scheduler that pauses agents before rate limits hit
Maleficent_Pain2722 · reddit · 2026-07-20
A Reddit post introduces agentpause, an MIT-licensed scheduler for long-running LLM agents.
What it does:
- Checks the estimated next-step cost against remaining rate-limit budget before every LLM call.
- If the call would exceed the budget, it waits only as long as needed or checkpoints and exits cleanly.
- On the next run, the agent resumes from the exact step instead of redoing work.
The author also distinguishes logical resume from a true runtime warm start:
- Cloud APIs can only resend the full context or use provider-side prompt caching.
- With llama.cpp, checkpoints can include KV-cache via /slots save/restore, which skips re-prefill entirely.
- On an M1 Pro, resuming a 9k-token Qwen3-8B context dropped from 46.9s to 0.5s, about 93x faster.
Other findings:
- History compression can be counterproductive because it breaks prefix caching.
- Blind truncation can destroy factual recall and sometimes causes the model to hallucinate replacements.
- The repo includes benchmarks, works with multiple providers, and plugs into LangGraph with minimal setup.
Related event: agentpause: Scheduler Pauses Agents Before Rate Limits(2 posts)→
More from coding & agent
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11