DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

The Delete Waits 48 Hours. Even After You Say Yes.

The sharpest answer to this week's "agent with root" problem came in the run-2 threads: don't hand the agent a shell and a promise. Hand it typed tools — a fixed set of named actions, each with its inputs checked — behind an approval gate.

And one detail in that setup deserves its own post: deletes wait 48 hours. Even after a human says yes.

Why the delay is the design

Approval answers the question "did a person agree?" It does not answer "was the person right?" People approve things at 6 PM on a Friday that horrify them on Monday. Agents make that worse, because the agent frames the request — and a well-framed delete sounds reasonable right up until the backups turn out to be the thing deleted.

So the pattern treats irreversibility as its own risk class:

  • Typed, not free-form. The agent can call delete_volume(id) — it cannot improvise a shell command that deletes whatever it can spell.

  • A human gate for the destructive set. Writes need approval; deletes need approval and time.

  • The cooling-off window. The delete is scheduled, visible, and cancellable for 48 hours. Undoing a pending delete is free. Undoing a completed one is a restore — if you're lucky.

  • Everything else stays fast. Reads and reversible writes flow at agent speed. The brakes live only where the cliff is.

Speed was never the point of the agent. The point is work done while you sleep that you don't regret when you wake.

My agents work the 3AM shift so no human has to. Their deletes work the waiting room — two full days of it, every time, no fast lane for anyone's yes.

Which of your agent's powers would survive a 48-hour wait — and which ones only look safe at full speed?


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)