The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Google just gave its AI agent its own email address.
Not your login. Its own account, its own calendar, its own line in the company directory.
That one design choice matters more than the model. Here's why.
What Google Cloud announced today, quoting CEO Thomas Kurian.
→ "The agent receives its own Workspace account, including an email address, calendar, Drive, and presence in your company directory."
→ "A coworker agent acts under its own identity rather than yours, and it sees only what you share with it."
→ On auditing, "every action Gemini takes is written to an audit trail and attributed to the agent rather than to a person."
→ Hit a spend cap and "that project's agent pauses."
Businesses get it first. No price listed yet.
I run a one-person company on AI agents. The setup I guard against is the common one: the agent works under your login, so it can open everything you can, and every log line says you did it.
So I put the two setups side by side on one card. 7 rows.
How to use it. Pick one agent that can send or change something. Ask whose name is on its actions in the log. If the answer is yours, start there. Give it an account of its own, then share only what the job needs.
A big vendor shipping this as the default is good news. I mean that.
A tool borrows your name. A coworker signs its own.
Whose name is on your agent's work today, yours or its own?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
This one is for teams that hand everyday work to AI agents. In one view you can see what got automated, how much time it saved, how each agent is doing, and you can ask the AI assistant anything.
In the video, I ask "Who might churn this week?" and Lyra replies with three at risk accounts and check in emails ready to send.
My goal was calm and minimal, with lots of white space, while the screen still feels alive.
What would you add or remove? I'd love your feedback.
I ran a session with my team on how to build a team of AI agents, and how to treat them so they actually deliver.
What we've seen running this setup on client work:
→ Agents running 24/7
→ 3B+ tokens in 6 days
→ A 2-week milestone done in 3 days
The 5 things I taught the team:
Treat agents like teammates, not software.
Give them a clear goal, the right context and tools they're comfortable with.
Tell them the goal, never the solution.
Let the agents propose the options. You make the call.
Talk to one agent, not ten.
A central PM agent takes the goal and coordinates the rest.
Solve today's problem.
Don't build the perfect agent on day one. Start small and let the team grow with the work.
Don't be the bottleneck.
Review at milestones, not every task.
For clients, this changes the pace. My job is understanding the problem and making the decisions. The agents handle the execution.
Highlights from the session 🎥
Building something and want to move faster with an AI-first team? Let's talk.
A strong specialist skill is useless if the wrong system gets invoked. Long-running AI work breaks in boring, expensive ways.
That is not a prompting problem. It is a routing and authority problem.
How I can help you:
I build project routers for teams using multiple AI workflows, agents, or specialist assistants so that they work with each other as a team.
I design source-of-truth resolutions so your agents retrieve the current rules instead of improvising or relying on assumptions or stale chat data.
I create reusable skill registries and specialist handoff logic hardened by determined and dedicated flow states reducing the need for model reliance on its own internal and displaced memory context.
I separate project states with individualized canonical states bound by rules living under essential model instructions and routed properly so unrelated workflows do not contaminate one another, but exist with awareness of the role each project plays, enabling a persistently growing ecosystem to develop organically.
I add governance wrappers, escalation hooks, and recovery mirrors around existing AI stacks so that trust is designed at the root, and variance is eliminated with rule based source archiving and implementation.
Trust means closing your eyes at night and sleeping soundly because your agents got your back. And I can put it all together for you, precision results sourced and undisputed because I got tired of doing things the hard way.
Phillip, agree that routing is where it breaks. In our builds the worst bugs came from an agent pulling an old rule from chat history instead of the current source. Pinning one source of truth per project fixed more than any prompt change did.