Y Combinator Startup Podcast · Startups & Venture · November 2026
A host asked how permissions, authentication and access should work for bots with their own identities. He says nobody has a silver bullet and offers the new-employee analogy as the shortcut.
do you think of that? How do you think of permission and auth and access?
How does Grockbot do it?
I think this is an industry-wide question. I don't think anyone has the silver bullet answer yet. I think, not just for auth, but for everything related to Grockbot, the way we try to answer these questions is: what would you do for a human? And if we're really trying to build an AI Coworkers, maybe the shortcut is let's not overthink it and complicate it. What does it look like to hire a person? You hire a person, you give them a computer. You give them access to credentials. You maybe scope those credentials based on their role, maybe how new they are. As they build more trust, you maybe expand their access level. And so, what would it look like for us to onboard a bot to our company with kind of those same principles? And maybe we don't have to rebuild things.
This is what we did with Quartermaster. This is the YC project that we open sourced. It's like a bit kind of Grockbot-ish. And the permissions that it gets per Slack channel or working with someone, it inherits the ones of the user. So, me as a GP has certain access as opposed to, let's say, a…
Quartermaster, though, is built in this paradigm of there being one super employee bot. Yeah, as opposed to this swarm of bots. I'm curious: are the bots able to talk to each other without the humans seeing what they're saying to each other? Can they go off and have their own conversation?
They can talk to each other. I mean, in the Grockbot application, both desktop and mobile, you can see their chat. So, we have a first-class tool for the bots to chat and collaborate. And it's often quite entertaining to look at them to just see, like, you know, we've had examples where I told one…