Emi and the engineers on my moontower.ai team have been harping on me to download Grokbot. It’s an always-on AI agent that lets you assign multi-step work to persistent AI teammates “staff” on their own cloud computers.
The Cursor team (acquired by SpaceXAI) just feels like they nailed this. You keep hearing about “agents” working around the clock for nerds who like to brag about their AI armies. Grokbot sands down the rough edges to give normal people a chance to plug in to a world of their own assistants.
You download it on your computer (Mac, Windows or Linux) and get the phone app from the App Store or Google Play. Your bots and conversations sync between them, so I start something on my laptop and check on it from my phone.
It’s included with paid Cursor plans and runs on a weekly usage allowance. First-time users get the first month for $15, which renews at $30 a month afterwards. There’s several plans that give you usage and pre-pay discounts.
Let’s dive in.
The setup
The onboarding UX is gentle, fast, and self-explanatory. You name your first bot who will act as the manager bot. I just called it “Chief”.
You can simply chat with Chief and tell it to do asks or spin up more bots. We’ll get to that. Let me take you through my first few hours.
Chief
There’s a “chief” agent that knows my whole world at a high level. I seeded it with 4 sets of sources.
1. “About me” doc
I had Claude generate a description of my businesses and context about my life it knows from what I discuss with it. For example, coaching sports teams or building an ADU on our property.
2. Connecting apps and MCP/APIs
-
Gmail, two accounts: your personal and your work inbox
-
Google Drive
-
Google Calendar
-
Moontower.ai MCP
-
Twitter
-
Notion
-
Linear
-
Stripe
-
Slack
-
Supabase
-
GitHub
-
Had it help me create a Discord bot it can communicate with
3. Knowledge base
I had it read and index all my writing across Substack, WordPress, moontower.ai/blog, and notion.moontowermeta.com. You could have it crawl your PKM (personal knowledge management) system, digital notes, Drive, or even a local file system.
4. A Mission
This summer in hedging is for gardeners, I wrote:
I spent over an hour walking through the local hills while talking to ChatGPT’s voice functionality Thursday evening. It was the easiest way to think through a large automation project. I won’t discuss the project yet but the sense I had while architecting it with ChatGPT was a new one. It was the feeling I know some friends had about 8 months ago and a smaller group of people (but not a tiny group) had 18 months ago and so on. A tiny group had the feeling a decade ago.
I never got around to implementing the project which I called Personal AI OS. In short, the automation project is an operating layer that turns your messy idea dumps and recurring obligations into verified work, so you don’t have to do the project-management overhead yourself. The AI’s within it have roles like orchestrator, chief, data scientist, etc. I had several spec documents related to its construction based on about an hour of back-and-forth with ChatGPT.
As with many things AI, the thing you can imagine just seems to become reality if you procrastinate for 3 months.
[This is simultaneously exhilarating and terrifying, like morning sex on doomsday].
I gave Grokbot the spec documents, so it understood my objectives. Honestly, I don’t think it really needed them since those documents are clunky blueprints to a problem the Cursor wizards have already had their sights on.
Subagents
Then each lane gets its own specialist.
One for writing, one for Moontower ops, one for coding, one for travel, one for household logistics, and one that reads my X lists so I can check X less. They can message each other while each maintains its own memory.

Why split them up?
Every one of these bots has a limited working memory per conversation. You’ve probably seen LLMs inform you when a thread gets long that it’s “compacting”. This specialized focus per agent lets a thread get longer without degrading
Grok itself tells me the bigger reason it works is that the important stuff per agent can be stored in its own files. For example, the writing bot keeps a voice guide, an index of everything I’ve published and a map of ideas I keep coming back to. I don’t know if it’s accurate to say this, but it at least feels like each agent is the equivalent of what Claude calls a “project” in the setup I’ve been using all year.
The cost of subagents is the handoffs. The chief only knows the outline of what the writer is doing, so anything that crosses lanes has to be written down or passed along on purpose. But handing off is part of manual work as well. As it is, if I tell an agent what I want to do on a website, I tell it to make me the prompt to give to my Claude browser extension agent, and it just makes the changes from the prompt.
The next step is to automate even the hand-off. I set up a shared board in Notion called the Agent Handoff Board. It’s one database where my agents (Grokbot, Claude, Meta Muse) pass work to each other. Each gets its own inbox view. The rules are what you’d give a new hire: check the queue a few times a day, claim a row before you start it, log progress in dated lines you never go back and edit, set a “next check” date, and if you need me, flag the row and write the exact question.
Nothing sends an email, files a dispute, pays, buys, or deletes anything because of the board without my OK in chat. The board is for coordination but permission still comes from me.
Grokbot read the page, set up its own recurring check, and started on the first row.
First hours of work
After telling the Chief to spin up these agents, I noticed the Chief starting to delegate. For this post, I asked it what it did for me since onboarding. It asked its direct reports.
This made me laugh, although I’m sure it was sincere:
Ops and X Digest still haven’t sent their rundowns. I’ll add their lines once they do.
Just like human teams, always a couple of slackers.
I hear “Ops” was seen at the dollhouse for the lunch buffet. I thought that went out of style with the trading pits.
Finally:
All six agents have answered, so here’s the whole team’s list. Ops warned that its Stripe numbers are internal business data, so I left them out.
[lightly edited for some privacy stuff]
What the agents did in the first 2 hours
Chief
-
Built the team: the specialist bots plus a shared Notion board where they hand work to each other.
-
Connected Gmail, Calendar, Notion, Slack, Linear, Stripe, Supabase (read-only) and a read-only Discord bot.
-
Wrote a Monday brief and a markets and vol digest, and split the digest into 3 posts sized for Discord.
-
Set up 5 recurring jobs. They pair newsletter ideas with what vol is doing, check classifieds, turn beta feedback into draft Linear tickets, flag community questions nobody has answered, and send a Friday best-of-Discord recap to the writer. None of them post without my OK.
-
Automated classified ad bookings with a Notion tracker and a Stripe checkout link.
Writer
-
Indexed 2,680 documents across Substack, WordPress, Notion and moontower.ai.
-
Mapped 71 recurring ideas across 11 themes, each backed by quotes checked word for word.
-
Fact-checked a reader’s I-bonds pitch
-
Caught two number errors in an IG story before I recorded it.
Ops
-
Found the last product-update email and catalogued new features since the last one
-
Ran a 30-day health check on billing, looking at chargebacks, failed renewals and retries.
-
Traced a bug where the in-app chat gave the same canned answer to a specific user. Diagnosed the source and drafted a reply to the user who reported the issue, and I sent it.
X Digest
-
Read 334 posts across my two focus lists and picked 5, so about 1.5% made the cut.
-
Worked around the fact that it can’t read lists directly by using a public search filter.
Travel
-
Priced holiday flights from three Bay Area airports, then about ten other destinations, plus a second family’s airport on the other coast.
-
Pointed out that moving the dates a few days likely saves more than changing the destination. Nothing was booked.
Household
-
Turned my scattered notes into a status brief for each area of the house.
-
Rebuilt a year of emails on a home office redo and ADU. Figured out who owed the next reply.
Coding
-
Got connected to 15 code repositories. No coding work has been assigned yet.
The first handoff
The first row on the board was a medical bill. A One Medical visit in September got coded as a problem visit instead of the annual physical it was, which turned a free preventive visit into an $800+ bill. Grok pulled the claim data, built the case for why the code should be the physical, drafted what to say to One Medical’s billing office and the fallback if they wouldn’t budge, and lined up the United Healthcare follow-up.
Impressions
In the short time I’ve had Grokbot running, I’ve noticed many proactive updates from each agent. I’m also using it for things I shouldn’t (for example, doing work I have Claude and Muse doing), but I’m trying to get a feel for it and compare its performance. It will take time to feel out where its assistance is most appreciated and how to use it best. And this will have more stakes than time. I’ve already used 25% of my weekly usage!
Because I work with Emi, I get a glimpse (and still cannot even fully “grok”) of how someone who lives on the edge of technology approaches work in 2026.
– it has replaced 100% of my search-like queries on chatgpt / claude
– it has replaced 100% of my Hermes usage & automations
– it now runs 100% of my Cursor cloud agents, reviews PRs, merges for me
It also…
I’m slower than I’d like to be on the uptake of the tools. I explained this feeling 6 months ago.
I like watching people like Nat use AI because they are plugged into the right layer of abstraction. The layer of recursion where every action is coupled with instructions to learn from the action so next time the action is improved. Infinite loop until you find a limit of perfection that would satisfy Zeno himself.
In contrast, when I use AI, I feel like I’m living during the debut of the automobile and thinking, “Wow, I could drive that to the granary to buy food for my horse.”
I’m going to repost this again:
– Napkin math somewhere around 6B people (~75% of the population) have barely come…
The first issue I think is around recency and tier of use. I think a lot of people tried the free tier of ChatGPT somewhere last year and allowed it to inform their views on AI a little too much. This is
Andrej is telling you that:
The gap in shared understanding of LLM capability is *widening*. It’s now less “two groups of people speaking past each other” and more a sharp funnel.
I took the liberty of making his block of text easier on your eyes:

Look at the .2% number. 20 mm people. That’s less than the number of millionaires in the US alone.
The .2% scaled down to the U.S. is ~700k people.
A bit less than the population of SF. About the same number of Americans who suffer a stroke each year. Or the number of electricians in the US. Joe Walsh has 4x that many monthly listeners on Spotify. A regular season NBA game has twice as many viewers.
I don’t know about the investing part of all this because I’m not convinced this isn’t a wildly deflationary technology, but from the point of view of people’s understanding of change, we are still very early.
But let’s get back to the basics that matter. Consumerism!
Emi told me on Monday he used Grokbot to research and order a TV from Costco. Before the TV shipped, the bot found the same TV at Sam’s Club for $400 less, on its own. It asked him whether he wanted to cancel the Costco order and buy from Sam’s. With his approval, it took care of everything, including the payment.
We spend a lot of time and mental overhead routing things around. Acceleration comes with a lot of unknowns, but I think a major part of any optimistic scenario is having more time to focus on what is irreplaceable about your vocation and the relationships you spend so much time doing logistics to enjoy.













