1
00:00:08,057 --> 00:00:12,757
So, um, last time we were looking at those
public share links and specialized

2
00:00:12,817 --> 00:00:15,137
templates like Jess and Video Editor,
right?

3
00:00:16,197 --> 00:00:20,397
But, okay, here is the thing that
completely flips the script this week.

4
00:00:21,177 --> 00:00:21,757
Access.

5
00:00:22,338 --> 00:00:26,558
It, it, it used to be pretty gated, but
xAI just opened the floodgates.

6
00:00:27,077 --> 00:00:31,097
If you are on SuperGrok Plus, SuperGrok
Heavy, Cursor Pro+,

7
00:00:31,477 --> 00:00:37,117
Cursor Ultra, or Cursor Teams, you now get
Grok Bot built right into your plan.

8
00:00:37,197 --> 00:00:41,537
And, er, if you visit the site, you will
see that August thirty first header update

9
00:00:41,577 --> 00:00:45,557
that streamlines everything into Grok Bot
101, the changelog,

10
00:00:45,617 --> 00:00:46,577
and official Docs.

11
00:00:47,217 --> 00:00:51,337
It feels like we moved from a closed
experiment to a full on public deployment

12
00:00:51,397 --> 00:00:52,377
practically overnight.

13
00:00:52,577 --> 00:00:57,057
Now, what really blew me away when I
opened the latest build was local execution.

14
00:00:57,697 --> 00:01:02,017
For the longest time, your bots lived
exclusively on cloud Linux virtual machines.

15
00:01:02,557 --> 00:01:04,677
Which is great for offloading work, sure,
but...

16
00:01:05,357 --> 00:01:10,017
um, what if you are working on a
sensitive, local codebase or custom internal

17
00:01:10,138 --> 00:01:10,558
scripts?

18
00:01:11,317 --> 00:01:15,437
Well, the official download page now
serves a native Windows build right alongside

19
00:01:15,477 --> 00:01:16,138
macOS.

20
00:01:16,798 --> 00:01:20,798
Community version numbers bumped from zero
point twenty three point zero to zero

21
00:01:20,958 --> 00:01:22,197
point twenty four point zero.

22
00:01:22,997 --> 00:01:24,717
And there is this toggle in Settings.

23
00:01:25,237 --> 00:01:29,138
You can literally route long running tasks
to run locally on your own machine's

24
00:01:29,197 --> 00:01:30,978
hardware instead of in the cloud.

25
00:01:31,319 --> 00:01:34,439
I, I, I actually tested this on my own
Windows setup yesterday.

26
00:01:35,039 --> 00:01:38,619
Running a local terminal script while
having cloud sub agents coordinate in the

27
00:01:38,659 --> 00:01:39,179
background...

28
00:01:40,139 --> 00:01:41,300
man, it changes everything.

29
00:01:42,000 --> 00:01:46,180
There is zero API round trip latency when
your bot is interacting with local files,

30
00:01:46,679 --> 00:01:50,840
and you do not have to worry about pushing
proprietary code up to a remote instance

31
00:01:51,299 --> 00:01:53,699
just to parse a file or run a local build
script.

32
00:01:54,260 --> 00:01:58,459
It just executes locally, spits out the
result, and hands it back to the agent loop.

33
00:01:58,500 --> 00:02:02,740
And speaking of daily workflow fixes,
there are a few quality of life upgrades that

34
00:02:02,790 --> 00:02:04,740
dropped in the log that I have to mention.

35
00:02:04,860 --> 00:02:07,700
First, multi account plugin support.

36
00:02:07,887 --> 00:02:12,100
If you manage multiple client accounts or
separate GitHub profiles,

37
00:02:12,140 --> 00:02:16,100
you can now run multiple sets of
credentials on a single plugin instance without

38
00:02:16,151 --> 00:02:17,780
constantly logging in and out.

39
00:02:17,924 --> 00:02:22,420
Then you have Command D voice dictation
for dictating instructions on the fly,

40
00:02:22,540 --> 00:02:27,380
and grouped mobile notifications where
every bot gets its own distinct app icon on

41
00:02:27,428 --> 00:02:28,100
your phone.

42
00:02:28,240 --> 00:02:32,900
You can glance at your screen, see exactly
which bot is pinging you for approval,

43
00:02:32,940 --> 00:02:35,860
and tap to confirm without opening a
massive dashboard.

44
00:02:35,974 --> 00:02:39,674
That brings us to enterprise governance,
which is where things get really serious

45
00:02:39,754 --> 00:02:41,194
for actual team production.

46
00:02:42,194 --> 00:02:46,234
xAI rolled out a two week free trial for
Grok Bot for Enterprise.

47
00:02:46,734 --> 00:02:51,654
Admin dashboards, strict network access
boundaries, and full audit logging.

48
00:02:52,194 --> 00:02:57,334
Every single bot runs in its own isolated
environment, so there is zero risk of data

49
00:02:57,375 --> 00:03:00,254
bleeding between departments or cross
tenant leaks.

50
00:03:00,774 --> 00:03:04,754
If you work in a corporate environment
where legal or compliance usually shuts down

51
00:03:04,834 --> 00:03:09,235
autonomous AI agents, this is the
governance framework they have been waiting for.

52
00:03:09,333 --> 00:03:14,213
And if you use X for research or community
tracking, the native X connector update

53
00:03:14,293 --> 00:03:15,493
is massive.

54
00:03:15,621 --> 00:03:20,373
When you link your X account inside Grok
Bot, it automatically sets up a developer

55
00:03:20,413 --> 00:03:25,573
account for you, and paid subscribers get
free X API credits right out of the gate.

56
00:03:25,713 --> 00:03:29,973
You do not need third party scrapers or
messy custom web scripts anymore.

57
00:03:30,085 --> 00:03:34,133
Your bot can natively read timelines,
track brand mentions,

58
00:03:34,173 --> 00:03:37,013
and search posts directly using official
endpoints.

59
00:03:37,000 --> 00:03:41,400
Think about how this actually looks in a
real multi bot production setup.

60
00:03:41,620 --> 00:03:45,320
Say you set up an X monitoring bot in a
shared group chat.

61
00:03:45,560 --> 00:03:50,200
It watches live posts for trending
industry topics or breaking news.

62
00:03:50,420 --> 00:03:55,720
The moment it detects a spike, it
summarizes the key quotes and hands the task

63
00:03:55,773 --> 00:03:59,721
directly over to a Video Editor template
bot in that same group chat.

64
00:03:59,920 --> 00:04:05,160
The Video Editor bot takes those topics,
generates a video draft or asset,

65
00:04:05,180 --> 00:04:08,360
and posts a preview card right in your
transcript for you to review.

66
00:04:08,653 --> 00:04:13,080
No human context switching, no copy
pasting links between apps.

67
00:04:13,224 --> 00:04:17,160
Just two specialized agents collaborating
on a single timeline.

68
00:04:17,167 --> 00:04:21,327
Before we wrap up, today's episode is
brought to you by Jellypod AI,

69
00:04:21,367 --> 00:04:25,247
the easiest platform to create AI podcasts
and generative videos.

70
00:04:25,434 --> 00:04:30,127
If you want to turn your raw notes,
technical docs, or changelogs into engaging

71
00:04:30,194 --> 00:04:34,847
audio and video content in minutes, head
over to Jellypod AI and check it out.

72
00:04:34,932 --> 00:04:39,313
When you look at the whole picture, from
expanded plan access and local Windows

73
00:04:39,372 --> 00:04:45,433
execution to enterprise security and free
API tiers, Grok Bot is rapidly shifting

74
00:04:45,472 --> 00:04:49,472
from an experimental toy into essential
daily infrastructure.

75
00:04:50,272 --> 00:04:51,412
That is all for this quick take.

76
00:04:51,773 --> 00:04:54,192
Thanks for listening, and I will catch you
in the next one!