WEBVTT

1
00:00:01.550 --> 00:00:03.760
Hello, my name is Cliff.

2
00:00:03.970 --> 00:00:06.600
I'm joined here with Martin.
We are going to be, well,

3
00:00:06.650 --> 00:00:09.020
Martin is going to be
running the 101 today.

4
00:00:09.530 --> 00:00:13.420
I will be moderating the chat,
so please post your questions,

5
00:00:13.850 --> 00:00:15.240
and I'll try to respond to them.

6
00:00:15.470 --> 00:00:18.180
As many as I can, I probably won't
be able to get to all of them,

7
00:00:18.250 --> 00:00:22.090
and I will surface what is most
important to Martin so we can cover them

8
00:00:22.130 --> 00:00:24.800
live for everyone in the
audience where relevant.

9
00:00:25.550 --> 00:00:28.600
I work on the AI deployment
team here at SpaceXAI,

10
00:00:28.810 --> 00:00:31.160
so I work with tons of customers,

11
00:00:31.550 --> 00:00:33.810
to help them get the most
value out of the platform,

12
00:00:33.850 --> 00:00:36.700
everything from workshops to
workflows, things just like this.

13
00:00:36.810 --> 00:00:39.720
And I'm joined by Martin,
who I will pass it off to,

14
00:00:39.790 --> 00:00:43.050
who is a field engineer here at SpaceXAI.
Thanks for coming, everyone.

15
00:00:44.550 --> 00:00:45.900
Hi, nice to meet you all.

16
00:00:46.190 --> 00:00:47.620
Thank you, Cliff for the introduction.

17
00:00:48.130 --> 00:00:51.330
By the way, Cliff is awesome. So be
kind to him in the Q&A over there.

18
00:00:51.370 --> 00:00:53.940
I know he'll be locked in
and slammed the questions.

19
00:00:54.390 --> 00:00:58.760
But nice to meet you all. I'm a field
engineer here on the SpaceXAI side.

20
00:00:59.030 --> 00:01:00.190
I originally came from Cursor.

21
00:01:00.230 --> 00:01:04.610
And so now as we expanded the
actual ecosystem of products

22
00:01:04.650 --> 00:01:07.590
that we help educate and
give the best tips and tricks

23
00:01:07.630 --> 00:01:12.770
that now includes the Grok main,
Grok APIs, and now also Grok Bot.

24
00:01:12.810 --> 00:01:15.780
So everything Grok related, all fun there.

25
00:01:16.070 --> 00:01:21.070
But more so extremely excited to
hop into a 101 session on our latest

26
00:01:21.110 --> 00:01:23.920
product, which is now in
the general knowledge work.

27
00:01:24.370 --> 00:01:30.190
And so before really kicking off here,
I would love to know if you could put a.

28
00:01:30.230 --> 00:01:36.550
rating in the chat on how well
you know Grok Bot where zero is

29
00:01:36.590 --> 00:01:40.510
this is like your first time actually
seeing or hearing what it's going to do

30
00:01:40.550 --> 00:01:46.690
to five you already have an AI workforce
that is already doing some crazy

31
00:01:46.730 --> 00:01:48.970
things behind the scenes with Grok Bot.

32
00:01:49.010 --> 00:01:50.970
So if you could put a zero
to five rating in the chat,

33
00:01:51.010 --> 00:01:55.220
that would be awesome to see there just
to get a gauge of the audience we have.

34
00:01:56.820 --> 00:02:00.400
Also, Cliff, I am not
able to see the Zoom chat,

35
00:02:00.440 --> 00:02:03.340
so feel free to let me know
what numbers we got here.

36
00:02:03.380 --> 00:02:06.150
I'm seeing the full spectrum of ratings.

37
00:02:06.800 --> 00:02:09.910
A lot of zeros, a lot of folks above five,

38
00:02:11.120 --> 00:02:12.950
really every number.

39
00:02:14.740 --> 00:02:16.690
Any 1,000 in there?

40
00:02:17.300 --> 00:02:19.290
Nobody's put 1,000 yet. Okay.

41
00:02:20.480 --> 00:02:25.420
If you are at 1,000, hopefully there is
something you can take away in this 101.

42
00:02:25.460 --> 00:02:31.680
And as well, we have a 201 coming up with
Joseph, which amazing flowed engineer.

43
00:02:31.720 --> 00:02:32.960
Then you can learn a lot more stuff there.

44
00:02:33.000 --> 00:02:36.550
But this would be more or less
the basics of how to use Grok Bot.

45
00:02:36.820 --> 00:02:37.780
Some context on me.

46
00:02:37.820 --> 00:02:41.920
So it was a previous software
engineer used Cursor from 2023,

47
00:02:41.960 --> 00:02:45.290
that IDE agents window to like, you know,

48
00:02:45.600 --> 00:02:48.730
2025 of launching cloud
agents during team meetings.

49
00:02:49.000 --> 00:02:51.610
I hope my old manager isn't
in this workshop hearing that.

50
00:02:51.840 --> 00:02:55.420
But now more so, really excited to
showcase this because it is our.

51
00:02:55.460 --> 00:02:58.530
first tool that is for
everyone across the board.

52
00:02:59.100 --> 00:03:03.090
So even all the segments,
I'm sure you saw the Grok Bot Galaxy,

53
00:03:03.700 --> 00:03:05.990
if you're going to go to market,
if you are in product,

54
00:03:06.220 --> 00:03:07.220
if you're in engineering,

55
00:03:07.740 --> 00:03:11.690
or even just a hobbyist and you want
to be able to have a simple interface,

56
00:03:11.740 --> 00:03:15.070
but really leverage power
of AI to do real work.

57
00:03:15.420 --> 00:03:19.230
This is the workshop for you.
So I'm glad that you joined us today.

58
00:03:21.280 --> 00:03:25.120
So just for some housekeeping,
this is being recorded.

59
00:03:25.160 --> 00:03:27.490
And if you have any questions,

60
00:03:27.960 --> 00:03:30.410
I would recommend you
don't put them in the chat,

61
00:03:30.640 --> 00:03:32.350
but you put them in the Q&A section,

62
00:03:32.600 --> 00:03:36.220
just so Cliff will be able to actually
manage and answer whatever questions

63
00:03:36.260 --> 00:03:38.460
may come up as well too.

64
00:03:38.500 --> 00:03:40.190
And we can showcase in the agenda.

65
00:03:41.500 --> 00:03:46.250
We can have like sections of if questions
arise with common themes and ideas.

66
00:03:46.880 --> 00:03:49.500
Cliff can go off mute and then
let me know. We can handle that.

67
00:03:49.540 --> 00:03:52.470
And so it could be beneficial for
everyone to hear that across the board.

68
00:03:53.960 --> 00:03:54.960
Awesome.

69
00:03:55.780 --> 00:03:57.710
Just a level set on the agenda,

70
00:03:58.740 --> 00:04:02.820
really want to showcase the history
in the last couple of years of how AI

71
00:04:02.860 --> 00:04:04.650
has transcended, how we use it today,

72
00:04:05.300 --> 00:04:07.880
to why we even brought
Grok Bot into market.

73
00:04:07.920 --> 00:04:10.370
And I think there's a really
fascinating story there.

74
00:04:10.740 --> 00:04:15.530
And then we'll showcase Grok Bot
inaction, so showcasing the platform.

75
00:04:15.880 --> 00:04:19.460
And then we'll sprinkle every bits
and pieces of potential questions

76
00:04:19.500 --> 00:04:20.680
if there is room.

77
00:04:20.720 --> 00:04:25.120
But more or less, we'll have 10
minutes at the end just for Q&A.

78
00:04:25.160 --> 00:04:28.120
if there's anything that arises
throughout the entire workshop

79
00:04:28.160 --> 00:04:29.930
that you have a question on.

80
00:04:32.350 --> 00:04:33.350
Great.

81
00:04:33.830 --> 00:04:35.710
And so before now going into Grok Bot,

82
00:04:35.750 --> 00:04:39.730
I think talking about the history and
the way that we've actually brought

83
00:04:39.770 --> 00:04:41.680
this product into the market is important.

84
00:04:42.210 --> 00:04:46.910
And so let's start off with where
we had AI a couple of years ago.

85
00:04:46.950 --> 00:04:51.820
So around the 2023 time, this is where
the concept of chatbots came into play.

86
00:04:52.130 --> 00:04:55.280
And I remember distinctly, I was in
my living room, I was on the couch,

87
00:04:55.390 --> 00:04:56.500
asking Chad GPT.

88
00:04:57.150 --> 00:04:59.090
you know, like what is
the meaning of life?

89
00:04:59.130 --> 00:05:00.870
What is like the weather tomorrow?

90
00:05:00.910 --> 00:05:04.690
I'm just asking crazy questions to see
what exactly can come back to me with

91
00:05:04.730 --> 00:05:08.170
and extremely surprised at how
conversational it actually was.

92
00:05:08.210 --> 00:05:12.410
And moving more into a year where
connectors and MCPs came into play

93
00:05:12.450 --> 00:05:17.900
where we're able now to give
AI a specific, you know,

94
00:05:18.250 --> 00:05:19.630
action or task.

95
00:05:19.670 --> 00:05:25.750
And we can connect a Figma MCP to now
work in a turn-based style to complete

96
00:05:25.790 --> 00:05:30.090
a slide deck, whether that is in a
couple of hours and actually go back

97
00:05:30.130 --> 00:05:33.480
and forth with it to do that. Now,

98
00:05:33.810 --> 00:05:38.370
where we've seen Grok Bot come into
play is being able to actually take

99
00:05:38.410 --> 00:05:40.400
that execution off of your laptop,

100
00:05:40.790 --> 00:05:44.400
move a bit away from that turn-based
language of talking with your AI,

101
00:05:44.770 --> 00:05:48.500
and now actually being able to
have a colleague, have a teammate,

102
00:05:48.750 --> 00:05:52.530
that you're able to trust a job and
have it actually delegate this outcome

103
00:05:52.570 --> 00:05:53.060
to it.

104
00:05:53.070 --> 00:05:56.920
So Grok Bot is something that before
we even launch it into production,

105
00:05:57.370 --> 00:06:01.240
I believe last month, Cliff let
me know if I'm off base there,

106
00:06:01.530 --> 00:06:05.990
but we were using Grok Bot internally
across our entire work from engineering

107
00:06:06.030 --> 00:06:07.030
to go to market.

108
00:06:07.230 --> 00:06:12.810
And so like we're talking to specific
Grok Bots like one conversation for

109
00:06:12.850 --> 00:06:14.780
months on end and is
able to actually learn.

110
00:06:14.950 --> 00:06:16.480
So when we delegate an outcome,

111
00:06:16.790 --> 00:06:19.360
because we essentially onboarded
it as if it was a new hire,

112
00:06:19.670 --> 00:06:23.960
it was as easy as being able
to now just pass future work.

113
00:06:24.550 --> 00:06:29.530
And so moving forward up as maturity
curve now is where we see at SpaceXAI,

114
00:06:29.570 --> 00:06:31.930
the evolution of how AI works,

115
00:06:31.970 --> 00:06:35.540
where no longer we're working with
one teammate to delegate work to.

116
00:06:36.050 --> 00:06:38.990
But now we have a company
or cohort of teammates.

117
00:06:39.030 --> 00:06:41.270
So I view it less as agents warms.

118
00:06:41.310 --> 00:06:45.250
I view it more as like an entire
AI workforce that is able to act on

119
00:06:45.290 --> 00:06:49.610
your behalf so that ideas that you
might not have thought were possible

120
00:06:49.650 --> 00:06:53.030
before are now meant possible
because Grok Bot exists.

121
00:06:53.070 --> 00:06:57.460
and because we actually have teammates
that are able to talk to each other.

122
00:06:58.990 --> 00:07:00.970
And so this is now moving into, right,

123
00:07:01.010 --> 00:07:03.700
like Grok Bot and where
we see in today's market,

124
00:07:04.710 --> 00:07:08.650
this is a first ever true AI teammate
and colleague that you were able

125
00:07:08.690 --> 00:07:10.040
to delegate work to.

126
00:07:10.750 --> 00:07:14.300
And so if you notice
on the screenshot here,

127
00:07:14.810 --> 00:07:18.360
it should feel familiar and
simple as if it was iMessage.

128
00:07:18.550 --> 00:07:22.890
The main premise was that we wanted
this tool to be extremely easy,

129
00:07:22.930 --> 00:07:26.630
to be onboarded onto regardless
of if you are in a profession,

130
00:07:26.670 --> 00:07:27.550
if you're a hobbyist,

131
00:07:27.590 --> 00:07:31.050
if you know, you're even a parent and
you want to see cooking techniques

132
00:07:31.090 --> 00:07:33.800
and recipes to use for tonight's meal.

133
00:07:33.970 --> 00:07:36.930
This should be as simple
as texting a colleague,

134
00:07:36.970 --> 00:07:39.620
right, where you have all your
bots on the left-hand side.

135
00:07:39.910 --> 00:07:41.340
We have the sales outbound.

136
00:07:41.610 --> 00:07:42.860
We have the inbox manager.

137
00:07:43.550 --> 00:07:46.730
And this is where we'll
briefly touch on the 101,

138
00:07:46.770 --> 00:07:51.170
but even have a chief of staff that is
able to talk to these different bots

139
00:07:51.210 --> 00:07:52.220
on our behalf.

140
00:07:53.970 --> 00:07:55.950
In the middle section,
going from left to right here,

141
00:07:55.990 --> 00:07:59.230
is just the single point of conversation
where we are able to talk to

142
00:07:59.270 --> 00:08:01.860
our teammate. So I know in today's tools,

143
00:08:02.610 --> 00:08:06.150
you have to create a new conversation,
hit that plus button every single time.

144
00:08:06.190 --> 00:08:07.190
You have a new task.

145
00:08:07.730 --> 00:08:10.630
That experience feels a little bit
less cohesive when we think about

146
00:08:10.670 --> 00:08:14.290
actually how we talk to teammates and
colleagues and how we distribute work

147
00:08:14.330 --> 00:08:15.330
to others.

148
00:08:15.850 --> 00:08:20.070
This is now able to have that
memory as we talk with it over time

149
00:08:20.110 --> 00:08:25.030
and is able to already now do work
and even without prompting it.

150
00:08:25.070 --> 00:08:29.610
So if you realize there is a little
snippet here is called created the

151
00:08:29.650 --> 00:08:31.040
sales outbound routine.

152
00:08:31.770 --> 00:08:33.190
This is where on the right hand side.

153
00:08:33.230 --> 00:08:36.350
We can see how our bot is actually
operating asynchronously even without

154
00:08:36.390 --> 00:08:37.400
us prompting it.

155
00:08:37.790 --> 00:08:42.860
So name, description, but also the actual
routines of every morning at 8 a.m.

156
00:08:43.170 --> 00:08:46.720
If this sales outbound bot is doing PG,

157
00:08:47.190 --> 00:08:51.170
automatically send to everyone in
our queue those drafted emails of how

158
00:08:51.210 --> 00:08:52.480
I actually taught you to do that.

159
00:08:54.380 --> 00:08:57.870
And so in short here, right,
Grok Bot is that true first teammate.

160
00:08:58.380 --> 00:09:03.550
And I think the two product decisions
that we create with the Grok Bot,

161
00:09:04.060 --> 00:09:06.470
first is being able to
have persistent memory.

162
00:09:06.900 --> 00:09:10.740
So actually being able to talk
with this bot until the end of time

163
00:09:10.780 --> 00:09:12.750
and it knows exactly how it operates.

164
00:09:13.000 --> 00:09:14.280
It knows the type of work that we do.

165
00:09:14.320 --> 00:09:17.940
It's handling a very
specific role for that job.

166
00:09:17.980 --> 00:09:19.970
you are typically used to doing,

167
00:09:20.320 --> 00:09:23.060
whether it is a rote or mundane
work or even meaningful work

168
00:09:23.100 --> 00:09:24.550
that you want to pass it off to.

169
00:09:24.960 --> 00:09:30.290
But secondly now, the fact that we
actually give each Grok Bot a computer.

170
00:09:31.140 --> 00:09:33.810
So if you think about
the current tools today,

171
00:09:34.000 --> 00:09:36.300
when it does, the execution
does it on your laptop.

172
00:09:36.340 --> 00:09:37.910
So if I'm creating a slide deck,

173
00:09:38.180 --> 00:09:41.130
the moment I actually want to go
out to lunch, close my laptop,

174
00:09:41.640 --> 00:09:45.220
all of that just gets absolutely
paused, when in reality,

175
00:09:45.260 --> 00:09:49.850
if we actually have a real 24-7,
ASync agent or ASync teammate,

176
00:09:50.480 --> 00:09:55.370
it has its own computer that is able
to actually do work off of our laptops,

177
00:09:56.100 --> 00:10:00.340
or sorry, out of our laptops, and is
now able to do long-running work there.

178
00:10:00.380 --> 00:10:02.590
And even more important,
because it has a own computer,

179
00:10:02.960 --> 00:10:05.910
it's able to actually use the internet
very similar to how we use it.

180
00:10:06.080 --> 00:10:08.440
So you'll realize that there are
a lot of MCPs and connections

181
00:10:08.480 --> 00:10:12.390
that we have out of the box, which
will showcase in the marketplace,

182
00:10:12.980 --> 00:10:16.900
whether that is pulling at
Lassian tickets or documents

183
00:10:16.940 --> 00:10:19.790
or whether it's pulling
conversations from Slack.

184
00:10:20.060 --> 00:10:24.180
We can also just have our bot,
go to United Airlines.com,

185
00:10:24.220 --> 00:10:28.160
and actually just book a flight travel
for us because why would United have

186
00:10:28.200 --> 00:10:30.370
an MCP or an API for that matter?

187
00:10:30.680 --> 00:10:32.990
If it does, I would be
extremely interested.

188
00:10:33.260 --> 00:10:35.950
But for everything else,
even internal dashboards,

189
00:10:36.280 --> 00:10:39.560
you're able to have RockBot just point
at it and do the work specifically

190
00:10:39.600 --> 00:10:40.960
how you already would.

191
00:10:41.000 --> 00:10:42.500
And as a little teaser,

192
00:10:42.540 --> 00:10:46.900
we can even teach the bot how to
use a computer with a teach a task.

193
00:10:46.940 --> 00:10:53.040
feature but that would be more later
coming up take a little pause here i

194
00:10:53.080 --> 00:10:57.860
am curious cliff i know you're locked
in with messaging there the q-nas is

195
00:10:57.900 --> 00:11:02.260
there a bot in mind that
you've used in the past

196
00:11:02.300 --> 00:11:05.980
that you've wouldn't say aha moment but
like you is extremely useful in your

197
00:11:06.020 --> 00:11:07.020
day to day

198
00:11:07.900 --> 00:11:12.260
yeah i would say um so i work like
i mentioned i work with a lot of

199
00:11:12.300 --> 00:11:17.940
customers on helping to like deploy
SpaceXAI products into their company

200
00:11:17.980 --> 00:11:21.560
to help their employees work.

201
00:11:21.600 --> 00:11:24.570
And so what's hard is finding,

202
00:11:24.720 --> 00:11:29.050
you know, opportunities and
risks and things proactively.

203
00:11:29.360 --> 00:11:33.600
And I have this bot that I named
driver that's like my customer driver,

204
00:11:33.640 --> 00:11:36.930
if that makes sense, like the driver of
opportunities and getting things done.

205
00:11:37.080 --> 00:11:39.960
And it helps me to remember things
that I've dropped on the floor

206
00:11:40.000 --> 00:11:44.880
or surface opportunities for like
where a customer is having a problem

207
00:11:44.920 --> 00:11:48.000
and we have something or a
tool or a feature whatever

208
00:11:48.040 --> 00:11:51.260
that could help them things
like that the type of work

209
00:11:51.300 --> 00:11:54.840
that you know you could spend all day
Googling and looking on you know what

210
00:11:54.880 --> 00:11:57.600
are they posting on LinkedIn or their
blogs or whatever and you could never

211
00:11:57.640 --> 00:12:03.180
find everything and this bot is that
proactive like opportunity searching

212
00:12:03.220 --> 00:12:08.280
bot to help me do that with my customers
so it finds finds things on my behalf

213
00:12:08.320 --> 00:12:11.540
I think that's that's my favorite
type of use case for Grok Bot is

214
00:12:11.580 --> 00:12:13.150
like proactive monitoring

215
00:12:14.180 --> 00:12:16.460
not just doing work you already do,

216
00:12:16.500 --> 00:12:18.790
doing things you couldn't have
done before without a helper.

217
00:12:19.680 --> 00:12:22.570
That's awesome. Thanks for
sharing that. Yeah, we even have,

218
00:12:22.660 --> 00:12:24.940
I've seen, I'm not sure if it's
rolled out to everyone just yet,

219
00:12:24.980 --> 00:12:29.420
but we have a primary Grok Bot where
if in this interface you have the

220
00:12:29.460 --> 00:12:32.890
sales outbound, chief of staff,
inbox manager, we now, like,

221
00:12:33.420 --> 00:12:34.810
from a Grok Bot experience,

222
00:12:34.900 --> 00:12:39.220
we make one their primary and
it's able to actually keep tabs

223
00:12:39.260 --> 00:12:41.850
and everything across the board of what
we're doing. And to your point cliff,

224
00:12:42.280 --> 00:12:46.590
I remember rescheduling a calendar
invite with one of my teammates,

225
00:12:46.760 --> 00:12:48.270
but didn't actually reschedule it.

226
00:12:48.360 --> 00:12:51.260
So I woke up to Grok Bot
already scheduling that for me

227
00:12:51.300 --> 00:12:53.480
because it knew that
I was going to forget.

228
00:12:53.520 --> 00:12:55.360
And it was in fact correct.

229
00:12:55.400 --> 00:12:57.790
I did forget. But I love the name driver.

230
00:12:58.240 --> 00:13:02.840
I wish I actually named my Grok Bots
in a way that makes me remember what

231
00:13:02.880 --> 00:13:06.620
they actually do. I name it very
different names and even cute name.

232
00:13:06.660 --> 00:13:11.400
So what I want to showcase with the
two principles of the persistent memory

233
00:13:11.440 --> 00:13:16.470
and computer use, I want to showcase
with a story with a bot called Bobo.

234
00:13:17.480 --> 00:13:20.530
So Stilmore to Cliff,
I also work and go-to-market.

235
00:13:20.860 --> 00:13:26.010
So I have all of these workbots that
actually help me prep for all of my calls.

236
00:13:26.280 --> 00:13:28.950
It gives me a rundowns with all
the accounts, even account usages,

237
00:13:29.060 --> 00:13:30.060
all things like that.

238
00:13:30.640 --> 00:13:34.610
But Bobo is actually far and
away from all of my workbots.

239
00:13:34.900 --> 00:13:38.500
It's actually my number
one go-to personal bot,

240
00:13:38.540 --> 00:13:41.130
and it covers everything
outside of my work life.

241
00:13:41.440 --> 00:13:43.310
And for those that know me in this call,

242
00:13:43.660 --> 00:13:46.240
I think there's several
people that have told me, hey,

243
00:13:46.280 --> 00:13:47.670
I'm going to be joining no pressure.

244
00:13:47.860 --> 00:13:52.440
They know that I am a bit of a workaholic
in the sense that I even like to

245
00:13:52.480 --> 00:13:53.940
work into the weekends,

246
00:13:53.980 --> 00:13:57.380
and I have the systems and routines
of being able to wake up early,

247
00:13:57.420 --> 00:14:01.160
buy my overpriced coffee in New York
City and then feel productive for

248
00:14:01.200 --> 00:14:02.570
that day as a system.

249
00:14:03.460 --> 00:14:04.680
But with that being said,

250
00:14:04.720 --> 00:14:07.700
there are things that are meaningful
to me that I want to be able to make

251
00:14:07.740 --> 00:14:10.110
sure that I keep tabs on
and then put effort into,

252
00:14:10.540 --> 00:14:13.750
whether that is my two lovely
parents, my two older brothers,

253
00:14:13.840 --> 00:14:17.540
or maybe even booking adventures
so that I'm able to see the world

254
00:14:17.580 --> 00:14:21.060
and force that free time on my
calendar to actually enjoy so

255
00:14:21.100 --> 00:14:23.490
that hopefully I can have wonderful,

256
00:14:23.680 --> 00:14:26.450
innocent stories for my
grandchildren to tell one day.

257
00:14:26.840 --> 00:14:29.310
but this is where Bobo comes into play.

258
00:14:29.580 --> 00:14:32.610
So what I'm showcasing is my mobile app.

259
00:14:33.000 --> 00:14:37.060
We have the desktop version, which
is what I primarily use to work with.

260
00:14:37.100 --> 00:14:40.240
But if I am on the go, on the way to work,

261
00:14:40.280 --> 00:14:42.100
or even just walking
throughout the office,

262
00:14:42.140 --> 00:14:45.520
I don't want to handhold my
laptop open while it works.

263
00:14:45.560 --> 00:14:47.320
But I use a mobile app.

264
00:14:47.360 --> 00:14:48.750
It's very similar to iMessage.

265
00:14:48.800 --> 00:14:51.930
It feels familiar to me,
yet really powerful as a tool.

266
00:14:53.730 --> 00:14:55.700
But so in terms of persistent memory,

267
00:14:56.090 --> 00:14:59.770
Bobo is able to actually remember and
keep tabs on everything important in

268
00:14:59.810 --> 00:15:01.320
my life outside of work.

269
00:15:01.730 --> 00:15:03.730
And so very simple use case,

270
00:15:03.770 --> 00:15:07.280
you can tell already that
there was a routine at 907 a.m.

271
00:15:08.230 --> 00:15:12.340
Bobo told me that Kith,
which is a street apparel brand,

272
00:15:12.810 --> 00:15:16.030
told me that there was a drop
yesterday that my brother might like

273
00:15:16.070 --> 00:15:20.390
and even recommended me three different
apparel items with their prices.

274
00:15:20.430 --> 00:15:26.340
So as you can see, the Georgia
Romani is a $3,000 jacket.

275
00:15:27.010 --> 00:15:30.300
I don't think, I think Grok Bot
thinks that money grows on trees,

276
00:15:30.410 --> 00:15:33.700
even though I love my brothers.
So I'll say, I love my brother,

277
00:15:34.170 --> 00:15:38.800
but not $3,000 so that it
actually knows moving forward,

278
00:15:38.930 --> 00:15:42.240
that maybe we can have actually a
price range that makes sense for me.

279
00:15:43.430 --> 00:15:45.770
So it looks like the
disconnector went off there,

280
00:15:45.810 --> 00:15:49.980
but you can showcase Grok
Bot or Bobo with my desktop.

281
00:15:50.430 --> 00:15:54.690
to where if we notice it has a couple
of routines that it launches whether it

282
00:15:54.730 --> 00:15:59.310
is looking for that kith drop whether
it is all my fancy football leagues

283
00:15:59.350 --> 00:16:03.170
um seeing of injuries across the
board of what i have to do um

284
00:16:03.210 --> 00:16:08.670
or even like my parents love this tennis
player yala uh who crushed in the u

285
00:16:08.710 --> 00:16:10.990
s open and they want to make
sure that they actually see her

286
00:16:11.030 --> 00:16:13.750
when she comes in new york city so
i want to be able to surprise them

287
00:16:13.790 --> 00:16:17.650
with tickets the moment that that
does happen um hope my parents also

288
00:16:17.690 --> 00:16:21.090
aren't watching this or else that
surprise be ruined there but This is more

289
00:16:21.130 --> 00:16:25.490
or less where Bobo has a memory to
know over time specifically how I

290
00:16:25.530 --> 00:16:26.560
actually operate.

291
00:16:27.090 --> 00:16:30.770
And even more on the travel side,
it already knows allegiances, my hotels,

292
00:16:30.810 --> 00:16:34.910
my airlines, and it's able to actually
book entire itineraries for me.

293
00:16:34.950 --> 00:16:38.460
So even legs where I have
multiple different cities,

294
00:16:38.930 --> 00:16:44.180
a different destination location,
it's able to do that because Bobo,

295
00:16:44.330 --> 00:16:47.280
for better or for worse,
I've given it its own computer.

296
00:16:47.510 --> 00:16:51.810
so we can see in the right-hand side
here that if you open up the computer

297
00:16:51.850 --> 00:16:56.890
that again is not on mine but Bobo's
virtual computer we can see it's

298
00:16:56.930 --> 00:17:02.330
already looking up hotels to book for
me Atlanta is a sample location I'm

299
00:17:02.370 --> 00:17:06.590
not going there but this is where
it's looking at the different flights

300
00:17:06.630 --> 00:17:10.090
and hotel accommodations able to
actually book an itinerary for me

301
00:17:10.130 --> 00:17:15.570
and it's as simple is having a one-step
button of saying confirm booked

302
00:17:15.610 --> 00:17:21.270
looks good so everything outside
of work that might feel mundane

303
00:17:21.310 --> 00:17:24.670
or tedious to do i have bobo
handle everything behind the scenes

304
00:17:24.710 --> 00:17:29.020
and it's made my life extremely
easier on that front there

305
00:17:32.390 --> 00:17:36.570
awesome and so promise you not this is
literally the last slide i don't want

306
00:17:36.610 --> 00:17:40.010
to bore you all too much with just
content before actually moving in to the

307
00:17:40.050 --> 00:17:45.930
demo itself but just to recap why
Grok Bot it's as simple as messaging

308
00:17:45.970 --> 00:17:47.860
a colleague with iMessage.

309
00:17:48.250 --> 00:17:51.610
And the best part about these colleagues
is that you're able to give them

310
00:17:51.650 --> 00:17:55.050
a hundred different line items and
they actually won't be frustrated with

311
00:17:55.090 --> 00:17:56.340
you for doing so.

312
00:17:56.790 --> 00:17:58.840
And secondly, they're
always on colleagues.

313
00:17:59.250 --> 00:18:01.780
So the moment that I
actually log off for work,

314
00:18:02.210 --> 00:18:05.030
it's able to still do these long
running tasks behind the scenes

315
00:18:05.070 --> 00:18:08.550
and is able to give me a summary of
what it did the next day once I actually

316
00:18:08.590 --> 00:18:12.320
do log back in. And so it
has all the tools that we do.

317
00:18:12.510 --> 00:18:17.340
This differs on the actual segment.
that you're in, but as well,

318
00:18:17.390 --> 00:18:20.610
you're able to actually finish the work
because we were able to onboard it as

319
00:18:20.650 --> 00:18:21.650
if it was a hire.

320
00:18:22.830 --> 00:18:25.930
And what I actually love
specifically as well,

321
00:18:25.970 --> 00:18:27.560
which is more of a recent feature,

322
00:18:27.770 --> 00:18:32.870
is the fact that we can share these
templates of bots to others as well

323
00:18:32.910 --> 00:18:34.010
to find value immediately.

324
00:18:34.050 --> 00:18:39.290
So if I am able to actually onboard
Bobo and knows exactly how an

325
00:18:39.330 --> 00:18:40.500
assistant should operate,

326
00:18:40.770 --> 00:18:43.890
someone else is able to leverage that
power almost immediately by getting

327
00:18:43.930 --> 00:18:45.960
this imported bot template here.

328
00:18:47.820 --> 00:18:49.050
And lastly for resources,

329
00:18:50.960 --> 00:18:55.000
what we can showcase is Grok Bot
Galaxy was a three-day session

330
00:18:55.040 --> 00:18:56.930
that was ran back in September.

331
00:18:57.460 --> 00:19:02.930
This is if you are in a specific
segment for engineering, for PMs,

332
00:19:03.340 --> 00:19:06.150
for go-to-market, even
for founders on this call.

333
00:19:06.640 --> 00:19:10.760
There's 35-minute videos of very bright
and exceptional people talking about

334
00:19:10.800 --> 00:19:12.630
how they actually use Grok Bot.

335
00:19:12.740 --> 00:19:17.010
And the cool part is we even
have Grok Bot guides here,

336
00:19:17.620 --> 00:19:21.680
where we're able to get a step-by-step
play-through of why they create

337
00:19:21.720 --> 00:19:25.130
a specific bot and being able
to actually import a bot.

338
00:19:25.440 --> 00:19:28.990
So I know here that for
the Grok Bot for SDRs,

339
00:19:29.260 --> 00:19:33.810
there's actually a chief of
staff bot called Josh Allen,

340
00:19:34.220 --> 00:19:36.520
where you're able to actually
import this from the marketplace

341
00:19:36.560 --> 00:19:41.710
and already use in your team if,
you know, PG is something of used to you.

342
00:19:42.400 --> 00:19:44.040
And so maybe if we have enough time,

343
00:19:44.080 --> 00:19:47.340
we will get to the chief of staff
portion of actually how to manage team of

344
00:19:47.380 --> 00:19:51.150
bots and what that even means,
where I can feel a little bit abstract.

345
00:19:51.500 --> 00:19:54.840
But we have a marketplace we're able
to actually get these templates out of

346
00:19:54.880 --> 00:19:57.650
the box and something that
the 201 will cover more so.

347
00:20:00.790 --> 00:20:01.690
Lovely.

348
00:20:01.730 --> 00:20:05.160
So let's move into now meeting the
team what we'll actually work on today.

349
00:20:05.510 --> 00:20:11.470
So the main objective is I want to
give a workflow where we're using a

350
00:20:11.510 --> 00:20:13.120
similar tool, whether it's Figma,

351
00:20:13.550 --> 00:20:19.810
to actually create a Grok Bot designs
so that Maya as a community bot is able

352
00:20:19.850 --> 00:20:25.200
to create Google Form, create a QR code,
able to do that using the computer use.

353
00:20:25.770 --> 00:20:28.790
And then everyone in this call is able
to participate by actually scanning

354
00:20:28.830 --> 00:20:32.730
the QR code and voting on the
best specific Grok Bot piece

355
00:20:32.770 --> 00:20:34.680
that we do make,
in this case, it's stickers.

356
00:20:34.930 --> 00:20:38.350
And then Penny will actually find
vendors that's able to print these

357
00:20:38.390 --> 00:20:42.190
stickers out and distribute them
to everyone across the board.

358
00:20:42.230 --> 00:20:46.730
So this is the workflow of being able
to actually have a team delegated to

359
00:20:46.770 --> 00:20:49.640
their own specific roles where
we have decks as a designer,

360
00:20:50.110 --> 00:20:51.910
Maya focusing on the community aspect,

361
00:20:51.950 --> 00:20:54.280
and then penny for
procurement and sourcing.

362
00:20:55.590 --> 00:20:58.090
And again, if we have time,
I put a question mark here.

363
00:20:58.130 --> 00:21:02.830
There's a fourth mystery bot that
would be able to potentially work in

364
00:21:02.870 --> 00:21:06.770
this workflow and make this process
simpler for us as we actually teach

365
00:21:06.810 --> 00:21:09.080
these bots to do their
different jobs here.

366
00:21:11.900 --> 00:21:18.810
Awesome. So let's move now into
the demo portion of this session.

367
00:21:20.000 --> 00:21:23.710
I'm going to load back
up our interface. Again,

368
00:21:24.220 --> 00:21:25.870
what I want to highlight is that

369
00:21:26.340 --> 00:21:30.140
all these different colleagues or
bots on our left-hand side should feel

370
00:21:30.180 --> 00:21:32.470
very familiar to iMessage.

371
00:21:32.720 --> 00:21:35.830
We're able to click into one and
just text in natural language.

372
00:21:36.180 --> 00:21:37.750
We even have Grok voice,

373
00:21:38.140 --> 00:21:41.730
which is a very simpler way to
actually talk with their bots and

374
00:21:41.900 --> 00:21:45.500
I know that, like, we even speak
with founders who have Teslas

375
00:21:45.540 --> 00:21:47.410
or even in their cars on the way to work,

376
00:21:47.700 --> 00:21:51.460
have Grok voice just turn through all
their emails and even route to the

377
00:21:51.500 --> 00:21:54.820
correct person on Slack if that
email needs to be escalated. Like,

378
00:21:55.540 --> 00:21:58.000
extremely cool use cases of just
using voice chat to handle all of your

379
00:21:58.040 --> 00:22:00.090
work across the board with Grok Bot.

380
00:22:00.620 --> 00:22:02.240
But really getting started here,

381
00:22:02.280 --> 00:22:04.230
if this is your first
time using this interface,

382
00:22:04.720 --> 00:22:08.950
it's as simple as going to the plus
on the top left hand side here.

383
00:22:09.720 --> 00:22:11.990
This is where we can do create new bot.

384
00:22:13.610 --> 00:22:17.040
And what we'll notice is that
it will say new bot is working.

385
00:22:17.450 --> 00:22:22.010
It would give us a simple questionnaire
of exactly what it will be designed

386
00:22:22.050 --> 00:22:24.400
to do. Excuse me.

387
00:22:25.150 --> 00:22:29.860
And so in this case,
our team is decks, mine, penny.

388
00:22:30.010 --> 00:22:33.110
We can just start off with creating
decks and what that looks like is we

389
00:22:33.150 --> 00:22:35.260
can click the new bot at the top here.

390
00:22:35.730 --> 00:22:39.830
It will pull up our right side
panel where I can click on new bot

391
00:22:39.870 --> 00:22:43.920
and actually name this
teammate to be. Dex.

392
00:22:44.810 --> 00:22:45.940
And then for the add a label,

393
00:22:46.430 --> 00:22:50.940
this does not actually change the
outcome exactly of how your bot works,

394
00:22:51.270 --> 00:22:54.250
but is more so if,
you know, Cliff has driver,

395
00:22:54.290 --> 00:22:56.940
which actually makes sense
with what the bot does.

396
00:22:57.230 --> 00:22:59.410
I have Bobo. I might forget what it is.

397
00:22:59.450 --> 00:23:01.180
So I have it as my life stabilizer.

398
00:23:01.490 --> 00:23:03.600
In this case, Dex is my designer.

399
00:23:04.090 --> 00:23:05.520
So I can have this label here.

400
00:23:06.170 --> 00:23:10.430
And so now it's as simple as just
prompting it in plain text of exactly

401
00:23:10.470 --> 00:23:11.560
what the role should be.

402
00:23:11.630 --> 00:23:12.790
And so on the left-hand side,

403
00:23:12.830 --> 00:23:16.350
there's different sections we have
unassigned bots this is ways of

404
00:23:16.390 --> 00:23:20.630
just grouping bots of if we are
eventually going to move towards a team of

405
00:23:20.670 --> 00:23:24.970
bots being able to section them and
know what they're all working on and

406
00:23:25.010 --> 00:23:29.430
so i've actually already before just
for the sake of time created all the

407
00:23:29.470 --> 00:23:34.410
three bots i would be working with
today so you have maya penny and decks

408
00:23:34.450 --> 00:23:37.910
and what i'm going to do is
highlight them double click

409
00:23:37.950 --> 00:23:44.580
and do move three bots into a new section
Notice and moved into the top here.

410
00:23:45.110 --> 00:23:46.400
And I will just say,

411
00:23:47.370 --> 00:23:50.460
Grok Bot sticker team,

412
00:23:52.450 --> 00:23:53.600
just to get started here.

413
00:23:55.840 --> 00:23:59.850
So let's start off with
specifically with a community.

414
00:24:00.280 --> 00:24:02.690
So we already know that we
want to create a Google form

415
00:24:02.880 --> 00:24:07.020
and we want to be able to have a QR
code so that everyone on this call is

416
00:24:07.060 --> 00:24:09.480
able to actually vote on the
number one rock pot sticker,

417
00:24:09.520 --> 00:24:12.510
which hasn't been created yet,
but we can just focus here specifically.

418
00:24:13.360 --> 00:24:15.640
So it's as simple again as, as,

419
00:24:15.680 --> 00:24:18.940
talking to Maya in plain text
of what exactly the role will be

420
00:24:18.980 --> 00:24:23.410
and what we should work on. So Maya
said, hey, Maran, good to meet you.

421
00:24:24.080 --> 00:24:25.310
Nice to meet you too.

422
00:24:27.060 --> 00:24:31.820
Your role is to create Google Forms so

423
00:24:31.860 --> 00:24:37.090
that the audience that
is watching us right now

424
00:24:37.620 --> 00:24:42.600
is able to vote on a specific Grok Bot

425
00:24:42.640 --> 00:24:45.850
sticker that we,

426
00:24:47.300 --> 00:24:53.630
should end up following
through with printing out.

427
00:24:54.240 --> 00:24:59.600
Your sole job here is
just to make Google Forms,

428
00:24:59.640 --> 00:25:04.830
and I will showcase how
to make this for you.

429
00:25:07.620 --> 00:25:11.830
So now this is where, like, a lot of
people that we talk to with Grok Bot

430
00:25:12.640 --> 00:25:16.200
ask, you know, how do I actually get a
bot up and running? What if I'm confused?

431
00:25:16.240 --> 00:25:17.940
If you ever are, it's very similar to,

432
00:25:17.980 --> 00:25:21.900
Cursor if you're an engineer of just
being able to ask in natural language

433
00:25:21.940 --> 00:25:25.240
what exactly that you hope to
accomplish it can even lead you to the

434
00:25:25.280 --> 00:25:30.660
correct path of of that angle there
so got it i'm in google forms bot for

435
00:25:30.700 --> 00:25:34.080
the sticker vote pulling up
how i build ready when you are

436
00:25:34.120 --> 00:25:40.020
so what i'll first say is can
you open up google forms in

437
00:25:40.060 --> 00:25:45.670
your computer so i can take control

438
00:25:48.040 --> 00:25:52.960
and so i'll click on maya and we
the details which is the routine

439
00:25:53.000 --> 00:25:57.720
specifically that Maya will do so
again routines is instead of me

440
00:25:57.760 --> 00:26:03.340
actually prompting Maya to do a
specific task we're able to set those

441
00:26:03.380 --> 00:26:08.760
routines whether weekly monthly or
even daily or even hourly a minute of

442
00:26:08.800 --> 00:26:13.600
when it fires off and does a specific
role so all that was showcase here we

443
00:26:13.640 --> 00:26:16.820
have a library so once we actually
work with Maya whether it's photos

444
00:26:16.860 --> 00:26:22.390
or videos it will showcase here
and then computer is where, again,

445
00:26:22.660 --> 00:26:27.800
we're able to see Maya's screen and
actually what Maya is working on.

446
00:26:27.840 --> 00:26:30.150
So I can click on the screen here.

447
00:26:30.820 --> 00:26:33.190
Looks like Forms is
loading on the computer.

448
00:26:33.700 --> 00:26:35.180
I'll hand it off to you soon as this up.

449
00:26:35.220 --> 00:26:39.510
So we can see that Maya went directly
to Google Forms in the computer.

450
00:26:40.620 --> 00:26:46.640
And so what I'll say now is I will
take control and actually already knew

451
00:26:46.680 --> 00:26:47.970
that I wanted to do it.

452
00:26:48.140 --> 00:26:50.560
So I can say take over now.

453
00:26:50.600 --> 00:26:51.930
notice how it prompted me.

454
00:26:52.100 --> 00:26:55.790
This is sort of the going back
and forth with the Grok Bot here.

455
00:26:56.360 --> 00:26:59.990
And so I'm going to say,

456
00:27:01.220 --> 00:27:02.370
skip this step.

457
00:27:04.060 --> 00:27:05.060
Let me

458
00:27:07.680 --> 00:27:10.950
show you create

459
00:27:13.740 --> 00:27:17.230
a form, BRB. So I'll go
back in the computer.

460
00:27:17.740 --> 00:27:21.360
This is where we have a feature
called Teach a Task that I teased so

461
00:27:21.400 --> 00:27:25.530
that Maya is able to actually
see how I do a specific flow.

462
00:27:25.640 --> 00:27:28.460
In this case, it could be a bit
trivial that's a Google form

463
00:27:28.500 --> 00:27:33.780
but this is across everything whether
it's an internal dashboard a platform

464
00:27:33.820 --> 00:27:37.040
that you want your Grok Bot to point
to and actually do work for you

465
00:27:37.080 --> 00:27:41.300
whether it's many different inputs
and even typing in different things

466
00:27:41.340 --> 00:27:45.140
from different sources able to do all
this for you can teach it directly how

467
00:27:45.180 --> 00:27:48.410
so i'm making a new form in its computer

468
00:27:48.860 --> 00:27:52.140
notice that it's currently maya's
watching and learning let's help up the

469
00:27:52.180 --> 00:27:55.710
hand side This is where I will say,

470
00:27:58.100 --> 00:27:59.100
practice,

471
00:28:00.990 --> 00:28:03.860
Grok Bot sticker votes.

472
00:28:04.990 --> 00:28:09.460
Form description, allow
the audience to vote on

473
00:28:10.780 --> 00:28:12.610
a sticker.

474
00:28:13.380 --> 00:28:18.250
And then this first one will just
be what is your favorite color?

475
00:28:18.740 --> 00:28:21.660
So this form actually won't
be sent out in a QR code.

476
00:28:21.700 --> 00:28:25.800
This is more just showcasing to Maya.

477
00:28:25.840 --> 00:28:32.640
how to create these specific options
here i'll say blue i'll say red make

478
00:28:32.680 --> 00:28:36.760
this required and now the second
point to this piece is then creating

479
00:28:36.800 --> 00:28:42.680
another option where we will use an
image so here i have google image

480
00:28:42.720 --> 00:28:47.460
attached to my account or google
drive for example for this matter

481
00:28:47.500 --> 00:28:50.310
and i'm just going to input this here

482
00:28:52.330 --> 00:28:58.200
and then type what
thicker is your favorite

483
00:29:01.520 --> 00:29:05.780
And so this is now where
we'll make sure that my nose,

484
00:29:05.820 --> 00:29:07.270
this will be a multiple choice.

485
00:29:08.620 --> 00:29:10.050
You can say option one,

486
00:29:11.160 --> 00:29:12.160
option two.

487
00:29:12.820 --> 00:29:16.250
And so now I'll make this
required and now go into publish.

488
00:29:18.350 --> 00:29:22.070
Make sure that anyone on this
call is able to also access this.

489
00:29:22.110 --> 00:29:23.400
So anyone with a link, perfect.

490
00:29:24.590 --> 00:29:26.400
And then we will say publish.

491
00:29:27.270 --> 00:29:28.520
And then we will say

492
00:29:29.650 --> 00:29:32.010
pause the video there.

493
00:29:32.050 --> 00:29:37.860
So if we notice, what I will
say to as well is, by the way,

494
00:29:38.590 --> 00:29:44.960
once we eventually get to the
sticker portion, which is later,

495
00:29:45.930 --> 00:29:48.820
you will create a QR code.

496
00:29:49.870 --> 00:29:54.540
So the audience can use the Google form.

497
00:29:55.450 --> 00:29:59.560
Number one thing to note is that once
I actually finished that recording,

498
00:29:59.650 --> 00:30:04.570
it was able to tell me, what skill
would actually use to teach our bot.

499
00:30:04.610 --> 00:30:09.740
So for context, I could have told
Maya to just create this Google form.

500
00:30:10.090 --> 00:30:11.720
It would have went through it,

501
00:30:11.770 --> 00:30:15.790
looked at the HTML divs to see what
potential options is what Martin's

502
00:30:15.830 --> 00:30:16.830
looking for.

503
00:30:17.190 --> 00:30:20.730
When we think about tokenomics and
being able to actually drive our bot in

504
00:30:20.770 --> 00:30:24.720
a behavior that makes sense to us,
this is where skills comes back into play.

505
00:30:25.130 --> 00:30:28.120
So for us to be able to actually showcase,

506
00:30:28.950 --> 00:30:30.090
instead of doing five different steps,

507
00:30:30.130 --> 00:30:32.900
so we can condense that
iteration cycle down to one step.

508
00:30:33.470 --> 00:30:38.220
And Rockbot as an interface already has
a skill called learn from demonstration,

509
00:30:38.390 --> 00:30:43.470
where it's telling Maya in this
case of being able to actually turn

510
00:30:43.510 --> 00:30:45.840
this demonstration into a reusable skill.

511
00:30:46.430 --> 00:30:49.120
And so this is something where, again,

512
00:30:49.310 --> 00:30:54.640
now if I am working on onboarding Maya
to do specific flow in my company,

513
00:30:55.090 --> 00:30:59.170
being able to actually give it the
skills and workflows and pass this off as

514
00:30:59.210 --> 00:31:00.190
a template.

515
00:31:00.230 --> 00:31:04.130
All my other teammates across the
board knows exactly how to operate on

516
00:31:04.170 --> 00:31:05.170
this specific job.

517
00:31:06.710 --> 00:31:07.960
And so it looks like, got it.

518
00:31:08.210 --> 00:31:11.940
When we do the sticker vote, I'll publish
the form, like a QR for the audience.

519
00:31:12.690 --> 00:31:15.260
This looks solid so far.
You created a blank Google form.

520
00:31:16.250 --> 00:31:20.620
So, awesome. It finished watching and
actually save it as a skill for now,

521
00:31:21.110 --> 00:31:22.110
which is great.

522
00:31:22.610 --> 00:31:26.630
What I want to move into now is
actually having new bots now work in

523
00:31:26.670 --> 00:31:28.880
sequential order and talk into each other.

524
00:31:29.210 --> 00:31:33.070
So we've trained Maya now to be able
to build its Google form once we have

525
00:31:33.110 --> 00:31:33.950
the stickers.

526
00:31:33.990 --> 00:31:37.970
The next thing here is that we
actually need to know what sticker to

527
00:31:38.010 --> 00:31:41.160
actually do. And so what we can say is,

528
00:31:42.090 --> 00:31:48.060
can you message I would do at Dex that

529
00:31:49.600 --> 00:31:55.840
you are able to create Google
forms and that there is an

530
00:31:55.880 --> 00:31:58.710
audience that will vote sticker?

531
00:32:01.140 --> 00:32:06.820
Work with Martin to create
the stickers and don't do

532
00:32:06.860 --> 00:32:10.230
anything until you speak with him.

533
00:32:12.180 --> 00:32:13.980
So now this is more where we see,

534
00:32:14.020 --> 00:32:18.000
again, these team of bots of not only
are they able to actually handle a

535
00:32:18.040 --> 00:32:19.450
slice of your role,

536
00:32:20.060 --> 00:32:24.030
but now able to also delegate that work
onwards once it is able to complete it.

537
00:32:24.320 --> 00:32:28.040
So just the backtrack here
before moving on to Dex is

538
00:32:28.080 --> 00:32:32.020
that we realized Maya actually
saved a skill called Create

539
00:32:32.060 --> 00:32:33.310
and published Google form.

540
00:32:33.740 --> 00:32:35.250
So now intelligently,

541
00:32:35.740 --> 00:32:40.280
it will know to apply this next time
if my request in prompt is applicable

542
00:32:40.320 --> 00:32:45.730
to this. Elsewise, it won't bring it
in if I have many other skills as well.

543
00:32:47.160 --> 00:32:50.370
So cool, if you notice,
Maya message decks.

544
00:32:50.660 --> 00:32:53.300
And the cool thing about Rockbot is
that we actually have transparency into

545
00:32:53.340 --> 00:32:54.340
what they're doing.

546
00:32:54.980 --> 00:32:57.830
So Maya says, hey,
I'm Maya, this is what I do.

547
00:32:58.380 --> 00:33:01.450
Please work with Martin here and
actually creating the sticker options.

548
00:33:04.220 --> 00:33:06.410
So now I have. actually go into decks

549
00:33:08.560 --> 00:33:14.310
or it looks like iMessage the
wrong decks here so I actually say

550
00:33:15.800 --> 00:33:21.480
sorry message the wrong
decks message this one moving

551
00:33:21.520 --> 00:33:23.310
forward post

552
00:33:28.850 --> 00:33:33.430
that one out and so now decks again
all of these bots across the board I

553
00:33:33.470 --> 00:33:36.810
really want to showcase how we can
start from scratch and get that working

554
00:33:36.850 --> 00:33:40.210
so now we can see that I got a
message from Maya we can move

555
00:33:40.250 --> 00:33:45.050
and do it exact same thing and so this
is now my is ready to build a google

556
00:33:45.090 --> 00:33:49.250
form what should this stick
your idea be what is great is

557
00:33:49.290 --> 00:33:51.010
that this is where we start
thinking about the connectors

558
00:33:51.050 --> 00:33:54.770
that we can give Grok Bot whether
in this case it will be Figma MCP

559
00:33:54.810 --> 00:34:01.240
which we can look in the marketplace but
for this example i have a specific uh

560
00:34:03.070 --> 00:34:07.450
Figma guidelines that we have
here at Cursor and space x AI for

561
00:34:07.490 --> 00:34:11.060
when we want to create
Grok Bot apparel stickers,

562
00:34:11.190 --> 00:34:16.050
there is this specific icons and assets
to use so that our deck designer is

563
00:34:16.090 --> 00:34:18.460
able to actually use it and
then create really cool,

564
00:34:18.630 --> 00:34:20.240
hopefully looking stickers there for us.

565
00:34:20.450 --> 00:34:23.520
So I'm just going to paste
in this specific prompt,

566
00:34:24.490 --> 00:34:27.520
create eight Grok Bot stickers
following these guidelines from Figma,

567
00:34:28.110 --> 00:34:32.330
and then just having it just tell
back to us what exactly it's thinking

568
00:34:32.370 --> 00:34:34.860
before we even move it
along in the process there.

569
00:34:36.750 --> 00:34:41.820
And so now if we really think about being
able to use computer use for each one,

570
00:34:42.730 --> 00:34:48.810
going to connect apps and Figma is
that we have these out-of-the-box

571
00:34:48.850 --> 00:34:50.230
connectors that are bidirectional.

572
00:34:50.270 --> 00:34:53.970
So not only we're able to actually
pull context in from these sources,

573
00:34:54.010 --> 00:34:56.760
but we're also able to update
those downstream objects as well.

574
00:34:57.450 --> 00:35:00.390
But what I want to know is that Figma
and their team has configured a set

575
00:35:00.430 --> 00:35:01.030
of tools,

576
00:35:01.070 --> 00:35:05.070
which is just functionalities and
things that AI is able to do with Figma.

577
00:35:05.110 --> 00:35:07.250
And so out of the box,

578
00:35:07.290 --> 00:35:10.640
there's a lot of good things like
getting a screenshot, generating design.

579
00:35:11.230 --> 00:35:14.040
But as you know, Figma is
a very complex platform.

580
00:35:14.550 --> 00:35:17.030
And so there are some things
we might be limited to doing

581
00:35:17.070 --> 00:35:20.600
if we solely just use
this connector or MCP,

582
00:35:21.310 --> 00:35:26.630
which is why computer use exactly
important and why it's awesome for DECS

583
00:35:26.670 --> 00:35:30.340
to be able to actually go and Figma
view it exactly how we view it.

584
00:35:30.530 --> 00:35:34.960
And again, we can even teach
a task to DECS on how to

585
00:35:35.110 --> 00:35:40.730
create slides in this case also how
to create stickers so it'll say i'll

586
00:35:40.770 --> 00:35:44.070
tell you what i see before you make
any stickers assuming it's different

587
00:35:44.110 --> 00:35:47.280
things i'm just going to copy
the second prompt here once

588
00:35:47.590 --> 00:35:50.580
it actually does tell me what
the stickers are going to do

589
00:35:57.080 --> 00:36:00.760
and so now it mentioned got closer
shots of those brain assets colors

590
00:36:00.800 --> 00:36:05.160
and shapes this guideline is pretty
intense in the terms of there's

591
00:36:05.200 --> 00:36:09.160
different tabs different things you
can actually use um for pulling in

592
00:36:09.200 --> 00:36:10.430
that context from Figma

593
00:36:11.860 --> 00:36:12.940
And now it'll be like,

594
00:36:12.980 --> 00:36:15.930
this is what we'll summarize for what
actually matters for these stickers.

595
00:36:17.340 --> 00:36:19.290
So to Dex's point of view,

596
00:36:19.620 --> 00:36:23.450
does not matter what Maya is talking
about in terms of making Google forums.

597
00:36:23.900 --> 00:36:26.370
This is where we view, like
when you want to create a bot,

598
00:36:26.800 --> 00:36:30.550
this is more or less just being very in
tune with what that slice of the pie is.

599
00:36:31.100 --> 00:36:34.930
And so it mentioned that here's
what the Figma Links opens up into.

600
00:36:35.280 --> 00:36:37.350
You have characters, colors, stickers.

601
00:36:38.340 --> 00:36:41.820
And so even giving us
screenshots because it's able to.

602
00:36:41.860 --> 00:36:45.600
to open up in Figma's computer,
what exactly we're working on.

603
00:36:45.640 --> 00:36:48.610
So I'll say, awesome,
I want eight new stickers.

604
00:36:49.960 --> 00:36:56.360
Pull up the new Figma file
for these stickers once

605
00:36:56.400 --> 00:37:01.290
you create it on your
computer so we can watch.

606
00:37:06.910 --> 00:37:07.770
Awesome.

607
00:37:07.810 --> 00:37:12.330
So I'll take a pause here and we can
wait for Dex to actually open its

608
00:37:12.370 --> 00:37:14.370
computer, open Figma.

609
00:37:14.410 --> 00:37:16.750
Are there any questions here?

610
00:37:16.790 --> 00:37:19.580
specifically Cliff that you've
seen have been surfaced?

611
00:37:20.970 --> 00:37:22.580
So many questions.

612
00:37:23.290 --> 00:37:27.150
I think a couple of common patterns
are how to think about knowing

613
00:37:27.190 --> 00:37:31.040
when you should use like computer
use or like the in, you know,

614
00:37:31.190 --> 00:37:33.630
the actual computer browser
yourself to teach it a task

615
00:37:33.670 --> 00:37:38.540
or something versus letting it go on
its own or trying to find a connector.

616
00:37:38.850 --> 00:37:42.910
And another common question is
around this idea of context windows

617
00:37:42.950 --> 00:37:45.150
and whether or not that
applies to Grok Bot.

618
00:37:45.190 --> 00:37:47.990
since I think folks are familiar
with that from working with other

619
00:37:48.030 --> 00:37:49.260
coding agents,

620
00:37:50.250 --> 00:37:51.250
I'll let you answer that one.

621
00:37:52.510 --> 00:37:56.030
Awesome. So for the first
question, we can tackle there.

622
00:37:56.070 --> 00:37:58.910
It sounds like it's more or
less of how to use computer use,

623
00:37:58.950 --> 00:38:02.670
or when using computer use, whether to
do teach a skill or let it roam free

624
00:38:02.710 --> 00:38:04.310
and actually do the job.

625
00:38:04.350 --> 00:38:05.760
Is that the first question there?

626
00:38:05.970 --> 00:38:09.220
Yeah, that general realm of like
how to think about that. Awesome.

627
00:38:09.550 --> 00:38:13.550
So as X pulls up, I think I'm on computer
and we can watch it in real time.

628
00:38:13.590 --> 00:38:19.070
The way that I view this is more so
guiding the Grok Bot behavior in a

629
00:38:19.110 --> 00:38:20.360
way that makes sense to us.

630
00:38:20.670 --> 00:38:23.840
So we could let our Grok Bot run free.

631
00:38:23.890 --> 00:38:28.870
And it is typically pretty well actually
designing and going end to end to

632
00:38:28.910 --> 00:38:30.240
end on creating those stickers.

633
00:38:30.930 --> 00:38:33.270
And so in this case,

634
00:38:33.310 --> 00:38:37.450
like if we want to actually save in
tokenomics and the API calls behind

635
00:38:37.490 --> 00:38:43.550
the scenes, we should be able to
actually create a skill, which now.

636
00:38:43.590 --> 00:38:46.120
now tells it step A, step B, step C,

637
00:38:46.490 --> 00:38:49.390
and it's able to get to your step
A to point A to point B in a more

638
00:38:49.430 --> 00:38:50.820
efficient manner.

639
00:38:51.090 --> 00:38:53.740
So it's more about like actually
reducing the iteration cycles.

640
00:38:54.230 --> 00:38:57.200
This is where you would use
the teacher task with computer.

641
00:38:57.990 --> 00:38:59.500
Now in terms of the plugins,

642
00:39:00.310 --> 00:39:02.640
if you're able to do a lot of
the flows with pulling plugins,

643
00:39:03.070 --> 00:39:05.020
that is also very simple to do.

644
00:39:05.250 --> 00:39:06.410
When I think about computer use,

645
00:39:06.450 --> 00:39:10.750
it's just more of things that you
are unable to do with plugins.

646
00:39:10.790 --> 00:39:16.370
So my example of Figma, having those
specific tool calls can be very limited.

647
00:39:16.410 --> 00:39:19.130
And so that's when you want computer
use to actually be able to use Figma

648
00:39:19.170 --> 00:39:22.420
for the platform that it was built to use.

649
00:39:22.690 --> 00:39:24.950
So when the connector
was created with Figma,

650
00:39:24.990 --> 00:39:30.450
it was more or less for the points of
AI to only be able to pull data from

651
00:39:30.490 --> 00:39:31.490
that source.

652
00:39:31.570 --> 00:39:32.790
Now with a computer use,

653
00:39:32.830 --> 00:39:35.800
it's now a whole new ballgame
as to what we can actually do.

654
00:39:37.660 --> 00:39:38.660
Awesome.

655
00:39:38.960 --> 00:39:44.340
And so what we'll notice here is that
Dex was able to actually showcase

656
00:39:44.380 --> 00:39:51.020
building stickers we can even
pull up directly the Figma

657
00:39:51.060 --> 00:39:57.100
here looks like it erred out and
so at this point is i would go back

658
00:39:57.140 --> 00:40:03.120
and forth with decks to can iterate
on it this is a one shot trying to

659
00:40:03.160 --> 00:40:07.360
actually onboard decks into how i want
to design Grok Bot stickers this is

660
00:40:07.400 --> 00:40:11.520
where we see actually taking the time
of if i'm a designer where i want decks

661
00:40:11.560 --> 00:40:15.880
to not only handle stickers but also
assets to be able to teach it in

662
00:40:15.920 --> 00:40:19.860
plain text of here are inspirations
here's different things of actually how

663
00:40:19.900 --> 00:40:23.740
you should go about building these
stickers out and so if on the first

664
00:40:23.780 --> 00:40:27.580
pass i'm not extremely satisfied
with it which i'd be extremely happy

665
00:40:27.620 --> 00:40:31.400
if it was able to one shot this
is where i now course correct it

666
00:40:31.440 --> 00:40:36.280
and teach it exactly what it should do
and so behind the scenes i ran decks

667
00:40:36.320 --> 00:40:39.680
a couple of times it gave me different
outcomes just because i did not

668
00:40:39.720 --> 00:40:44.660
actually to cliff's question create
a skill to build the stickers in a

669
00:40:44.700 --> 00:40:46.730
way that's routine and consistent.

670
00:40:47.600 --> 00:40:51.500
And so this is where I actually
have different sticker options here

671
00:40:51.540 --> 00:40:53.890
that we can actually showcase.

672
00:40:54.120 --> 00:40:58.300
And so this is some stickers
that a previous Dex made and

673
00:40:58.340 --> 00:41:01.270
that I actually want it to
use for the sticker vote.

674
00:41:01.540 --> 00:41:04.650
So what I'll tell Dex is awesome,

675
00:41:05.320 --> 00:41:09.710
notes the actual Pygma
screen on your computer.

676
00:41:10.240 --> 00:41:13.110
I want you to send

677
00:41:14.140 --> 00:41:15.140
Maya

678
00:41:18.020 --> 00:41:19.510
that screenshot

679
00:41:20.380 --> 00:41:27.000
so she can create a Google
form and have the audience vote

680
00:41:27.040 --> 00:41:28.450
in real time.

681
00:41:32.750 --> 00:41:35.080
And so now this is more
so not closing the loop.

682
00:41:35.120 --> 00:41:36.850
So Maya is talking to Dex.

683
00:41:37.220 --> 00:41:39.010
Dex is now talking back to Maya.

684
00:41:39.740 --> 00:41:43.640
And if we now go because
Dex has its own computer,

685
00:41:43.680 --> 00:41:49.150
able to actually create a screenshot
now of this Figma on the computer.

686
00:41:49.720 --> 00:41:54.160
And so all of these as like a conceptual
context of how we actually give

687
00:41:54.200 --> 00:41:57.370
these bots computer,
for each Grok Bot user,

688
00:41:57.860 --> 00:42:03.550
so you're a user, we provision an
entire VM or computer for your use,

689
00:42:03.800 --> 00:42:07.280
and then each of these different Grok
Bots have different desktops within them.

690
00:42:07.320 --> 00:42:11.470
So if you notice, Dex is
looking at Figma on that screen.

691
00:42:12.120 --> 00:42:16.110
Maya, though, is using Google
forms on a different screen.

692
00:42:16.520 --> 00:42:19.040
And so it's as simple as having
shared credential access.

693
00:42:19.080 --> 00:42:25.460
So once actually log in to Google
on this computer from Maya side,

694
00:42:25.500 --> 00:42:27.270
Dex is also able to do that as well.

695
00:42:27.940 --> 00:42:31.400
And so now what we'll
see is based on the skill

696
00:42:31.440 --> 00:42:35.030
that Maya learned from me teaching a task,

697
00:42:36.180 --> 00:42:39.190
Maya is hopefully now going
to create Google form,

698
00:42:39.740 --> 00:42:42.100
post that screenshot,
and find a way to do so.

699
00:42:42.140 --> 00:42:45.780
So it saved the photo into its
computer and we'll now post

700
00:42:45.820 --> 00:42:50.610
that as an actual photo for
y'all to vote on here shortly.

701
00:42:51.040 --> 00:42:54.510
So let's see, Maya's
not going to be working.

702
00:42:55.040 --> 00:42:56.790
We can leave her computer up here.

703
00:42:57.440 --> 00:43:00.430
We can see that now a new
Google form was created.

704
00:43:01.480 --> 00:43:03.870
We can even just go into full screen here.

705
00:43:04.980 --> 00:43:10.770
And we can see what Maya will now do in
terms of creating the title description

706
00:43:12.380 --> 00:43:15.290
notice that it already took
a picture of that Figma,

707
00:43:15.440 --> 00:43:17.470
and so it knew the different options here.

708
00:43:18.420 --> 00:43:21.570
It looks like it's already
ready to publish this form.

709
00:43:22.280 --> 00:43:24.970
And so what I want to note is,

710
00:43:26.080 --> 00:43:31.740
can you put the screenshots
of the different sticker

711
00:43:31.780 --> 00:43:35.150
options in that question,

712
00:43:40.530 --> 00:43:43.220
just so that when you
actually do scan the QR code,

713
00:43:43.430 --> 00:43:46.080
it is very easy to do that there?

714
00:43:51.560 --> 00:43:53.370
Awesome. So we'll let that work there.

715
00:43:53.700 --> 00:43:57.350
Cliff, is there any other questions
that have surfaced that you've seen?

716
00:43:58.600 --> 00:44:01.990
Yeah, a couple. I'll just
answer for everyone is yes.

717
00:44:02.580 --> 00:44:05.080
All of your bots are using one computer.

718
00:44:05.120 --> 00:44:06.550
It's like one cloud VM,

719
00:44:06.860 --> 00:44:08.980
but each bot is going to have,
how would you describe it,

720
00:44:09.020 --> 00:44:11.920
or like their own screen or their
own desktop, if that makes sense,

721
00:44:11.960 --> 00:44:14.290
which is part of how they
can parallelize the tasks.

722
00:44:14.680 --> 00:44:17.220
And again, in Grok Bot,
you're not supposed to,

723
00:44:17.260 --> 00:44:20.450
or you don't need to worry about things
like the idea of a context window.

724
00:44:20.860 --> 00:44:24.860
Think of the bots as a long-living
teammate that are going to manage

725
00:44:24.900 --> 00:44:29.090
many, many agents on your behalf,
each with their own context window.

726
00:44:29.220 --> 00:44:31.630
And so it's going to do all the
coordination of, like, you know,

727
00:44:31.820 --> 00:44:34.260
creating sub-agent threads,
managing their context,

728
00:44:34.300 --> 00:44:37.070
managing their memories
and tools on your behalf.

729
00:44:38.380 --> 00:44:40.390
Other than that, nothing big,
I don't think, Martin.

730
00:44:40.860 --> 00:44:44.020
Yeah, exactly. Some
questions about the VMs.

731
00:44:44.060 --> 00:44:46.640
Many, actually, many questions about,
like, where are the VMs hosted?

732
00:44:46.680 --> 00:44:48.360
What are the specs?
Can we change the specs?

733
00:44:48.400 --> 00:44:50.820
But probably beyond the 101,
unless you have any.

734
00:44:50.860 --> 00:44:52.310
high-level thoughts you want to share.

735
00:44:53.200 --> 00:44:55.170
Yeah, I think in terms
of the context memory,

736
00:44:55.780 --> 00:44:59.420
the main gist of Grok Bot is that we
want to keep it as simple as possible

737
00:44:59.460 --> 00:45:04.160
to use. We realize that even if you
have an AI tool that is powerful,

738
00:45:04.200 --> 00:45:07.870
that is able to have its own computer,
that is able to work autonomously,

739
00:45:08.820 --> 00:45:11.720
it means nothing if it's not as
simple as spinning up a new bot

740
00:45:11.760 --> 00:45:13.220
and talking to it in plain language.

741
00:45:13.260 --> 00:45:16.940
And for us to be able to handle that
memory and context behind the scenes,

742
00:45:16.980 --> 00:45:20.820
that is something that you don't
have a threshold here of like,

743
00:45:20.860 --> 00:45:22.610
you've talked to your bot too much today,

744
00:45:23.100 --> 00:45:25.750
it's going to summarize and
lose its threaded memory there.

745
00:45:26.040 --> 00:45:29.340
So that is less of what's
actually going to happen.

746
00:45:29.380 --> 00:45:32.050
And yeah, we handle all the
context memory behind the scenes.

747
00:45:39.030 --> 00:45:40.500
So now it's moving that image.

748
00:45:41.010 --> 00:45:43.360
As you notice, I said that
that is the wrong one.

749
00:45:43.770 --> 00:45:45.420
Use this specific one instead.

750
00:45:46.210 --> 00:45:48.580
And so now this is where it will actually

751
00:45:49.190 --> 00:45:51.660
create the question of what
sticker we should print.

752
00:45:52.150 --> 00:45:55.070
And then specifically that's
Korean shot in that Figma there.

753
00:45:55.110 --> 00:45:58.000
So now it'll copy their
response under link,

754
00:45:58.510 --> 00:46:02.830
hopefully now create the QR code that
the audience will then be able to

755
00:46:02.870 --> 00:46:05.230
actually do in the last
remaining time here.

756
00:46:05.270 --> 00:46:09.880
And so while this is working is I
can tell Penny and we use Grok Voice,

757
00:46:14.760 --> 00:46:18.210
hey Penny, just to note,
so moving forward,

758
00:46:18.820 --> 00:46:22.850
we have an audience watching us today
doing a 101 demonstration of Grok Bot.

759
00:46:23.220 --> 00:46:27.070
What we've had so far is we've had
decks actually create Grok Bot stickers.

760
00:46:27.480 --> 00:46:31.320
We've had Maya create a Google form
so that the audience is able to ask.

761
00:46:31.360 --> 00:46:34.230
actually vote on what
sticker we should print.

762
00:46:34.440 --> 00:46:37.870
Note that I'll give you that
information when we get there.

763
00:46:38.260 --> 00:46:41.450
I just want you first to look for vendors

764
00:46:42.020 --> 00:46:45.500
that in the New York City region
that would be able to actually print

765
00:46:45.540 --> 00:46:46.630
stickers for us.

766
00:46:46.900 --> 00:46:50.490
And look online, find that, and then
come back to me. Are there any questions?

767
00:46:51.880 --> 00:46:56.790
No questions. NYC sticker printers
online coming back to you.

768
00:46:58.300 --> 00:46:59.330
Awesome, thank you.

769
00:47:00.400 --> 00:47:01.470
Glad to help.

770
00:47:01.680 --> 00:47:04.850
Want me to flag anything specific
about the stickers while I dig,

771
00:47:05.060 --> 00:47:08.760
size, quantity, rush, turn around.
Nope, we can end the call.

772
00:47:10.460 --> 00:47:12.510
Sounds good, Martin. Talk soon.

773
00:47:13.960 --> 00:47:15.880
So we can see that once
we have the voice chat,

774
00:47:15.920 --> 00:47:18.740
it's able to actually close
off the voice because it knows

775
00:47:18.780 --> 00:47:20.730
that I'm moving on to a new task.

776
00:47:21.140 --> 00:47:23.430
We even have the dictation
here and that summary.

777
00:47:24.260 --> 00:47:28.130
But notice now that the
sticker vote forum is now live.

778
00:47:28.480 --> 00:47:32.720
What I would ask the audience to
do is if this is on your computer,

779
00:47:32.760 --> 00:47:33.850
And if you're on your phone,

780
00:47:34.360 --> 00:47:38.080
be able to actually take
a picture of this QR code

781
00:47:38.120 --> 00:47:43.050
and vote for the actual
sticker that you like here.

782
00:47:43.360 --> 00:47:49.430
And so just to note and highlight
is that if you're on a Safari,

783
00:47:49.820 --> 00:47:53.890
sometimes it might not load the image.
I would use Incognito or Chrome tab,

784
00:47:54.280 --> 00:47:58.120
but really be able to actually vote
now on the sticker and then we can wait

785
00:47:58.160 --> 00:48:00.170
and get the responses in here. And

786
00:48:18.070 --> 00:48:22.820
give me a screenshot the six stickers
and the QR code in one image.

787
00:48:23.050 --> 00:48:25.340
So it's easier to vote.

788
00:48:31.470 --> 00:48:34.820
Are you seeing any messages here,
Cliff, that they're unable to vote?

789
00:48:34.970 --> 00:48:37.460
Or actually, it looks like
we are getting responses.

790
00:48:37.650 --> 00:48:39.380
We have 415.

791
00:48:41.950 --> 00:48:42.950
Go team.

792
00:48:44.190 --> 00:48:46.410
Cliff, not that you will
influence a decision here,

793
00:48:46.450 --> 00:48:50.820
but what sticker is your
favorite so far? Which of these?

794
00:48:51.210 --> 00:48:54.760
Yeah. I like the bottom middle
one. It looks like two friends.

795
00:48:55.090 --> 00:48:56.090
Friends. Your friends?

796
00:48:58.930 --> 00:49:00.270
That's like my index in this case.

797
00:49:00.310 --> 00:49:04.250
So here, notice that it just gave me a
screenshot so it's easier now to vote

798
00:49:04.290 --> 00:49:05.960
and view the stickers to your left.

799
00:49:06.250 --> 00:49:10.550
Again, literally whatever Rockbot you
wanted to do, it has some computers,

800
00:49:10.590 --> 00:49:12.020
it's able to do that in this regards.

801
00:49:12.550 --> 00:49:15.120
And so now we'll just,
for the sake of time,

802
00:49:15.610 --> 00:49:18.780
a couple of minutes left, there's
actually close out this thing and say,

803
00:49:21.020 --> 00:49:24.230
tell Penny and you work,

804
00:49:25.200 --> 00:49:27.400
can you get the sticker winner?

805
00:49:27.440 --> 00:49:30.310
from Dex and

806
00:49:31.790 --> 00:49:38.010
then have Maya give
you the actual image or

807
00:49:38.050 --> 00:49:43.650
that winning sticker and
pull all of the different

808
00:49:43.690 --> 00:49:48.140
vendors we can use here and I will pick.

809
00:49:52.700 --> 00:49:56.210
And so it should be able to
find that Maya is referring to.

810
00:49:58.160 --> 00:50:02.130
I can just say specifically
that Maya is this one here.

811
00:50:02.480 --> 00:50:06.360
And so now when we think about the
overall trajectory of what we were

812
00:50:06.400 --> 00:50:07.400
working on,

813
00:50:07.660 --> 00:50:11.800
of being able to now onboard Dex,
a designer to build the Grok Bot stickers.

814
00:50:11.840 --> 00:50:12.480
And again,

815
00:50:12.520 --> 00:50:15.970
that was a one shot of me, would actually
work meticulously with Dex to do so.

816
00:50:17.820 --> 00:50:21.400
Onboarding Maya to be able to use
the computer use, to teach the tasks,

817
00:50:21.440 --> 00:50:26.340
to train, to use skills there so that
it is able to do this sequentially on

818
00:50:26.380 --> 00:50:29.830
its own if there is a new product
that we want to operate there.

819
00:50:30.320 --> 00:50:32.350
Notice that even got a message from Dex,

820
00:50:32.420 --> 00:50:35.270
and now it should check the form
responses for the winning sticker.

821
00:50:35.780 --> 00:50:38.700
and then to even to penny.

822
00:50:38.740 --> 00:50:42.460
So across the board, they all share
the same quote-unquote computer,

823
00:50:42.500 --> 00:50:43.850
but the different desktops.

824
00:50:44.200 --> 00:50:47.900
So we wanted to keep it extremely
easy that if you sign in once on one

825
00:50:47.940 --> 00:50:49.860
computer or one desktop, rather,

826
00:50:50.400 --> 00:50:53.430
it's synced across all of your
different bots along the scenes.

827
00:50:53.980 --> 00:50:58.350
So it's now looking into the registration.

828
00:50:58.920 --> 00:51:02.210
We can see that looking
at you did actually win.

829
00:51:02.600 --> 00:51:04.950
So congrats there, Cliff, on your choice.

830
00:51:07.480 --> 00:51:09.350
Hope I didn't skew the outcome.

831
00:51:10.760 --> 00:51:13.190
Fortunately, it was already
winning, so good there.

832
00:51:14.000 --> 00:51:15.000
But

833
00:51:16.560 --> 00:51:18.420
it looks like I used the wrong names.

834
00:51:18.460 --> 00:51:21.070
So notice I said I can get
the sticker winner from Dex,

835
00:51:21.440 --> 00:51:23.070
but Maya actually knew the winner.

836
00:51:23.440 --> 00:51:26.330
And so we can see that because
it talks back and forth,

837
00:51:27.020 --> 00:51:30.900
we actually were able to
see in real time of the fact

838
00:51:30.940 --> 00:51:34.040
that they actually figured it out
and that it actually was from Maya

839
00:51:34.080 --> 00:51:37.780
that was the actual bot that
should pull that information from.

840
00:51:37.820 --> 00:51:41.250
So we now have our own A-Sing team
that's running and working together.

841
00:51:41.560 --> 00:51:45.640
Again, we can see the conversations
of Dex saying there's actually a

842
00:51:45.680 --> 00:51:48.250
winning count vote looking at you one.

843
00:51:48.700 --> 00:51:51.870
And so here is Penny actually
doing a preview of the sticker.

844
00:51:53.000 --> 00:51:59.470
I will say, awesome, I can print
a specific print leaf Midtown.

845
00:51:59.880 --> 00:52:06.310
Open this up on your computer
and upload a sticker, J-Pagic.

846
00:52:08.580 --> 00:52:09.920
So now we're just going to wrap it.

847
00:52:09.960 --> 00:52:12.900
up here in terms of
procurement and sourcing,

848
00:52:12.940 --> 00:52:16.610
Penny will now open in its computer,

849
00:52:16.760 --> 00:52:21.940
specifically what this vendor would
be pulling the actual Figma asset into

850
00:52:21.980 --> 00:52:26.140
his computer and then uploading it
to the vendor of its choice here.

851
00:52:26.180 --> 00:52:29.310
And so I do want to be cognizant
of the remaining four minutes here.

852
00:52:29.820 --> 00:52:33.900
I just want to kind of recap everything
we've talked about where Grok Bot is

853
00:52:33.940 --> 00:52:37.140
the first ever teammate where you're
able to onboard it in natural language

854
00:52:37.180 --> 00:52:38.950
and to give it a role,

855
00:52:39.200 --> 00:52:42.390
to give it a job and as we
move up this maturity curve,

856
00:52:42.900 --> 00:52:47.120
able to actually have
potentially a now chief of staff.

857
00:52:47.160 --> 00:52:52.420
So I can, what I can do is promote
Bobo to not only be working on personal

858
00:52:52.460 --> 00:52:56.150
life stuff, but now actually,
hey, you have a team.

859
00:52:56.680 --> 00:52:59.660
This is where you're going to actually
be working end to end together

860
00:52:59.700 --> 00:53:01.890
and you are now their manager.

861
00:53:02.140 --> 00:53:05.370
So I put that in the Rockbot
sticker team section.

862
00:53:05.500 --> 00:53:08.470
Doesn't actually create
a sticker just yet.

863
00:53:09.340 --> 00:53:12.220
or it does actually create that
routine between them just yet

864
00:53:12.260 --> 00:53:15.470
but what i can do is um

865
00:53:15.960 --> 00:53:21.540
i get out of this create a group chat
and this is where i put penny i'll put

866
00:53:21.580 --> 00:53:27.840
dex i put maya and i put bobo
and i'll say bobo you have

867
00:53:27.880 --> 00:53:31.030
been promoted to chief of staff

868
00:53:33.570 --> 00:53:40.290
dex penny and maya can you
say in here what you've

869
00:53:40.330 --> 00:53:45.230
done in regarding to Grok Bot Snickers so

870
00:53:45.270 --> 00:53:48.440
that Bobo is pot up speed.

871
00:53:50.940 --> 00:53:53.740
And so the interesting part is you'll
realize they'll all now respond to

872
00:53:53.780 --> 00:53:55.470
each other in a group chat fashion.

873
00:53:56.060 --> 00:54:00.450
And this is where now, instead of
me having to manually talk to Dex,

874
00:54:01.060 --> 00:54:05.800
manually talk to Penny, I'm able
now to actually only talk to Bobo,

875
00:54:05.840 --> 00:54:06.990
which is the chief of staff,

876
00:54:07.340 --> 00:54:11.690
and that was in that SDR's Grok Bot Galaxy
case, the Josh Allen chief of staff.

877
00:54:11.980 --> 00:54:13.070
Same thing.

878
00:54:13.280 --> 00:54:19.260
of now being able to actually speak
to one leader that knows exactly how

879
00:54:19.300 --> 00:54:20.300
this team should operate.

880
00:54:20.340 --> 00:54:23.210
And that only happened because I
actually took the due diligence

881
00:54:23.580 --> 00:54:27.260
to train each bot independently
and now give them the actual skills

882
00:54:27.300 --> 00:54:30.450
and routines they need
to go end to end here.

883
00:54:31.000 --> 00:54:33.510
And so we'll notice that
this is more in the 201.

884
00:54:33.680 --> 00:54:37.640
Joseph will really showcase the different
types of things we can do across

885
00:54:37.680 --> 00:54:41.110
the board with team delegations
and passing back and forth.

886
00:54:41.300 --> 00:54:46.170
But this is with a fundamental two
minutes here, the Grok Bot interface,

887
00:54:46.560 --> 00:54:51.180
and hopefully there is something here
from computer use to connectors on

888
00:54:51.220 --> 00:54:54.620
the bottom left hand side that
you can take away in your jobs

889
00:54:54.660 --> 00:54:56.170
or even personal life there.

890
00:54:57.980 --> 00:54:58.980
Awesome.

891
00:55:00.620 --> 00:55:03.180
So just a couple of
summaries just to wrap up is

892
00:55:03.220 --> 00:55:07.690
that bots can access every single
tool even once without MCP.

893
00:55:08.020 --> 00:55:11.120
So this is the ability to
create that Google form,

894
00:55:11.160 --> 00:55:15.130
to use Figma the way that it was
intended to be built for users.

895
00:55:16.300 --> 00:55:19.280
Bots have memory, and we handle
all of that memory for you,

896
00:55:19.320 --> 00:55:22.270
so you can talk to the same
bot until the end of time.

897
00:55:22.620 --> 00:55:23.540
Well, actually, wouldn't quote me there,

898
00:55:23.580 --> 00:55:26.740
but you can talk to the same bot for
an extreme long amount of time there

899
00:55:26.780 --> 00:55:28.470
to actually learn how you operate,

900
00:55:28.680 --> 00:55:32.440
so you can trust it to do actually
meaningful work end-to-end without

901
00:55:32.480 --> 00:55:34.250
your permission at every step of the way.

902
00:55:35.060 --> 00:55:36.060
And lastly,

903
00:55:37.040 --> 00:55:38.140
when we are doing shell work,

904
00:55:38.180 --> 00:55:42.430
we're doing any specific work that we
wanted to get approval, action from us.

905
00:55:43.060 --> 00:55:45.520
We are able to actually go
with the last thing here.

906
00:55:45.560 --> 00:55:47.110
I want to showcase settings.

907
00:55:48.600 --> 00:55:53.570
And we have specific rules where
it's that when Grok Bot wants to say,

908
00:55:54.380 --> 00:55:55.650
create a Google form,

909
00:55:56.880 --> 00:56:00.540
it should ask first before actually
creating and going doing that.

910
00:56:00.580 --> 00:56:02.050
So this could be sending emails.

911
00:56:02.720 --> 00:56:05.280
This could be responding to someone
on Slack and you don't want them to

912
00:56:05.320 --> 00:56:09.450
know that AI responded. You would
have all of your rules here built in.

913
00:56:12.010 --> 00:56:15.730
Awesome. So, I want to leave
some time for Q&A as no,

914
00:56:15.770 --> 00:56:17.660
that didn't quite match out there.

915
00:56:17.710 --> 00:56:21.770
But hopefully, I know Cliff was
probably locked in on that Q&A section.

916
00:56:21.810 --> 00:56:24.290
Thank you so much, Cliff,
for handling all of that.

917
00:56:24.330 --> 00:56:30.320
This is also, I believe, the number one
workshop in terms of registrants so far.

918
00:56:30.430 --> 00:56:34.090
So huge kudos to Cliff there
and managing all of that there.

919
00:56:34.130 --> 00:56:35.130
And thank you all for joining.

920
00:56:36.490 --> 00:56:38.300
Thanks, Martin. Thanks,
everyone for coming.
