Cloudflare's new "Gatekeepers" concept for agent approvals — anyone tried it?
Cloudflare put out an open-source project called Cloudflare OS a week or so ago, and the part that caught my attention is "Gatekeepers": a capability-based layer that requires async approval before an agent can take a sensitive action. It got a lot of attention on HN specifically for that idea, more than the platform itself.
I've been dealing with a version of this same problem: figuring out where the line is between actions an agent should just do versus actions that need a human to say yes first. The "async" part is what's interesting to me. Most approval flows I've seen block the whole turn until someone responds. Doing it asynchronously means the agent can keep working on other things while one action sits waiting.
Curious if anyone's actually wired this into a real workflow yet, and whether async approval ends up feeling smoother in practice or just adds a different kind of complexity (tracking what's pending, handling timeouts, etc).
Replies