November 22, 2026 2 minute read

Guardrails

I caused an “incident” today.

Well, my AI agent caused an incident on my behalf.

The long and short of it: I gave my agent a list of Pull Requests to merge, and it went ahead and did it. Unfortunately, it was the wrong list. I meant to merge my own PRs, but I provided the wrong list. It was a list of my colleagues’ PRs that I was watching and reviewing, rather than the ones I owned.

Ok, that was a terrible paragraph, but here’s an easy way to describe it.

I went into my neighbor’s garden and harvested all the tomatoes before he thought they were ripe, then I cooked with them and served them with dinner.

It was my human mistake. Not my agent’s fault.

Which has me thinking about the guardrails and rules I need to put on my agent when it does work on my behalf.

And it’s not as simple as “the agent shouldn’t have permissions.” Your agent needs permissions. Autonomous permissions. It needs credentials and abilities. Otherwise, it’s just not that useful. The human-in-every-loop argument doesn’t hold. It can’t hold.

So what do we do?

We think about it from the human ownership point of view. Here’s an ownership ruleset I gave to my agent based on the incident:

  1. Don’t merge or complete work that I don’t own.
  2. However, there may be circumstances where I want you to do it anyway. If I ask you specifically to do that, confirm with me first.
  3. If you cannot complete work that I’ve given you without violating the ownership agreement, ask me what you should do.

We have thousands of years of human collaboration rules (written and unwritten) baked into our collective. There’s no reason our AI agents shouldn’t play nicely.

We just have to remember to tell them.


Discover more from johnmaconline

Subscribe to get the latest posts sent to your email.

Free ebook

The Talent Others Miss

A team building strategy for seeing potential differently.

Get the free ebook

Pin It on Pinterest

Share This

Discover more from johnmaconline

Subscribe now to keep reading and get access to the full archive.

Continue reading