Grok bot for office worker
Table of Contents
Table of Contents
The desk I already have is inbox, expenses, research, and the ops chase that never has an API. That’s where I would use a grok bot for office worker jobs.
I’m Aris Setiawan. I ship Next.js on client work. I already wrote the Grok Bot intro. Same app. This is the desk version.
Jobs I would hand a Bot
I name a Bot for the job so I can talk to it. The name is a label. Every Bot on my account still sits on one shared cloud computer.
Their product page has chips like Sales Outbound, Expense Manager, Account Health. Those are their examples. I have not run a week of them, so I will not invent hours saved.
What I would actually hand off is the work already on the desk.
I would let a Bot draft replies, sort the pile, and pull the threads I need before a meeting. I still send the ones that commit us.
I would let it export the month, match receipts, and flag the ones that need a human. I still approve the spend.
Research is the part I already hate doing by hand. Open the tabs, pull a brief, write the notes into /workspace. I still decide what we believe.
Before a call I would ask it for the agenda, the last email, and the open tickets. I still walk into the room.
The ops chase is invoices and status checks in tools with no API. If the tool has a connector, use that. In the app those show up as Plugins. If it doesn’t, the Bot clicks through the site like I would.
They can keep going after I close the laptop. I still have to be there for the login.
What I still type myself
Password, 2FA, CAPTCHA, a payment. Those come back to me.
Approvals sit on tool calls and computer actions. Require Approval or Always Allow. An approval does not undo work that already finished. That’s the sentence I’d want before anyone signed a Bot into Gmail.
All of my Bots share one Linux cloud computer. Browser, files, terminal. Cookies travel with the computer, not with the Bot name. I don’t treat a second Bot as a vault, and I don’t put prod credentials on that machine casually.
How I would set it up
I open the app on Mac or Windows. iPhone on iOS 18 if I need to watch it from my pocket.
I sign in with Cursor. There is no separate Grok Bot account.
I name one Bot for inbox, one for expenses, one for research. They share the computer. I sign them into the tools, watch the first run, and type the codes.
A skill is how to do the task. A routine is when it runs. I keep those two apart so I don’t schedule a job I haven’t seen finish once.
Teach a task can record a browser workflow into a draft skill. That rollout is gradual. I don’t treat it as a promise on every account.
It’s early beta. From 26 Aug 2026 it comes with SuperGrok and with Cursor plans. There isn’t a separate Grok Bot product to buy. I don’t have a published weekly allowance, so I won’t invent one.
The product page is x.ai/bot.
