toolcall() ← all concepts

// agents

Grok Bot vs a scheduled Claude: one thing new.

SpaceXAI's Grok Bot has been in beta since August 11. It comes with Cursor's paid plans, from $20 a month, and pitches "AI teammates" you message instead of building routines. A scheduled Claude task comes with the $20 Claude Pro plan. We read both vendors' own docs side by side to answer one question: what can Grok Bot do that a scheduled Claude can't? This is a comparison of their documentation, not a hands-on test. Checked 2026-10-02, written for how Claude works after its October 6 change.

// the verdict, and the sentence that decides it

One thing new, as of 2026-10-03. Grok Bot keeps a browser signed in to your accounts on its own cloud computer, so a browser job you show it can rerun while your laptop is shut. Running with the laptop shut is not the new part: a scheduled Claude does that too (below). What Claude can't do with your computer off is drive a browser: "Claude driving a browser as part of a task still needs the desktop app open." SpaceXAI's docs:

Bots learn workflows from demonstration. Walk a Bot through a multi-step path once, and it can save the path as a skill and rerun it on a schedule.
Does Grok Bot keep working when my laptop is closed? Yes. Work runs on the cloud computer. Closing the app, your laptop, or your phone doesn't stop a background turn or a routine.

Learning by demonstration on its own is not new. Anthropic's Claude in Chrome page, for every paid plan including Pro:

In the classic side panel, you can teach Claude a workflow by recording the steps yourself, and Claude learns to repeat them.

You can schedule those recorded shortcuts too (recording is in the classic side panel; if yours opens as a Cowork session, switch back to record). But they run in your own Chrome: Claude "keeps working even when you switch tabs (as long as Chrome is open)". And after October 6, Anthropic still says "Claude driving a browser as part of a task still needs the desktop app open." So the gap is where the taught job runs. Like OpenAI's dots, Grok Bot has a computer of its own in the cloud, which "can sign in and work across apps, tools, and websites, including platforms with no clean API or MCP".

Two caveats from SpaceXAI itself: "Teach-by-demonstration may be enabled gradually", and "A site may still block automation, require a new login, present a CAPTCHA, or require human confirmation."

The pitch vs the same post

Grok Bot's launch post sells it against routines:

Other AI tools may ask you to set up and build workflows and routines first. With Grok Bot, simply message a Bot to take on a task and it gets it done.

A few paragraphs down, under "Show a Bot how it's done", the same post says:

It watches the steps and remembers how you like the work done. It saves your workflow as a routine, takes your corrections, and runs it on its own next time

The docs agree: "A routine tells one Bot when to run a workflow—on a schedule or, where supported, after an event." A Bot "can own up to 50 routines". The fair reading is that Grok Bot lets you start by chatting and builds the routine for you. It still runs routines.

If you just use the app: a weekday report is a schedule

Grok Bot's own routine example:

Every weekday at 8:00 AM, run the Daily customer-risk skill against the current account list. Post a linked watch list in this conversation.

SpaceXAI already sells that job without the Bot. Its Automations post: "Schedules run once, daily, weekdays, weekly, monthly, or yearly … a morning brief at 8:00 before the day starts", and "Scheduled automations are available to everyone; email triggers are included with SuperGrok."

Claude does it too. Anthropic: "Scheduled tasks are available on all paid plans (Pro, Max, Team, Enterprise)", on a cadence of "hourly, daily, weekly, on weekdays, or manually". From October 6, "Your scheduled tasks move to the cloud too" and "Scheduled tasks run with no device online."

If you write code: one computer, every Bot

Grok Bot's FAQ is plain about the shared machine:

Every Bot on your account uses one persistent cloud computer. They share its files, browser sessions, and logins so they can hand work off. The computer is assigned per user, not per Bot. Do not use separate Bots as a security boundary.

So a "sales Bot" and a "debugging Bot" see the same logins. Between users, SpaceXAI says, "isolation is strict". Bots can also "independently message each other" and work in group chats. Claude has a version of that in Claude Code's agent teams, where "Teammates message each other directly", though agent teams are "experimental and disabled by default".

Claude Code routines run as cloud sessions: "Routines execute on Anthropic-managed cloud infrastructure … so they keep working when your laptop is closed", and "Each run creates a new session alongside your other sessions", each in its own VM. Any script can start one:

API: trigger on demand by sending an HTTP POST to a per-routine endpoint with a bearer token

Grok Bot's docs list events through Cursor integrations, "such as a Slack message or a GitHub notification". We found no per-Bot endpoint for your own scripts in those docs. Routines are on Pro and up and are in research preview.

What would change this verdict

If Claude's browser moves to the cloud, so a recorded or browser job can run with your computer off, the one thing is gone and Grok Bot is a scheduled prompt with a friendlier front end. If Anthropic drops workflow recording from Claude in Chrome, then teaching by demo becomes a second thing Grok Bot does that Claude doesn't. Watch that one: recording lives in Claude in Chrome's classic side panel only. Anthropic's page, read 2026-10-02: "On Max and Team plans, the side panel runs as a Claude Cowork session, and this is rolling out to Pro plans", and "Recording isn't available when the side panel runs as a Cowork session." For now you can "switch back at any time" to the classic panel to record. If that switch goes away, so does Claude's tick in the demo row.

Going the other way: if your work lives in websites with no connector and has to happen while you're away, a computer that keeps its logins is worth having. If it lives in Gmail, Drive, Slack or GitHub on a schedule, a $20 Claude already does it. More on what makes something an agent: agents.

Sources: SpaceXAI, "Introducing Grok Bot" (x.ai/news/introducing-grok-bot, Aug 11, 2026), "Automations in Grok" (x.ai/news/grok-automations, Jul 16, 2026), and the Grok Bot docs "Grok Bot", "Skills and routines" and "Frequently asked questions" (docs.x.ai/grok-bot/…). Cursor, "Pricing" (cursor.com/pricing) and "Plans and billing" (cursor.com/help/grok-bot/plans). Anthropic, "Get started with Claude in Chrome" (support.claude.com 12012173), "Schedule recurring tasks in Claude Cowork" (13854387), "Use Claude Cowork on web, desktop, and mobile" (15520349), claude.com/pricing, and Claude Code docs "Automate work with routines" (code.claude.com/docs/en/web-scheduled-tasks) and "Orchestrate teams of Claude Code sessions" (code.claude.com/docs/en/agent-teams). All checked 2026-10-02. Grok, Cursor, Claude and Anthropic are trademarks of their owners; this page is not affiliated with them.

One concept a week. Free.

The deeper, copy-paste version of each ToolCall short — in your inbox.

// total: 0.00 · spam: void · unsubscribe: one click