Who Pays When Grok Bot Hires a Bot?

James Turner

So, um, if you've been reading Cursor's community forum this month, you've probably seen thread titles like, "Is Grok Bot eating at Cursor usage? I thought it had its separate usage?" And another one, "Grok Bot spend cursor usage, I can't accept it." That second one has over a thousand views. Which tells you something, right? People are, uh, rattled.

James Turner

Last episode we were deep in the 43% desktop migration hangs and the local daemon flapping. This week the fight moved. Nobody's yelling about broken cloud VM handshakes anymore. It's all billing dashboards and, and, and who got charged for what.

James Turner

Quick honesty note. I don't have the individual support tickets or the exact percentages in front of me, so I'm not going to quote numbers I can't stand behind. Here's what I can stand behind. On August 21, xAI's announcement said SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, and Cursor Teams now include Grok Bot, and everyone else gets a free trial with limited usage. So you've got two quota worlds, Cursor's and Grok Bot's, sitting right next to each other.

James Turner

Now, the resolution people are pointing to. This is background from a Cursor forum thread, not something I've watched happen myself, so weigh it accordingly. The claim is that the per model breakdown was a display problem, but there's a design catch. When Grok Bot spins up Cursor cloud agents for coding, that work is billed to your Cursor usage by design.

James Turner

Okay, so, picture it. Grok Bot is the, the architect, working off its own expense account. That's the weekly pool. But when the architect hires subcontractors to actually pour the concrete, those subcontractors swipe your personal card. Is that a perfect analogy? Hmm, no. But it makes the surprise make sense. You watched the architect's budget and forgot the subcontractors exist.

James Turner

So my take, and it's only my take, is you want a hard ceiling on on demand spend before you let any bot loose. Go look at the usage and billing settings in your Cursor dashboard and decide what the worst case is allowed to be. Because a limit you set beforehand is a lot cheaper than a limit you discover afterward.

James Turner

Quick break. This episode is brought to you by Jellypod AI, the easiest platform to create AI podcasts and generative videos.

James Turner

So, here's a wrinkle that made the billing confusion worse. Where do you even check what changed? On August 19, the community tracked changelog noted that xAI still publishes no per version release notes, which is why that page exists. And a Cursor community support engineer, Colin, said there isn't an official changelog right now, and the best place to check for updates is Grok Bot on X.

James Turner

Which brings me to the directory that changelog lives on. On August 31 it said, and I'm quoting, "Templates are only public x.ai/bot share links posted on X." Directory listings stay in the table. The changelog doesn't say why. I'd read it as a trust boundary, um, you're installing something a real author published in public, not something scraped from who knows where. But that's my reading, not theirs.

James Turner

And, uh, the site calls itself a sponsor free directory that is not an official xAI product. Worth keeping in your head.

James Turner

Now the fun part, what people are actually building. Two original listings, Sanity and Jess. Sanity is a content desk. Per the directory, it turns a brief into a paste ready draft in Sanity, and it does not publish. The changelog says it plainly, CMS drafts, no publish. Jess is an executive assistant, calendar, email, a short daily list of decisions. The listing says she doesn't send or change events without asking.

James Turner

Notice the pattern? Each one is defined by what it refuses to do. There's a template on the directory, dr eggbot, whose description literally says "explicit anti jobs, no leftover tools." I love that phrase. The job tells you what the bot can do. The anti job tells you how bad your Tuesday can get.

James Turner

Which connects to something from xAI's API release notes. On September 25 they added a request field. Quote, "You can now send safety_identifier, an opaque end user identifier assigned by your application." It lets SpaceXAI attribute a policy violation to one of your end users rather than to your API key.

James Turner

Now, the docs say end user, not agent run. So, um, how you map bots or runs onto that identifier is on you, and that part is my inference. But the idea is the same as the anti job. Shrink the blast radius. One bad actor shouldn't take the whole key down with it.

James Turner

And the same thinking shows up in the changelog on August 29. One Machine copy is now, quote, "one bot, one job, one machine each," not one job on a shared Grok cloud box. Compare that to the launch post on Cursor's forum, which says the computer is isolated to your account rather than to an individual Bot, so any login or file you put there is available to all your Bots.

James Turner

I'm not going to pretend I've migrated a setup, I haven't. But picture it. One bot is halfway through a long job in a checkout, another bot wanders in on the same box... yeah. One machine each just removes that whole category of Tuesday.

James Turner

So, back to the opening question, who pays when a bot hires a bot? You do, unless you've drawn the line first. Cap the spend, name the anti jobs, and give each bot its own room. Alright, that's it from me.