At one point I stopped using Cursor. I was doing most of my work in Grok Build, and I was honestly looking at canceling the subscription.
Then Grok Bot came out, and it runs on that same Cursor subscription. Now I'm using Cursor more than I ever did. I'm just not sitting in an editor for most of it.
The team
Grok Bot isn't one assistant for me. It's a team. I talk to one bot, Eli, and Eli runs everyone else.

Each bot has a lane:
- TXGarage: Gage handles content and X, Spur researches the weekly press car, and TXG YT watches the YouTube channel.
- Home and family: Warda has the immediate family, Ben's Coach has school, Ann has extended family, Health is my coach, and LoneRider keeps the house organized.
- Money: Bill tracks bills and spending, and Meter watches RealView costs.
- Work and code: Orbit, Scout, and Storefront cover my OrderMyGear work, Patch reviews my code, and View handles RealView engineering.
- Brand and social: Sosh, Eich, Reed, Rally, Designer, Ian, and Overheard.
Every day at 3pm the bots check in with a standup, and Eli sends me a voice recap. Routines handle the recurring stuff: email, briefings, and watches. Everything runs on one shared computer with shared memory, so a login or a file one bot sets up is there for the rest.
By the numbers

Since August 14 I've set up 23 bots and a group chat. There are 41 routines, and they've run 399 times with a 92% success rate. The bots have saved 377 memory facts and use 71 skills, 20 of them custom, across 25 connected accounts. Eli is the one I talk to most, by a lot.
Bots hand the coding to cloud agents
Here's the part that changed how I think about my Cursor subscription. When a bot needs code written, it doesn't write it on its own computer. It hands the work to a Cursor cloud agent, which works in the repo and comes back with a pull request I review.
The first time this really clicked was with Bill, my money bot. He needed a real place to track open items, not a Google Sheet. He worked it out with the other bots until we had a ticket. I pointed Grok Build at that ticket and shipped the PR, and Bill verified it once it was live.
This week I went further, on this site. I wanted to write more field notes without pasting them in by hand, so over a couple of days:
- Eich, the bot that handles my content, had a cloud agent build a drafts-only API for field notes. Bots can create and edit drafts, but publishing is still my click.
- Designer mocked up a real CMS for my admin panel, and a cloud agent built it from that handoff.
- Patch reviewed both PRs and caught real bugs, like a way a draft could get published without anyone hitting Publish.
- A third PR added image uploads to DigitalOcean Spaces, an image gallery in the editor, and cover images.
All I did was review, merge, and set up a bucket. The post you're reading started as a draft one of the bots created through that API.
It goes where I go
I use this from my phone, my iPad mini, and my desktop. Android finally got an app, and so did the iPad. A lot of my dev work now happens from the iPad mini, because the heavy lifting is happening in the cloud.
It also helps with stuff that isn't code. Last week I was reviewing a Chevy Bolt for TXGarage, and I logged my mileage, charge state, and charging costs with Bot as I drove. Bot pulled the stats together, I fed screenshots of them to Grok Build, and in about 25 minutes Grok 4.7 turned them into two graphics for the review video.
Why I kept the subscription
I didn't need another editor. I needed something that keeps working when I'm not at the desk. My Cursor subscription now pays for that: bots that know my life and my projects, plus cloud agents that do the coding while I'm doing something else.
I'm extremely bullish on this. Next level, here we come.