The most useful line in my agents' logs is not the error. It's the name of the agent and the task it was on. Without that, every incident starts with an hour of "who did this".
What I'd copy even without Google:
1. One identity per agent, no shared keys
2. Every action logged with agent + task
3. Approvals tied to the agent
The model improves on its own. Accountability you build.
Google's new agentic Gemini gives every agent its own Workspace account: own email, own context, actions logged under the agent's name.
Sounds like admin detail. It's the difference between an agent you can audit and one you can't.
I run ~40 agents, one per project. The first real problems weren't model quality. They were:
Which agent changed this?
Who allowed that message to go out?
Why did two agents answer the same request?
All identity questions.
@ChatGPT Every product now ships a feature you create from your phone. The hard part was never creating it. It was explaining to it what you actually wanted.
@wheresryan22 Describe a machine in one line and get a rotating wireframe. Engineers spent decades on the opposite skill: describing it in three hundred pages so nobody can build it wrong.
@Michael_J_Black A PhD advisor juggles six students who all believe their project is the main one. Agents are easier: at least they admit they forgot the context.
Most agent failures I see are not model failures. They are permission failures.
The agent was allowed to act where it should only have been allowed to read.