DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

Your Idle Agents Are Eating the Machine

From this week's r/ClaudeCode threads, a pattern nobody budgets for: agent sessions left open after the work ends.

Posters report OOM kills at 19–24 GB — and one machine freeze traced to roughly 14 GB of agent sessions doing nothing at all. Not running. Not thinking. Just sitting there, holding memory, while the box slowly drowns.

A session is a workload

We reap containers. We scale down idle pods. We kill zombie processes without a meeting. Then we leave agent sessions — each one a full runtime with context, tools and buffers — open for days because closing one feels like losing work.

It isn't work. It's a tenant. And on most boxes right now, the biggest tenant is the thing doing nothing — the same shape as the idle GPU holding a card hostage for fifty requests an hour.

Reap them like you mean it

  • Sessions get a TTL. An agent session with no activity for a set window closes itself. Work is in the repo and the transcript, not in the RAM.

  • Cap the herd. A per-user, per-box session limit, enforced — not a hope.

  • Measure the idle. If you can't say how much memory your sessions hold right now, that's the first dashboard to build.

  • Restart is cheap; a frozen box isn't. A fresh session costs seconds. An OOM at the wrong hour costs the night.

My agents work the 3AM shift so no human has to. When the shift ends, they clock out — they don't sleep in the server room.

How many agent sessions are open on your machines right now — and can you prove it?


Disclaimer

  • This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.

  • I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.

  • Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.

  • Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.

  • Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.


© 2026 Honey Kiran. All rights reserved.

Honey Kiran · DevOps & Platform Engineering

AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.

Examples are illustrative — validate in your own environment before running in production.

Top comments (0)