1 00:00:08,320 --> 00:00:09,980 Welcome to Grok Bot Release Notes. 2 00:00:10,200 --> 00:00:11,760 Brought to you by Jellypod AI. 3 00:00:12,480 --> 00:00:16,820 Last time we talked about the shopping carousels in Grok Bot 0.78.1. 4 00:00:17,400 --> 00:00:19,960 Today we're pivoting to the other half of that same release, 5 00:00:20,300 --> 00:00:22,240 the part aimed at teams and enterprises. 6 00:00:23,040 --> 00:00:28,800 Version 0.78.1 was released October 27, 2026, and it also includes 7 00:00:29,020 --> 00:00:30,080 0.78.0. 8 00:00:31,132 --> 00:00:34,851 Let's start with the team dashboard, because this is where a manager actually 9 00:00:34,892 --> 00:00:35,752 governs Bots. 10 00:00:36,432 --> 00:00:40,432 On the dashboard, a section called Bot computers now groups setup scripts, 11 00:00:40,752 --> 00:00:43,312 setup files, and team secrets together. 12 00:00:43,792 --> 00:00:47,252 And there's one Security and compliance card that holds the computer controls. 13 00:00:47,872 --> 00:00:51,732 So instead of hunting across screens, the things that define how a Bot's computer 14 00:00:51,772 --> 00:00:54,392 gets built and locked down sit in one place. 15 00:00:55,090 --> 00:00:58,450 Then there's an Enterprise setting, Terminate Inactive Computers. 16 00:00:58,930 --> 00:01:03,170 With it on, a computer counts as inactive after 30 days without a message to any of 17 00:01:03,210 --> 00:01:03,770 its Bots. 18 00:01:04,070 --> 00:01:05,170 That's the official wording. 19 00:01:05,690 --> 00:01:09,610 It's a housekeeping control, and I'd read it as a way to stop forgotten computers 20 00:01:09,630 --> 00:01:10,250 from lingering. 21 00:01:10,790 --> 00:01:13,650 That part is my interpretation, not something the notes spell out. 22 00:01:14,382 --> 00:01:15,742 Sharing got tighter too. 23 00:01:16,162 --> 00:01:20,822 In the Share dialog, Who has access now lists your team and organization, 24 00:01:21,282 --> 00:01:23,942 and a Team Bot can be limited to Only you. 25 00:01:24,602 --> 00:01:29,542 If your team limits sharing, the share controls say Only team admins can share Bots. 26 00:01:30,142 --> 00:01:35,522 In the Library, Team Bot rows show a Pin button on hover, and a pinned row keeps its 27 00:01:35,582 --> 00:01:36,262 pin visible. 28 00:01:36,962 --> 00:01:42,222 The admin page also now says Shared Bots, with Manage Shared Bots and Create Bot. 29 00:01:42,860 --> 00:01:44,880 Now the piece I think matters most. 30 00:01:45,480 --> 00:01:48,700 Managers can add logins to a Team Bot's own Vault. 31 00:01:49,260 --> 00:01:54,200 You go to Configure, then Tools, and the Bot signs in with those logins for the 32 00:01:54,260 --> 00:01:54,580 team. 33 00:01:55,220 --> 00:01:59,480 So a manager sets up the credential once, and the Bot does the sign in on behalf of 34 00:01:59,520 --> 00:01:59,940 the team. 35 00:02:00,800 --> 00:02:03,940 The notes don't describe exactly how secrets are shielded in chat, 36 00:02:04,060 --> 00:02:05,400 so I won't claim more than that. 37 00:02:05,880 --> 00:02:08,400 But it pairs with the Vault work from the previous release, 38 00:02:08,600 --> 00:02:12,340 where the Bot's own Vault holds logins and you approve purchases. 39 00:02:13,008 --> 00:02:15,888 Background routines got smarter about missing access. 40 00:02:16,408 --> 00:02:20,808 When a Team Bot routine needs one of your connectors, it asks in the routine's Slack 41 00:02:20,848 --> 00:02:21,988 thread and tags you. 42 00:02:22,428 --> 00:02:25,028 Rather than just stalling, it pulls the right person in. 43 00:02:25,668 --> 00:02:29,648 And in Slack, people whose account isn't linked now learn that some features are 44 00:02:29,708 --> 00:02:33,048 limited, and how to link it, including in threads the Bot follows. 45 00:02:33,695 --> 00:02:35,775 Next, how the Bot behaves out on the web. 46 00:02:36,575 --> 00:02:40,555 The Bot's browser now types one character at a time and moves the mouse on every 47 00:02:40,595 --> 00:02:41,655 website it fills in. 48 00:02:42,255 --> 00:02:43,195 The notes just say that. 49 00:02:43,235 --> 00:02:44,175 They don't say why. 50 00:02:44,775 --> 00:02:48,195 My guess is it makes the browsing look more like a person, but treat that as 51 00:02:48,255 --> 00:02:48,875 speculation. 52 00:02:49,570 --> 00:02:53,269 When the Bot lands on sign in pages for Cloudflare, Coinbase, 53 00:02:53,450 --> 00:02:58,530 Gusto, YouTube, Railway, Google Ads, Meta Ads, or TikTok for Business, 54 00:02:58,970 --> 00:02:59,970 it offers that connector. 55 00:03:00,470 --> 00:03:02,990 That's a nudge toward the cleaner, connected route. 56 00:03:03,690 --> 00:03:07,350 And there's a fix for routing: with Route traffic through this computer on, 57 00:03:07,610 --> 00:03:11,670 Settings says when the computer is asleep and that routing reconnects when it wakes. 58 00:03:12,330 --> 00:03:16,310 Also, pages no longer fail right away when only another host on them is refused. 59 00:03:16,845 --> 00:03:19,105 A few workspace fixes you'll feel daily. 60 00:03:19,645 --> 00:03:23,745 Copy on a reply keeps headings, lists, and links when you paste into Slack, 61 00:03:24,085 --> 00:03:28,305 Gmail, Docs, or Notion, and copied selections paste as markdown. 62 00:03:28,985 --> 00:03:32,225 Gmail drafts the Bot writes in plain text open in rich text, 63 00:03:32,485 --> 00:03:35,165 so they read well on a phone and send without hard line breaks. 64 00:03:35,885 --> 00:03:39,765 Clicking a webhook routine opens its details, including the webhook URL. 65 00:03:40,467 --> 00:03:41,747 And one safety fix. 66 00:03:42,287 --> 00:03:46,727 When the Bot's computer has been refusing saves, Reset and Recover keep the current 67 00:03:46,787 --> 00:03:48,887 disk instead of restoring an older backup. 68 00:03:49,507 --> 00:03:54,047 Also, Bots using the built-in code review tools act with your access and never 69 00:03:54,107 --> 00:03:55,507 approve your own pull request. 70 00:03:56,297 --> 00:03:57,657 So how do you use this? 71 00:03:58,217 --> 00:04:02,717 If you manage a team, open the dashboard and check the Security and compliance card, 72 00:04:03,257 --> 00:04:06,177 then look at the Vault under Configure and Tools. 73 00:04:06,757 --> 00:04:09,657 Set sharing rules deliberately, and if you're on Enterprise, 74 00:04:10,057 --> 00:04:12,597 decide whether the 30 day inactive rule fits you. 75 00:04:13,237 --> 00:04:13,937 That's the episode. 76 00:04:14,277 --> 00:04:14,777 See you next time.