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
- PyTorch practitioners are being urged to treat profiling as a basic skill — RisingSayak · 2026-07-21
- DocETL adds a Python DSL and new tools to clean up long-form LLM outputs — sh_reya · 2026-07-21
- AI-assisted development is widening security backlogs, so teams should measure risk velocity — WeldPond · 2026-07-21
- Frontend Textbooks turns long Codex outputs into book-style documents — nbaschez · 2026-07-21
- A Codex harness user says OpenAI’s assistant is less smart-sounding but more decisive — McDonaghMatthew · 2026-07-21
- Octen’s search benchmark is public and reproducible for agent stacks — aakashgupta · 2026-07-21