Grok Bot 0.78.1: Enterprise Controls, Team Vaults, and Browser Updates

James Turner

Welcome to Grok Bot Release Notes. Brought to you by Jellypod AI. Last time we talked about the shopping carousels in Grok Bot 0.78.1. Today we're pivoting to the other half of that same release, the part aimed at teams and enterprises. Version 0.78.1 was released October 27, 2026, and it also includes 0.78.0.

James Turner

Let's start with the team dashboard, because this is where a manager actually governs Bots. On the dashboard, a section called Bot computers now groups setup scripts, setup files, and team secrets together. And there's one Security and compliance card that holds the computer controls. So instead of hunting across screens, the things that define how a Bot's computer gets built and locked down sit in one place.

James Turner

Then there's an Enterprise setting, Terminate Inactive Computers. With it on, a computer counts as inactive after 30 days without a message to any of its Bots. That's the official wording. It's a housekeeping control, and I'd read it as a way to stop forgotten computers from lingering. That part is my interpretation, not something the notes spell out.

James Turner

Sharing got tighter too. In the Share dialog, Who has access now lists your team and organization, and a Team Bot can be limited to Only you. If your team limits sharing, the share controls say Only team admins can share Bots. In the Library, Team Bot rows show a Pin button on hover, and a pinned row keeps its pin visible. The admin page also now says Shared Bots, with Manage Shared Bots and Create Bot.

James Turner

Now the piece I think matters most. Managers can add logins to a Team Bot's own Vault. You go to Configure, then Tools, and the Bot signs in with those logins for the team. So a manager sets up the credential once, and the Bot does the sign in on behalf of the team. The notes don't describe exactly how secrets are shielded in chat, so I won't claim more than that. But it pairs with the Vault work from the previous release, where the Bot's own Vault holds logins and you approve purchases.

James Turner

Background routines got smarter about missing access. When a Team Bot routine needs one of your connectors, it asks in the routine's Slack thread and tags you. Rather than just stalling, it pulls the right person in. And in Slack, people whose account isn't linked now learn that some features are limited, and how to link it, including in threads the Bot follows.

James Turner

Next, how the Bot behaves out on the web. The Bot's browser now types one character at a time and moves the mouse on every website it fills in. The notes just say that. They don't say why. My guess is it makes the browsing look more like a person, but treat that as speculation.

James Turner

When the Bot lands on sign in pages for Cloudflare, Coinbase, Gusto, YouTube, Railway, Google Ads, Meta Ads, or TikTok for Business, it offers that connector. That's a nudge toward the cleaner, connected route. And there's a fix for routing: with Route traffic through this computer on, Settings says when the computer is asleep and that routing reconnects when it wakes. Also, pages no longer fail right away when only another host on them is refused.

James Turner

A few workspace fixes you'll feel daily. Copy on a reply keeps headings, lists, and links when you paste into Slack, Gmail, Docs, or Notion, and copied selections paste as markdown. Gmail drafts the Bot writes in plain text open in rich text, so they read well on a phone and send without hard line breaks. Clicking a webhook routine opens its details, including the webhook URL.

James Turner

And one safety fix. When the Bot's computer has been refusing saves, Reset and Recover keep the current disk instead of restoring an older backup. Also, Bots using the built-in code review tools act with your access and never approve your own pull request.

James Turner

So how do you use this? If you manage a team, open the dashboard and check the Security and compliance card, then look at the Vault under Configure and Tools. Set sharing rules deliberately, and if you're on Enterprise, decide whether the 30 day inactive rule fits you. That's the episode. See you next time.