Grok Bot 0.68.1 Outages, the Reset Trap, and Grok 4.7

James Turner

Last episode, I was pretty happy. SpaceXAI had finally launched an official changelog for Grok Bot, and we walked through versions 0.62.0 to 0.66.0. Today, the story is about what happened after that feed went quiet. Quick note first: this episode is brought to you by Jellypod AI, the easiest platform to create AI podcasts and generative videos.

James Turner

Here's the detail that matters. As of October 7th, the official feed, both the changelog page and the RSS, still tops out at version 0.66.0, dated October 2nd. That entry introduced Main Bot, a primary Bot marked with a star that checks in proactively and coordinates your other Bots. It also fixed update downloads resuming after your computer sleeps. The community changelog at getgrokbot.com doesn't help here either. Its last update is August 31st, so it hasn't tracked desktop versions past that point.

James Turner

But the app kept moving. Community reports on the Cursor forum show desktop clients on macOS with Apple silicon, Windows, and Linux sitting on version 0.68.1. The build timestamps shown in those reports are October 6th, at 4:15 AM UTC for Linux and 4:18 AM UTC for Windows. So versions 0.67 through 0.68.1 reached production with no published release notes. I can't tell you what's in them, because nobody has published that, and I'm not going to guess.

James Turner

So how did people end up there without doing anything? This goes back to my warning last time. Version 0.65.0 made Automatic Updates on by default, so Grok Bot restarts to apply updates while you're away. You can turn it off under Settings, then Updates. If you left it on, you may have woken up on 0.68.1 and never seen a prompt.

James Turner

And that matters, because on October 7th a service degradation notice went up. The wording was: we are investigating a service degradation affecting Grok Bot's computers in certain regions. I need to be precise about the sourcing. The symptoms I'm about to describe come from user reports on the Cursor forum, tied to 0.68.1. The notice itself doesn't name a version as the cause, so treat the link between the two as a pattern in reports, not a confirmed diagnosis.

James Turner

The symptoms are rough. First, the Computer tab hangs on Starting desktop, then says it can't reach your Bot's screen. Second, the shell goes dead. In one report, every shell command hangs and times out after about 840 seconds at spawn, even a simple echo. Some file reads still work, but terminal execution doesn't. Third, deleting an affected Bot can fail with a message that says Couldn't delete, check your connection and try again.

James Turner

Then there's the reset trap. People click Update Grok Bot's Computer under Settings, then Updates, or they click Reset, and it stalls. The message says Reset couldn't finish, Grok Bot's computer may be in a partial or incomplete state, retry to run the reset again. Click it repeatedly, and the buttons gray out, and reports say the cloud computer ends up unbootable.

James Turner

That leads to the most important guidance in this episode. Support responses cited in the forum threads advise users to stop clicking Reset or Update once a computer fails. The reasoning given is that repeated attempts break the container image and block automated recovery, and that you need an escalation for a server side reprovision. So if you're stuck, open a support ticket and describe the symptoms. Don't hammer the button.

James Turner

Now, the good news. Chat still works. Reports say pure reasoning and text generation keep running normally. The failure is isolated to the cloud computer and desktop side, the place where your Bot browses, runs shell commands, and clicks around.

James Turner

There's also an outbound traffic problem. Users report that since October 1st, traffic from the cloud computer that isn't HTTPS is timing out. That includes MySQL, SSH, IMAP and SMTP mail, and FTP. If your Bot depends on any of those, there's a workaround that already exists. Back in version 0.50.0, Grok Bot added a setting called Route egress through this desktop. Turn it on, and your Bot's web traffic goes through your own computer instead of the cloud. I'd treat that as a community suggested workaround for this problem, not an official fix, but it's a real setting you can try today.

James Turner

One more item, and it's a security report, so take it as unverified. Community bug reports say that in 0.68.1, browser snapshots have captured passwords entered through the Secure Form. That's the form window introduced in 0.64.0 for logins. Until there's an official word, I'd think twice about typing sensitive credentials into a Bot session that's behaving strangely. If you use 1Password with Grok Bot, that's another path to consider.

James Turner

So what's the practical playbook? If your Bot is healthy, think about whether you want Automatic Updates on right now. That's your call, and it's a tradeoff, because the setting also means you get fixes without lifting a finger. If your Bot is broken, stop resetting, gather the symptoms, and file a ticket. And keep an eye on the official feed for the next entry.

James Turner

Now the model side, because it does affect Grok Bot. Grok 4.7 launched on September 21st. SpaceXAI says it has a 500k context window, and reasoning effort options of low, medium, high, and xhigh. The line that matters for us is this: they say they trained Grok 4.7 to natively understand the Grok Bot harness, which should make it better at conversational tasks and general knowledge work. They also say it's better at verifying its own work and managing longer context, and better at creating documents and presentations. Those are the company's claims, not independent tests.

James Turner

On the API, the old Grok Voice Transcribe 1.0 reached end of life on October 2nd. Requests are routed to Grok Voice Transcribe 2.0 at the same price, with higher accuracy. If you build on the API, you don't need to change anything. The sources don't say how Grok Bot itself uses that model, so I won't claim a connection.

James Turner

Let me end on what people are building, because this is why the stability matters. Harper, an insurance company, built a Team Bot in 24 hours to find customers with lapsed policies. Their CEO, Dakotah Rice, says they used to check every customer by hand through three platforms, pull balance details, and send personalized emails. He says the Bot saved customers over $120,000 across hundreds of policies.

James Turner

Amplitude's Head of Marketing, Angela Ferrante, says they're building toward Team Bots for every marketing function. And on the tooling side, SEOAgent 1.0 now supports Grok Bot alongside Claude Code, Cursor, and Codex, for things like website audits.

James Turner

Real teams are betting workflows on these cloud computers. So the thing to watch is simple: does the official changelog catch up to 0.68.1, and does that degradation notice get resolved? When it does, we'll cover it.