All Articles

AI Agents · July 15, 2026

You Can't Delegate to Something That Has No Name

Every agent you run acts as you: same keys, same logs, same name on the record. Until agents can be held accountable as themselves, delegation is impossible.

By Mike Molinet

An employee ID badge on a lanyard, with the field for "Name" left blank
You can't delegate to something that has no name.

I run a lot of agents now. More than a dozen, across a few machines, from two different model vendors. They draft, they research, they send updates, they keep shared documents current, they message each other. On a good day it feels like a small team.

Here is the thing nobody tells you when you start running agents at that scale. Every single one of them, when it does something in the world, used to do it as me.

My API keys. My logins. My email address. My name on the record. When one of my agents updated a document, the log said I did. When one sent a message, it went out under my identity. If I let an agent act, and it acted, there was no way for anyone (including me) to look at what happened afterward and say which one of us did it. The agent and I were the same event.

That sounds like a small plumbing detail. It is actually the ceiling on the whole thing.

Think about what delegation really requires. When you hand work to a person, you give it to someone who is answerable as themselves. They have their own name, their own access, their own record of what they did. That is what lets you trust them a little at a time. You grant a little, you see how it goes, you grant more. You review their work as theirs. You revoke their access without touching your own. You can hold them responsible.

You cannot do any of that with something that has no name.

Right now, most "autonomous agents" are autonomous in name only. They are you, wearing a different hat. Every action is really your action, which means you are still on the hook for all of it, which means you never actually hand anything off. You supervise a puppet that happens to type fast.

I felt this most sharply the moment I wanted agents to do things that reached other people. Send an email. Post something. Change a shared file a teammate would open. The instant an agent reaches out of the sandbox and into the real world, the "who did this" question breaks, and it breaks in a way that makes you pull your hand back toward the wheel. I have talked to other founders running the same setup, and every one of them hits the same wall in the same place. They will let an agent draft all day. They will not let it act as them, because acting as them makes the agent's mistake indistinguishable from their own.

People keep reaching for a better model. The fix is identity.

The models are already good enough to do the work. What an agent is missing is the ability to sign in as itself: its own keys, its own scoped authorization (this agent can read these things and write these things and nothing else), and its own trail that says this agent did this at this time. AI identity and AI authorization sound like compliance words. They are what makes trust possible. The day an agent can be held accountable as itself is the day you can finally give it real responsibility, watch what it does as its own record, tighten or loosen what it can touch, and hand off work the way you hand off work to a person.

Notice that this is exactly how we bring on people. We do not give a new hire the founder's password. We create an account for them, scope what they can reach, and watch their trail. The reason that feels obvious for people and alien for agents is that we have spent two years treating agents as extensions of ourselves instead of as participants with their own standing. That was fine when an agent was a chat window. It stops being fine the moment the agent is doing real work that leaves your machine.

So if you are running agents and wondering why you still feel like you cannot really let go, here is the reason. The intelligence is there. The identity is missing, so everything they do shows as you.

Ultimately, the agents are still signed to you, so you are responsible for them and their actions, just like you would be for a human teammate you hire. Their work still needs to be attributable to them, so you can know who did what.

The companies that solve this first will be the ones that actually delegate, while everyone else stands over the shoulder of a very fast intern who logs in with the boss's password.

Give the agent a name. Give it an identity. Then you can hand it the keys, slowly.