By Adam Moore

I Almost Canceled Cursor. Now It Runs My Bot Team.

I was ready to drop my Cursor subscription for Grok Build. Then Grok Bot showed up, and now 23 bots and a bunch of Cursor cloud agents do work for me while I'm away from the desk.

October 12, 2026

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.

Adam's Grok Bot team, organized under Eli by lane

Each bot has a lane:

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

Grok Bot team by the numbers since Aug 14, 2026

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:

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.

Read Next

More field notes

October 18, 2026

My App Said It Failed. It Didn't.

A slow AI call, a browser that gave up too early, and a handful of bots that filed the bug and got it fixed before lunch.

Read analysis

October 17, 2026

I Shipped a Work Fix From My Phone

15+ years into web dev, a new workflow still blew my mind: Grok Bot on my phone driving Claude Code on my work computer to file the ticket, make the fix, and open the PR while I was out of the office.

Read analysis

October 17, 2026

Agents Need APIs, Not Spreadsheets

My assistant bots were working out of a Google Sheet. Then one of them basically asked for a real feature. The pattern I keep landing on: give agents real APIs plus a skill doc.

Read analysis