1
00:00:08,240 --> 00:00:14,000
Last time, I told you the official Grok
Bot changelog stopped at 0.70.2,

2
00:00:14,440 --> 00:00:20,020
and that 0.71.2 only existed as forum
chatter about Windows 11 tool problems.

3
00:00:20,520 --> 00:00:22,340
Well, that gap is closed.

4
00:00:22,880 --> 00:00:28,480
xAI published the official 0.71.2 notes on
October 14, 2026,

5
00:00:28,920 --> 00:00:33,480
and they roll in 0.71.0 and 0.71.1 too.

6
00:00:34,060 --> 00:00:36,260
This episode is brought to you by Jellypod
AI.

7
00:00:36,862 --> 00:00:41,942
The headline xAI chose is smarter
notifications and larger file attachments.

8
00:00:42,362 --> 00:00:44,802
But the detail I find most useful is tiny.

9
00:00:45,262 --> 00:00:48,222
Bots can now send from a tagged form of
their email address,

10
00:00:48,402 --> 00:00:50,082
like name plus shop at.

11
00:00:50,582 --> 00:00:54,242
And a routine tied to that tag runs only
for mail sent to that tag.

12
00:00:54,827 --> 00:00:55,787
Think about what that does.

13
00:00:56,407 --> 00:01:00,007
A Bot can claim its own address as of
0.70.2.

14
00:01:00,607 --> 00:01:03,487
Until now, everything landing there was
one stream.

15
00:01:04,087 --> 00:01:08,607
With tags, you could give one Bot a tag
for receipts and another for invoices,

16
00:01:09,007 --> 00:01:11,487
and each routine fires only for its own
mail.

17
00:01:12,207 --> 00:01:14,627
Say you set up a finance plus receipts
address.

18
00:01:15,067 --> 00:01:18,127
Vendors send PDFs there, and only the
receipts routine wakes up.

19
00:01:18,747 --> 00:01:23,047
That's my example, not xAI's, but it's
exactly the segregation the feature allows.

20
00:01:23,822 --> 00:01:27,282
Now the numbers, because this release is
full of limits that moved.

21
00:01:27,802 --> 00:01:31,722
You can attach files up to 250 MB, and
videos up to 1 GB.

22
00:01:32,302 --> 00:01:34,822
If a video is too large for the Bot to
watch, it tells you.

23
00:01:35,642 --> 00:01:38,802
One message can now carry up to 20
attachments instead of 6,

24
00:01:39,242 --> 00:01:42,762
and there's a notice telling you how many
weren't added once you pass the 200 MB

25
00:01:42,802 --> 00:01:43,122
total.

26
00:01:43,862 --> 00:01:45,162
Those distinct figures matter.

27
00:01:45,702 --> 00:01:50,922
250 MB is per file, 1 GB is for video, and
200 MB is the total for a message.

28
00:01:51,642 --> 00:01:55,542
And the notes say the file size and
desktop notification changes both require Grok

29
00:01:55,642 --> 00:01:59,682
Bot 0.70.2 or later, so update first.

30
00:02:00,402 --> 00:02:02,262
The second big number is skills.

31
00:02:02,722 --> 00:02:07,022
Bots can use up to 200 skills from your
installed plugins, instead of 24.

32
00:02:07,662 --> 00:02:09,522
That's a bit more than eight times the
room.

33
00:02:10,222 --> 00:02:15,062
The practical point is in the note itself:
skills from plugins you add are no longer

34
00:02:15,102 --> 00:02:15,622
left out.

35
00:02:16,242 --> 00:02:19,222
If you installed a plugin and your Bot
acted like it didn't exist,

36
00:02:19,502 --> 00:02:21,542
a cap like this could have been part of
the story.

37
00:02:22,162 --> 00:02:24,262
I'd go check any plugin you installed
recently.

38
00:02:24,987 --> 00:02:26,707
Notifications got smarter too.

39
00:02:27,047 --> 00:02:31,547
While you're using Grok Bot on a Mac or
Windows PC, replies and questions notify you

40
00:02:31,587 --> 00:02:33,047
there, instead of on your phone.

41
00:02:33,567 --> 00:02:37,007
If you've ever had a Bot buzz your pocket
while you were staring at the desktop app,

42
00:02:37,367 --> 00:02:38,087
that's the fix.

43
00:02:38,860 --> 00:02:40,360
Voice calls got more resilient.

44
00:02:40,840 --> 00:02:44,440
If a voice chat's connection drops, the
call reconnects and continues the same

45
00:02:44,500 --> 00:02:45,960
conversation instead of ending.

46
00:02:46,539 --> 00:02:49,360
And a voice call from your phone wakes the
Bot's sleeping computer,

47
00:02:49,680 --> 00:02:52,140
so the Bot can work with what you said
after the call.

48
00:02:52,780 --> 00:02:57,060
So you can ramble out a task on a walk,
hang up, and the Bot has a machine ready to

49
00:02:57,180 --> 00:02:57,400
act.

50
00:02:58,092 --> 00:03:00,452
One adjacent note, and I'll flag it as
adjacent.

51
00:03:00,972 --> 00:03:07,892
On the same day, the xAI API release notes
say grok-voice-3.0 became available for

52
00:03:08,012 --> 00:03:13,112
Speech to Speech at the same price as Grok
Voice 2.0, and the older model is

53
00:03:13,132 --> 00:03:13,652
deprecated.

54
00:03:14,171 --> 00:03:17,972
The Grok Bot notes don't say Bot calls run
on it, so I won't claim that.

55
00:03:18,292 --> 00:03:19,872
But it's a good sign for voice overall.

56
00:03:20,510 --> 00:03:24,330
Let's talk about what happens when things
go wrong, because this release is heavy on

57
00:03:24,390 --> 00:03:24,870
fixes.

58
00:03:25,510 --> 00:03:28,510
When a Bot's computer runs low on disk,
the Bot tells you once,

59
00:03:28,910 --> 00:03:31,810
names the biggest files, and deletes them
only if you agree.

60
00:03:32,370 --> 00:03:33,210
That's the right design.

61
00:03:33,690 --> 00:03:37,030
It surfaces the problem without letting an
agent clean house on its own.

62
00:03:37,755 --> 00:03:39,515
Sleep handling got a lot of attention.

63
00:03:40,015 --> 00:03:43,455
Clicking the Computer is asleep preview
now wakes it in place,

64
00:03:43,675 --> 00:03:45,275
replacing the separate Wake button.

65
00:03:45,995 --> 00:03:49,635
Grok Bot opens while the computer is still
starting, instead of sitting behind a

66
00:03:49,695 --> 00:03:51,015
full window setup screen.

67
00:03:51,735 --> 00:03:55,735
Images a Bot creates or captures, and
files from cloud agents it started,

68
00:03:56,155 --> 00:03:58,035
load in the chat while its computer is
asleep.

69
00:03:58,355 --> 00:04:01,235
So you can look at results without waking
the machine just to see them.

70
00:04:01,955 --> 00:04:05,475
And if the computer fails to wake, the Bot
now says it couldn't start,

71
00:04:05,735 --> 00:04:08,075
instead of retrying as if it were still
starting up.

72
00:04:08,675 --> 00:04:13,055
On the local side, when your computer
sleeps, Bots treat it as disconnected within

73
00:04:13,115 --> 00:04:17,215
two minutes and say so right away, instead
of waiting for commands to time out.

74
00:04:17,935 --> 00:04:22,895
After a Wi Fi, VPN, or other network
change, Bots can run tasks on your computer

75
00:04:22,935 --> 00:04:23,435
right away.

76
00:04:24,055 --> 00:04:26,575
Commands keep going through brief
connection stalls.

77
00:04:27,115 --> 00:04:30,395
And background jobs a Bot starts on your
Mac, such as a local server,

78
00:04:30,855 --> 00:04:32,715
keep running after the command returns.

79
00:04:33,435 --> 00:04:37,315
If work is meant for one of your computers
that's offline, the Bot tells you instead

80
00:04:37,355 --> 00:04:39,215
of quietly running it on another computer.

81
00:04:39,758 --> 00:04:43,858
Another good one: Stop now also ends a
Bot's background subagents.

82
00:04:44,398 --> 00:04:48,458
Their results no longer wake the Bot
afterward, and their pending approval cards

83
00:04:48,498 --> 00:04:48,998
expire.

84
00:04:49,738 --> 00:04:52,498
If you've ever hit Stop and then watched
something resurface later,

85
00:04:52,958 --> 00:04:53,958
that's what this addresses.

86
00:04:54,657 --> 00:04:59,997
For connected tools, Bots can archive,
move, delete, flag, or mark many Outlook

87
00:05:00,057 --> 00:05:03,837
messages as read or unread in one step
instead of one at a time.

88
00:05:04,577 --> 00:05:08,097
Bot searches on X with date limits,
minimum likes or reposts,

89
00:05:08,217 --> 00:05:12,237
or filters X doesn't support now return
posts instead of being rejected.

90
00:05:12,957 --> 00:05:16,857
Connector calls wait up to two minutes for
a reply, instead of timing out after one

91
00:05:16,917 --> 00:05:17,157
minute.

92
00:05:17,737 --> 00:05:21,117
And at checkout, Bots use card details or
photos you send in chat,

93
00:05:21,417 --> 00:05:24,797
asking only for missing fields or a
verification code in a Secure Form.

94
00:05:25,508 --> 00:05:26,768
Forms also get friendlier.

95
00:05:27,388 --> 00:05:31,688
A form a Bot asks you to fill in can
arrive with known fields already filled,

96
00:05:32,088 --> 00:05:33,808
and you can edit them before you submit.

97
00:05:34,408 --> 00:05:39,548
Secure Form also fills fields on more
websites, including inside embedded frames

98
00:05:39,568 --> 00:05:40,428
from other sites.

99
00:05:41,132 --> 00:05:43,432
If you run a team, there are two controls.

100
00:05:43,812 --> 00:05:48,612
Team admins can turn off Messaging between
Bots under Bot capabilities on the

101
00:05:48,672 --> 00:05:52,732
dashboard, so members' Bots can't message
or hand work to other Bots.

102
00:05:53,332 --> 00:05:57,592
And Enterprise team admins can recreate,
terminate, or delete members' Grok Bot

103
00:05:57,632 --> 00:06:02,112
computers from Manage Bot Computers on the
dashboard, or through the Admin API.

104
00:06:02,712 --> 00:06:06,372
Those are labeled Teams and Enterprise, so
they apply to those plans only.

105
00:06:07,132 --> 00:06:08,672
There's also a small account note.

106
00:06:09,192 --> 00:06:13,852
While a paid account merge is still moving
data, Settings shows Your accounts are

107
00:06:13,892 --> 00:06:17,432
being merged, with Contact Support if it
runs long.

108
00:06:18,052 --> 00:06:22,412
And merges where both accounts have files
on the Bot's computer now finish,

109
00:06:22,851 --> 00:06:27,632
keeping both sets and adding from
transferred account to clashing file names.

110
00:06:28,338 --> 00:06:29,478
So how do you use this?

111
00:06:30,178 --> 00:06:35,598
First, update to at least 0.70.2 so the
notification and attachment changes apply.

112
00:06:36,258 --> 00:06:39,718
Second, try a tagged address for one
routine, like receipts,

113
00:06:39,918 --> 00:06:42,138
and watch whether only that mail triggers
it.

114
00:06:42,798 --> 00:06:47,198
Third, if you review video, try a cut up
to 1 GB, and know the Bot will tell you if

115
00:06:47,238 --> 00:06:48,278
it's too large to watch.

116
00:06:48,938 --> 00:06:51,798
Fourth, recheck any plugin that seemed to
be missing skills.

117
00:06:52,398 --> 00:06:56,358
Last, if you manage a team, decide whether
Bots should be able to hand work to each

118
00:06:56,438 --> 00:06:56,638
other.

119
00:06:57,318 --> 00:06:58,838
That's 0.71.2.

120
00:06:59,518 --> 00:07:03,478
Not flashy, but a lot of limits moved, and
a lot of rough edges got sanded down.

121
00:07:04,438 --> 00:07:04,997
See you next time.