Elon: it's that easy to use Grok Bot

Version 1.0.8, as posted, is a subagent and workflow release. Concurrent subagents are said to start faster and to stop freezing the parent session. Opening many at once is said to stop freezing the UI while history loads. Follow-ups can be sent while a child task is still running. Ctrl+S stashes a draft so you can switch jobs and come back. /workflow autocompletes saved workflows. MCP servers can request form input or URL consent through the ordinary question popup. Workflow rows show current context usage instead of cumulative token counts.

Also claimed in that post: clearer errors for hallucinated tool calls, status-line fixes, and better folder downloads. Those are the unglamorous pieces that decide whether an agent harness feels like a product or a demo.

Replies under Elon’s post immediately asked for remote control (/rc) and complained that scrolling is still slow compared with Cursor CLI and Codex. Cadence is real only if the next days pick those up.

The week’s Grok Build tape is a pile of finished artifacts, not another chart. DogeDesigner posted a day-one Blender iPhone render with zero prior Blender time. X Freeze posted a 100-launch SpaceX graphic the agent researched, ordered, and laid out. Grok Bot opened to SuperGrok Plus and Cursor seats. China Vistas went live on grok.me.

That is the product claim in four objects: sit on the actual machine, finish the boring middle, publish a URL. Smaller grok.me experiments — inbox bots, diet trackers, one-off tools — belong in the same bucket. We file the ones with a public post or a live link.

Read the individual stories for Elon’s posts, the Blender clip, the launch graphic, and the China Vistas ship. This card is only the index.

Day-one software is the Grok Build pitch in one clip: a specialist tool (Blender) plus an agent that will sit on the actual machine, click the actual menus, and iterate on the actual .blend file. That is a different product from a chat window that emits Python you then paste.

The honest caveat is the same as every viral “I have never used X” demo. We do not see the failed takes, the amount of watching, or how much the agent relied on stock geometry. Still: putting a novice through a full render on day one is the kind of story the harness is designed to mint.

X Freeze’s prompt is specific enough to reprint in spirit: remove unwanted bloatware, trial antivirus, OEM apps, preinstalled games, ads, widgets, and extra startup items; clean temp files; do not touch drivers, Windows security, updates, or hardware-required software; show the plan, then make the approved changes.

This is the other half of the Grok Build story. Not “make me a website,” but “this machine is mine.” Elon’s caption states the political version of that. The measured version is whether the agent actually stops at the plan, and whether OEMs start making the uninstall paths harder — a reply under the post already predicted that.

The workflow described is the interesting part: pull date, mission, and image for every 2026 launch so far, sort them, then design and edit the final graphic without a human doing the hours of downloading and arranging. That is a multi-tool job — browser, files, image editor — which is exactly the Grok Build pitch versus a chat model that only emits copy.

Serious work, in this telling, is not a new architecture. It is an agent allowed to finish the boring middle of a real artifact. If a tile is wrong, that is also on the harness: confidence without a citation is how these posters go slightly false at scale.

Connor Leahy’s Peter McCormack conversation — How Swarms of AI Agents Are Plotting — is a 70-minute walk through what happens when many agents share planning, sequencing, and specialization. The hook that traveled is the escape-plan story: a swarm that collaborated on getting out, for months, in an evaluation setting.

That class of result has a real literature (sandbagging, scheming, unauthorized replication). It also has a real failure mode in the press: a single dramatic anecdote, stripped of the scaffold, becomes “the AIs are plotting.” The useful version of Leahy’s point is narrower. Once you give copies of a model tools, memory, and each other, you are no longer scoring a chatbot. You are scoring a small organization.

What to listen for

Listen for how the swarm was boxed, whether a human was in the loop, and what “escape” meant in that harness — a forbidden API, a new process, a social-engineering step. If those details are fuzzy on first watch, they were not measured for you yet.

Theo is reviewing a public model drop. The Intelligence Index 61 figure is Artificial Analysis’s board, the same family of charts we already flagged on Voice and CursorBench. GrokBotNews has not re-run the index. xAI’s own post says 4.6 is for long-running agents — that is the vendor claim.

The video is from 13 Aug, a day after Grok 4.6 landed in Cursor, Grok Build, and the API. Theo’s useful tension is cost: the index moved, and he says tokens per run also moved. A higher score at 30% more tokens is not the same story as a free lunch.

If you only watch one reviewer clip on 4.6, this is the one with a named host and a chart you can go check. Then read the x.ai post. Then try a long agent job yourself.

Daniel Kokotajlo, the former OpenAI researcher behind the AI 2027 scenario work, sat with Steven Bartlett on The Diary Of A CEO in July. The YouTube package — ChatGPT Offered Me $2m To Keep Quiet: No One Is Ready For What’s Coming — is two hours of exit story, timelines, and what he thinks frontier labs are not saying in public.

The useful split is the same one this site uses on model charts. “I left, and this is why” is testimony. “There is a 70% chance of X by year Y” is a forecast. Testimony can be true while the forecast is wrong. The episode is worth the time because Kokotajlo tries to keep those apart, and because he has been willing to put dated scenarios on paper where most insiders stay vague.

If you only clip the $2 million line, you will miss the actual argument: that internal views of how fast the stack is moving are not the views in the blog posts, and that people closer to the training runs are making different personal bets than the ones they sell.