Grok Bot 0.78.1 Under the Hood: Key Updates and Critical Reliability Reports

0:08 Welcome to Grok Bot Release Notes, brought to you by Jellypod AI. Last time we covered the shopping carousels and subscription templates in 0.78.1. Today I'm skipping all of that and going into the engine room of the same release. Some quiet changes there matter more than the carousels if you run Bots with real accounts and real work.

0:27 And then there's a reliability story from the community that you should hear before you update anything important. Start with one line in the official changelog.

0:35Quote The Bot's browser types one character at a time and moves the mouse on every

0:40 website it fills in. End quote. That's it, one bullet. So what does it mean? Before, a form fill could look like a value just appearing in a field. Now it behaves more like a person: keystroke by keystroke, with the pointer travelling across the page. The changelog doesn't say why. My read, and this is interpretation, not something the notes claim, is that it's meant to look and behave more like normal human input.

1:06 I'd treat any promise about getting past bot detection or captchas as unconfirmed. The practical effect you can count on is probably this. Form fills on sites with fiddly inputs could behave differently, and might take a little longer. So if a routine of yours fills in long forms, watch the first few runs.

1:24 Next, connector handoffs. On the sign in pages for Cloudflare, Coinbase, Gusto, YouTube, Railway, Google Ads, Meta Ads, and TikTok for Business, the Bot now offers that service's connector. So instead of the Bot grinding through a login in its browser, it can point you at the proper connector. There's a matching fix too.

1:44 Connect cards for Railway, Square, TradingView, and Google Ads now appear only on those services' own pages. And when a connector needs a permission its connection can't request, the Bot now says reconnecting won't help. That one saves you a loop of pointless reconnects. Then there's cloud agents. Bots can now start cloud agents in a custom mode you name, and keep replying to them in it.

2:07 The notes say nothing more than that. So I won't invent what modes you should build. What I'll say is that if you already split work between a planning mode and an execution mode, naming one explicitly and having the Bot stay in it is the thing to test. For teams, the notable one is this. Managers can add logins to a Team Bot's own Vault, in Configure, under Tools, and the Bot signs in with them for the team.

2:31 So the credential lives in the Bot's Vault, and the team uses the Bot rather than passing a password around. There's also a new Share detail: Who has access lists your team and organization, and a Team Bot can be limited to Only you. And one enterprise fix. With Terminate Inactive Computers on, a computer counts as inactive after 30 days without a message to any of its Bots.

2:54 Now the guardrails and small fixes that I'd actually screenshot. Bots using the built in code review tools act with your access and never approve your own pull request. That's a clean rule. The Bot reviews as you, and it can't rubber stamp your own work. Gmail drafts the Bot writes in plain text now open in rich text, so they read well on a phone and send without hard line breaks.

3:17 Bot emails retry once when the mail server connection times out. And routines made in a new Bot's first chat run in your time zone instead of UTC. If you ever had a morning routine firing at a strange hour, that's your fix. Two more that people will miss. Two saves to the same memory at once no longer overwrite each other.

3:37 And Spend totals the Bot records now use the right currency, so other currencies aren't counted as US dollars. If you track spend, old totals could have been off. Now the part I'd want to know before updating. The official notes are tidy. The community picture is messier. On the Cursor forum, a user posted a bug report against Grok Bot 0.78.1, build dated 2026 10 28 at 02:34 UTC, stable channel, on macOS.

4:08 Their Bot's computer had been unresponsive since about 17:00 UTC on October 28, for over 20 hours when they wrote it up. The symptoms are specific. The Computer tab says Can't connect to the screen, and Retry doesn't help. Any shell command the Bot runs hangs for 14 minutes, which is an 840 second timeout, or reports the computer is still starting up.

4:33 They clicked Update Bot's Computer several times, installed the latest app update, and fully quit and reopened the app. Nothing changed. And Recover Grok Bot's Computer never appeared. They also said that before this, the kernel log showed many virtual machine fork events and virtio balloon errors, on October 27 and 28.

4:54 Here's what we can and can't say. This is one user's report. They had a support ticket open, number T I six two zero three six, escalated to a human, with a queue they described as three to four days. They also point to another forum topic, number 176526, about a computer stuck in a partial state after freezing, same version, starting a few hours earlier.

5:17 The forum's related topics list more freeze reports, including one about a computer unreachable since October 21, one frozen since October 23, and one unresponsive since October 26. Some of those are dated before 0.78.1 shipped. So I can't tell you 0.78.1 caused this. What I can tell you is the freezes are being reported around this release, and some reports say the symptoms persisted after Update and Reset.

5:44 That Reset detail matters. The reporter chose not to press Reset, because the computer holds local databases and project work. And that's the choice I'd think hardest about too. One of the related topic titles says support told that user not to reset. So my practical advice, and this is my advice, not official guidance: if your Bot's computer freezes, don't treat Reset as the first move.

6:07 Try the Update and an app restart, check whether Recover is offered, and if it isn't, get a support ticket in early. There's one fix in the 0.78.1 notes that touches this. When the Bot's computer has been refusing saves, Reset and Recover now keep the current disk instead of restoring an older backup.

6:25 Good news in principle, because it means those actions shouldn't roll you back. But the notes don't claim to fix the freezes, and the reports say Recover sometimes isn't offered at all. So don't lean on it as a safety net. Some habits that cost nothing. Anything important on the Bot's computer, like databases and project files, should exist somewhere else too.

6:46 Keep your long running routines pointed at work you can rerun. And if you run a Team Bot, with the new Vault logins, think about who gets hurt if that computer is down for a day or more. So the takeaway. Under the hood, 0.78.1 makes the Bot behave more like a person at the keyboard, offers connectors where you'd otherwise hand over a login, and adds sensible rules like never approving your own pull request.

7:12 But if your Bot's computer is doing real work for you, watch the forum and the official changelog for follow ups before you change anything. That's it for today. Thanks for listening.