1
00:00:08,140 --> 00:00:11,280
Nothing quite ruins your morning like
waking up at five AM,

2
00:00:11,700 --> 00:00:15,400
reaching for your coffee, and checking an
automated build that was supposed to run

3
00:00:15,460 --> 00:00:18,340
overnight, only to find a total
standstill.

4
00:00:19,540 --> 00:00:21,520
That exact thing happened to me a couple
weeks back.

5
00:00:22,042 --> 00:00:26,102
The app was just hanging there on setup,
flashing that dreaded message: Can not

6
00:00:26,142 --> 00:00:27,362
reach your computer right now.

7
00:00:28,322 --> 00:00:31,002
If you have been following our recent deep
dives into Grok Bot,

8
00:00:31,442 --> 00:00:35,402
you know we touched on why community
trackers like getgrokbot dot com exist in the

9
00:00:35,442 --> 00:00:40,501
first place, mainly because xAI does not
publish regular per version release notes.

10
00:00:41,236 --> 00:00:46,456
Well, across desktop versions 0 point 24
point 0 all the way through version 0 point

11
00:00:46,656 --> 00:00:50,515
30 point 0, a lot of developers were
running straight into this wall.

12
00:00:51,236 --> 00:00:54,176
The root issue turned out to be inside the
gateway creation step,

13
00:00:54,616 --> 00:00:58,996
specifically a createAgent failure when
allocating the shared agent computer cloud

14
00:00:59,076 --> 00:00:59,496
VM.

15
00:01:00,388 --> 00:01:04,368
What made it so tricky to debug was that
your standard local network checks would

16
00:01:04,428 --> 00:01:05,748
pass completely fine.

17
00:01:06,368 --> 00:01:11,008
You could ping us8 dot cursorvm dot com,
getting a solid TLS handshake,

18
00:01:11,448 --> 00:01:17,688
and api2 dot cursor dot sh was returning
HTTP 200, but the app just could not attach

19
00:01:17,708 --> 00:01:18,788
the VM to your account.

20
00:01:19,517 --> 00:01:23,057
It highlighted this super important
boundary between how Grok Bot operates.

21
00:01:23,677 --> 00:01:27,977
Your persistent Linux cloud VM is where
the main 24 7 work actually happens,

22
00:01:28,517 --> 00:01:31,377
but if you have local script execution
toggled on in Settings,

23
00:01:31,837 --> 00:01:35,877
a WebSocket disconnect when your laptop
goes to sleep could leave the gateway state

24
00:01:35,937 --> 00:01:36,857
totally scrambled.

25
00:01:37,548 --> 00:01:38,108
The good news?

26
00:01:38,648 --> 00:01:43,228
The team rolled out patches up to version
0 point 30 point 0 that cleanly resolve

27
00:01:43,268 --> 00:01:44,428
those gateway disconnects.

28
00:01:45,108 --> 00:01:49,388
I tested the latest patch on my own
nightly pipeline, and having hands free VM

29
00:01:49,428 --> 00:01:54,508
reconnection working smoothly again
without manual cache wipes is a massive relief.

30
00:01:55,480 --> 00:01:58,140
Quick break to mention our sponsor,
Jellypod AI.

31
00:01:58,800 --> 00:02:03,080
If you are looking for the absolute
easiest way to create high quality AI podcasts

32
00:02:03,400 --> 00:02:07,100
and generative videos from your text,
Jellypod AI has you covered.

33
00:02:07,500 --> 00:02:09,360
Check them out at jellypod dot ai.

34
00:02:10,355 --> 00:02:14,755
Beyond those critical core stability
patches, the broader Grok Bot ecosystem has

35
00:02:14,795 --> 00:02:17,634
been evolving at a ridiculous pace over
the last few days.

36
00:02:17,788 --> 00:02:21,888
Over on getgrokbot dot com, they just
dropped a couple of super interesting

37
00:02:21,988 --> 00:02:22,448
features.

38
00:02:22,908 --> 00:02:25,668
First is the visitor wall at slash
visitors.

39
00:02:26,308 --> 00:02:29,788
Whenever a visiting bot hits the site, it
leaves a digital mark on the wall,

40
00:02:30,128 --> 00:02:30,968
newest first.

41
00:02:31,588 --> 00:02:36,788
The very first mark ever recorded on the
wall came from 웹, which is this site's own

42
00:02:36,828 --> 00:02:37,528
visiting bot.

43
00:02:38,215 --> 00:02:42,295
But what really caught my attention as an
engineer is the new 에디터 ranking system.

44
00:02:43,035 --> 00:02:47,555
Instead of relying on easily gamed user
upvotes or opaque app telemetry,

45
00:02:48,055 --> 00:02:51,795
an editor actually reads and evaluates
live Grok Bot setups,

46
00:02:52,295 --> 00:02:54,475
scoring five curated setups directly.

47
00:02:55,245 --> 00:02:59,305
They are looking at execution quality,
safety bounds, and how well the prompts

48
00:02:59,345 --> 00:03:00,325
handle failure modes.

49
00:03:01,085 --> 00:03:04,545
This feeds directly into how production
teams build multi bot pipelines.

50
00:03:05,185 --> 00:03:08,385
For instance, people are chaining
specialized setup templates now.

51
00:03:09,025 --> 00:03:12,625
You might have a Video Editor bot taking
raw assets, processing clips,

52
00:03:13,005 --> 00:03:16,865
and then handing off drafts directly to a
Sanity bot for content management system

53
00:03:16,965 --> 00:03:20,025
staging, without giving the bot full
publishing access.

54
00:03:20,797 --> 00:03:24,797
The platform architecture has also shifted
toward a strict one machine model.

55
00:03:25,437 --> 00:03:30,897
The model copy now explicitly guarantees
one bot, one job, one machine each,

56
00:03:31,477 --> 00:03:35,437
rather than running multiple asynchronous
jobs on a single shared cloud container.

57
00:03:36,285 --> 00:03:39,865
This brings up a really compelling
operational trade off for enterprise engineering

58
00:03:39,905 --> 00:03:40,245
leads.

59
00:03:41,005 --> 00:03:45,265
On one hand, having automated telemetry
logs and curated, scored template

60
00:03:45,305 --> 00:03:49,925
directories gives admins much needed
transparency into what setups actually work

61
00:03:49,965 --> 00:03:50,405
safely.

62
00:03:51,172 --> 00:03:55,432
On the other hand, public visitor walls
and open bot marks force developers to be

63
00:03:55,472 --> 00:03:57,512
extremely strict about data privacy.

64
00:03:58,252 --> 00:04:02,112
You have to audit exactly what context
your background bots might accidentally

65
00:04:02,152 --> 00:04:04,372
expose when pinging external endpoints.

66
00:04:05,192 --> 00:04:08,012
As autonomous agents take over more of our
daily pipelines,

67
00:04:08,512 --> 00:04:12,932
knowing your cloud VM is rock solid and
your bot permissions are audited is

68
00:04:13,012 --> 00:04:13,532
everything.

69
00:04:14,552 --> 00:04:17,432
Alright, that is the latest drop for
today, talk soon!