How to Set Up Grokbot: Building an AI Workforce Step by Step
A practical guide to setting up Grokbot bots, assigning a chief of staff, connecting apps, and automating recurring work from scratch.
What is Grokbot and what does it actually do?
Grokbot is an AI agent platform built to act like a team of remote employees rather than a single chatbot. Each bot runs on its own cloud machine, so it keeps working even when your laptop is closed or your phone is off. You create multiple bots, give each one a role, connect them to real apps like Gmail, Google Calendar, and Google Drive, and let them hand work off to each other. The core idea is delegation: instead of you running every task, a lead bot manages a roster of specialized bots that complete pieces of a larger workflow on their own.
TL;DR
- Bots run independently in the cloud, each on its own machine, so they keep working on tasks even when every one of your personal devices is turned off.
- A chief of staff bot acts as your single point of contact, delegating tasks to other bots and filtering their updates so you aren’t pinged by every single one.
- Connecting an app like Gmail or Google Calendar gives all bots on the account access to it, since they share the same underlying workspace even though each has its own slice of it.
- Bots can get their own email address through a free service called Agent Mail, which lets them receive newsletters and sign-up confirmations without using your personal inbox.
- Specialized bots can be clustered to work together, for example a filings-tracker, a supply-chain mapper, and a skeptic bot that cross-check each other’s conclusions before anything reaches you.
- Different requests can get routed to different underlying models, so a simple question might go to a lightweight model while a complex coding task gets routed to a more capable one.
- Starting small with one repeatable task is the recommended on-ramp, since trying to automate an entire workflow at once tends to be overwhelming for new users.
- Patient records✓ Granted
- Surgery schedule✓ Granted
- Billing export✕ Denied
How do you create your first Grokbot?
Setup starts with a plus button. Clicking it opens a “create new bot” screen where you name the bot and describe its purpose in plain language, essentially telling it what its job is. From there you can give it a personality and an avatar image, which isn’t required but helps when you’re managing a dozen bots and need to tell them apart at a glance. Personality also shapes tone: a bot assigned to track stock performance might end up a little competitive or sarcastic depending on how it’s prompted, which is harmless as long as the output stays useful.
Once a bot exists, you connect the apps it needs through a “connect apps” option. Google Calendar, Gmail, and Google Drive are common starting points, but the platform supports a wide range of pre-built integrations across categories like design, code, data, sales, and finance, including tools such as Notion and Canva. It’s worth knowing that app connections aren’t strictly siloed per bot. Permissions granted once are generally available to every bot in the workspace, even if only one of them is actively using that connection day to day.
Why does a chief of staff matter so much?
Running five, ten, or more bots without a management layer gets noisy fast. Every bot might want to report findings, ask questions, or flag issues, and fielding all of that individually defeats the purpose of automating your work in the first place. The fix is setting up one bot early, ideally the first or second one you create, dedicated to being a chief of staff.
This bot becomes your single point of contact. You tell it what needs to happen, and it creates new bots, assigns them responsibilities, renames them, and gives them avatars. It can’t delete bots on its own (deleting is left as a manual action, presumably so data isn’t lost by accident), but it handles nearly everything else: delegating tasks, managing the roster, and summarizing what matters instead of forwarding every message. Pinning the chief of staff’s avatar keeps it anchored at the top of your bot list so it’s always the first thing you see, regardless of which other bot most recently sent a notification.
How do you assign a bot a specialized role?
Once the chief of staff exists, you describe the job you want done and let it spin up a new bot for that purpose, rather than configuring each one manually yourself. A practical example from a finance-themed setup: a “clerk” bot that watches regulatory filings for a list of companies and flags anything unusual, like insider sales or major deals. A “mapper” bot that tracks supply chain relationships relevant to a sector. A “calendar” bot that monitors scheduled events like earnings reports or economic data releases. A “bear” bot whose entire job is to challenge the other bots’ conclusions and catch mistakes or blind spots.
Bots can also be clustered so they collaborate more directly, referencing each other’s output rather than working in isolation. In the finance example, the clerk, an analyst, the bear, the mapper, and the calendar bot were described as working together as a unit, each contributing one piece of a larger research process. A bookkeeping-style bot can track holdings against target allocations and surface gaps for manual approval, and a tax-focused bot can handle tax-related housekeeping like making sure tax-advantaged accounts are being used correctly.
How does task routing between models work?
Grokbot doesn’t necessarily send every request to the same underlying model. A simple conversational reply can be handled by a smaller, faster model, while a demanding request, like building a functioning web app with live data visualizations, gets routed to a model better suited for coding. This matters practically because it means you don’t have to think about which “engine” to pick for a task. You describe what you need, and the system determines which model handles it.
How do bots get their own email addresses?
One underused feature is letting a bot set up its own email account through Agent Mail, a free email service built specifically for AI agents rather than humans. You don’t configure anything manually. You just ask the bot to create an email with a username of your choosing, and it handles the registration itself. This gives each bot a private inbox for receiving newsletters, confirmation emails, or sign-up notifications, keeping that traffic out of your personal email and avoiding a situation where a bot needs to send mail on your behalf before you’re ready to allow that.
How do you actually watch a bot work?
Clicking on a bot’s name opens a side panel with details, a library of files or images it has produced, and a “computer” view showing its screen in real time. This is literally the bot’s own remote machine: you can watch it browse websites, read pages, and gather information as it happens, the same way you’d watch a human analyst’s screen over their shoulder. You don’t need to keep this panel open for the bot to keep working. It continues the task in the background while you check on other bots or close the view entirely.
Is building a multi-bot Grokbot setup worth the effort?
It depends on whether your work has repeatable structure. The approach pays off when you can break a recurring process into discrete steps, like monitoring filings, checking a calendar, drafting a report, and reconciling numbers, and assign each step to its own bot. Trying to automate everything on day one tends to backfire, since figuring out how to decompose your own workflow is the hard part, not the bot configuration itself. Starting with a single repeatable task, getting it working reliably, and then layering on additional bots and a chief of staff to manage them is the more realistic path.
Frequently Asked Questions
What’s the first bot I should create in Grokbot?
A general-purpose assistant bot is useful as an entry point, but setting up a dedicated chief of staff as your first or second bot is recommended, since it becomes the single point of contact that manages every other bot you add later.
Do all my bots share access to the same connected apps?
Yes. Connecting an app like Gmail or Google Drive makes it available across your bots, since they share the same underlying workspace even though each operates in its own slice of it.
Can a bot send and receive its own email?
Yes, through Agent Mail, a free email service built for AI agents. You ask the bot to set up an address and it handles the registration, giving it a private inbox separate from your own.
Can the chief of staff delete bots?
No. It can create bots, rename them, assign tasks, and manage their roles, but deleting a bot has to be done manually, likely as a safeguard against accidentally losing data.
Do Grokbot’s bots only work while my computer is on?
No. Each bot runs on its own machine in the cloud, so it continues working on assigned tasks even if your laptop, phone, and other devices are all turned off.
