Lauren Tan & Roman Ugarte on AI agents as teammates, not tools
The team behind xAI's Grokbot argues that AI agents should be run like employees — given identities, tools, and scoped trust — so that once execution is cheap, a company's real work becomes defining intent, guarding quality, and redesigning itself around bots.
Bots, Not Chats, Are the Unit of Work
<strong>The unit of work is the bot, not the chat</strong> — each one gets its own identity, the same tools a human uses, and runs proactively instead of waiting to be prompted.
we wanted to build a product uh where the work was organized around bots as the key operative principle, not around chats or around files or any other primitive.
Onboard a Bot Like a New Hire
<strong>Onboard a bot the way you would onboard a person</strong> — give it a computer and credentials, scope them to its role, and widen access only as it earns trust.
The way we try to answer these questions is what would you do for a human?
Do the Work in Public
<strong>Bring the agents to where the work already happens</strong> — in a public Slack or X thread, one power user's workflow becomes something the whole company can watch and copy.
the more that the stuff is in public, I think more the more of the rest of the company that can get lifted up by the top 1% power users who are very tooling minded, very engineering minded and know exactly how to use these tools.
The Bot With No EQ
<strong>Multiplayer AI is still unsolved</strong> — a bot dropped into a human thread has no sense of who to listen to, and that has to be fixed at the product, harness, and model levels at once.
It's as if you were to onboard an employee who has no EQ and like no like social awareness of the room. Just the models weren't trained that way. The harness wasn't built that way.
Execution Gets Cheap, Taste Gets Scarce
<strong>When execution gets cheap, defining the problem gets expensive</strong> — with a hundred agents on tap, the failure is rarely bad execution and almost always a bad goal.
It really matters that you define the problem well and the gap is probably not going to be an execution failure. It will probably be a uh intent specification failure or a goal failure.
The Codebase Is Memory
<strong>Your codebase is memory</strong> — encode a rule as static analysis once and you stop paying to re-review it, which is how fast, cheap, and good stop being a pick-two.
from the engineering point of view uh I like to think of this as you know your your code base is a form of memory
The Company Shrinks to Three Roles
<strong>The AI-native company sheds middle management</strong> — everyone becomes an IC who ships outcomes, a DRI owns each outcome, and a player-coach teaches the rest.
the way uh Jack Dorsey talked about it is like in a organization you would get get rid of pretty much all middle management and it would basically boil down to just three roles.
Change Your Life With a Tweet
<strong>You can change your life with a tweet</strong> — Lauren Tan went from a finance degree to a top AI engineer by doing interesting things in public and talking about them.
you could change your life with with just a tweet.