WEBVTT

1
00:00:00.000 --> 00:00:03.060
back with our team training for the week.

2
00:00:03.060 --> 00:00:05.380
We are gonna keep doing these as often as we can.

3
00:00:05.380 --> 00:00:07.440
We're gonna be moving them to Thursdays as well.

4
00:00:07.440 --> 00:00:10.560
Thursdays at noon, that just works better.

5
00:00:10.560 --> 00:00:13.360
We typically do all of our client check-ins on Tuesdays.

6
00:00:13.360 --> 00:00:14.760
And so this makes more sense

7
00:00:14.760 --> 00:00:16.520
to kind of zoom out a little bit.

8
00:00:16.520 --> 00:00:18.320
Everybody's had a little bit of time

9
00:00:18.320 --> 00:00:20.600
to do some deep work sessions during the week.

10
00:00:20.600 --> 00:00:22.520
And so I wanna just kind of chat

11
00:00:22.520 --> 00:00:25.520
about a couple of things that we're working on.

12
00:00:26.520 --> 00:00:30.000
We have been, there's just a lot.

13
00:00:30.000 --> 00:00:30.960
There's a lot that's changing.

14
00:00:30.960 --> 00:00:33.080
So what I'm gonna try to do is just spend

15
00:00:33.080 --> 00:00:35.520
just a few minutes kind of showing you

16
00:00:35.520 --> 00:00:37.720
what's changed since last week.

17
00:00:37.720 --> 00:00:39.720
Like what are some things I'm messing with?

18
00:00:39.720 --> 00:00:42.960
And then we'll jump into some examples.

19
00:00:44.000 --> 00:00:47.520
Mainly we'll talk about like how we've been using

20
00:00:47.520 --> 00:00:50.320
MCP servers now for the Innova dashboard.

21
00:00:50.320 --> 00:00:52.440
I'll show you a little bit of that here.

22
00:00:52.440 --> 00:00:54.760
So let me switch over to my demo here.

23
00:00:55.840 --> 00:01:00.640
We now added MCP to our Innova dashboard.

24
00:01:00.640 --> 00:01:03.320
This has been super helpful.

25
00:01:03.320 --> 00:01:07.120
And so now when you are in cloud code

26
00:01:07.120 --> 00:01:09.560
or whatever, you can actually spin up,

27
00:01:10.720 --> 00:01:13.040
you connect to MCP, connect to the server here.

28
00:01:13.040 --> 00:01:16.120
And we have access to all of the projects

29
00:01:16.120 --> 00:01:20.720
and clients now inside of your favorite LLM.

30
00:01:20.720 --> 00:01:22.760
You can get project details, status,

31
00:01:22.760 --> 00:01:24.600
billing status, things like that.

32
00:01:24.640 --> 00:01:26.520
You can read the framing docs.

33
00:01:26.520 --> 00:01:28.320
And then of course you can go into

34
00:01:28.320 --> 00:01:30.920
and actually pull down the task grid.

35
00:01:30.920 --> 00:01:32.640
So you can get through like manage looking

36
00:01:32.640 --> 00:01:33.880
at the slices tasks.

37
00:01:33.880 --> 00:01:37.440
You can create, edit, move, delete, slide tasks

38
00:01:37.440 --> 00:01:39.040
and even flag things as unknown.

39
00:01:39.040 --> 00:01:41.600
So the cool thing here is we can load,

40
00:01:41.600 --> 00:01:44.480
search for a project, pull down the frame

41
00:01:44.480 --> 00:01:47.880
and then basically build out the tasks

42
00:01:47.880 --> 00:01:50.400
for that project using cloud.

43
00:01:50.400 --> 00:01:52.360
So you're not having to click in and do that.

44
00:01:52.360 --> 00:01:55.960
Cause we get so used to having AI do things for us

45
00:01:56.920 --> 00:02:00.040
in 2026 now that sitting there and clicking

46
00:02:00.040 --> 00:02:01.840
into a task grid and typing out a task

47
00:02:01.840 --> 00:02:03.400
just feels like a caveman.

48
00:02:03.400 --> 00:02:06.200
So we wanted to automate all that

49
00:02:06.200 --> 00:02:08.080
and help at least get kind of the first version

50
00:02:08.080 --> 00:02:09.240
of it together.

51
00:02:09.240 --> 00:02:10.960
And one thing that we're doing,

52
00:02:10.960 --> 00:02:13.280
which I'm really liking is that we're able

53
00:02:13.280 --> 00:02:18.280
to build our process into this MCP.

54
00:02:18.880 --> 00:02:21.160
So when you pull down a project

55
00:02:21.160 --> 00:02:22.240
and you start working on tasks

56
00:02:22.240 --> 00:02:24.000
and it doesn't have a framing doc,

57
00:02:24.000 --> 00:02:26.560
it's gonna let you know that we need a framing doc

58
00:02:26.560 --> 00:02:28.400
before we can keep moving on this.

59
00:02:28.400 --> 00:02:30.640
And then I'll pull up,

60
00:02:30.640 --> 00:02:34.480
I think we had one that was the pull request.

61
00:02:34.480 --> 00:02:37.880
We did this project for a client

62
00:02:37.880 --> 00:02:40.040
and we had a little framing doc here.

63
00:02:40.040 --> 00:02:41.640
And then we went through and built out

64
00:02:41.640 --> 00:02:42.720
this little task grid.

65
00:02:42.720 --> 00:02:45.440
And so it broke the project into some slices

66
00:02:45.440 --> 00:02:47.000
for us and pulled tasks.

67
00:02:47.000 --> 00:02:48.400
So this was just sort of a,

68
00:02:48.720 --> 00:02:51.480
you know, we just did a one-shot prompt

69
00:02:51.480 --> 00:02:53.880
on this to get it to build out.

70
00:02:53.880 --> 00:02:55.240
There's of course you can keep editing it

71
00:02:55.240 --> 00:02:57.040
and changing it and manipulating it.

72
00:02:57.040 --> 00:02:59.280
And the idea would be that you would connect this

73
00:02:59.280 --> 00:03:00.680
to your existing workflow.

74
00:03:00.680 --> 00:03:03.800
So if I were to go start working on this slice,

75
00:03:03.800 --> 00:03:06.400
I might pull down that slice from the task grid

76
00:03:06.400 --> 00:03:10.320
into my terminal, go ahead and plan out

77
00:03:10.320 --> 00:03:11.720
the changes I wanna make.

78
00:03:11.720 --> 00:03:13.680
And then as you build it,

79
00:03:13.680 --> 00:03:15.040
it can go and update the status.

80
00:03:15.040 --> 00:03:17.720
So it starts to check off the items here

81
00:03:17.720 --> 00:03:19.120
as it works through that.

82
00:03:19.120 --> 00:03:22.320
And you may even have it like as it's planning it out,

83
00:03:22.320 --> 00:03:24.560
you can just tell it, hey, also update the task grid.

84
00:03:24.560 --> 00:03:26.400
We may find four or five other tasks here

85
00:03:26.400 --> 00:03:28.600
that we didn't know we needed

86
00:03:28.600 --> 00:03:30.320
once we actually get to working on it.

87
00:03:30.320 --> 00:03:34.080
So I think this will become like a really beautiful UI

88
00:03:34.080 --> 00:03:38.640
of what is actually going on in the project in real time,

89
00:03:38.640 --> 00:03:41.920
you know, as you're working through tasks

90
00:03:41.920 --> 00:03:43.640
and pushing, you know, changes and stuff.

91
00:03:43.640 --> 00:03:46.560
So I'm really excited about task grid.

92
00:03:46.560 --> 00:03:49.400
We'll also add it to the framing doc.

93
00:03:49.400 --> 00:03:51.800
The reason I haven't completely gone all in

94
00:03:51.800 --> 00:03:56.040
on the framing MCP just yet, you can pull it down,

95
00:03:56.040 --> 00:03:58.600
but I'm also wanting to make sure that we bake in

96
00:03:58.600 --> 00:04:01.240
all of our cloud skill that we talked about

97
00:04:01.240 --> 00:04:02.160
in a previous video.

98
00:04:02.160 --> 00:04:07.160
We did a whole training just on this cloud skill we created.

99
00:04:07.240 --> 00:04:08.400
And of course you can take that skill

100
00:04:08.400 --> 00:04:12.040
and put it into any LLM you want,

101
00:04:12.040 --> 00:04:17.040
but that will allow you to basically take an idea

102
00:04:17.279 --> 00:04:21.680
for a project and then get it much more fleshed out.

103
00:04:21.680 --> 00:04:24.200
I'll grab one that we did recently.

104
00:04:24.200 --> 00:04:29.200
So if I go to this project here, we have a new client.

105
00:04:30.160 --> 00:04:32.800
We did a bunch of framing here for approval.

106
00:04:32.800 --> 00:04:36.640
And I think these all went through that framing skill

107
00:04:36.640 --> 00:04:38.040
and task grid and all of that.

108
00:04:38.040 --> 00:04:40.120
And we had to do it across four different projects.

109
00:04:40.160 --> 00:04:44.800
And you'll kind of see once it comes out that skill,

110
00:04:44.800 --> 00:04:45.920
it kind of has a certain look to it.

111
00:04:45.920 --> 00:04:48.440
There's a little bit of text to introduce,

112
00:04:48.440 --> 00:04:50.600
what's broken today, why now?

113
00:04:50.600 --> 00:04:52.720
These are all things that we've heard from Ryan

114
00:04:52.720 --> 00:04:56.600
and others on as far as how to get something

115
00:04:56.600 --> 00:04:57.800
really, really tight.

116
00:04:57.800 --> 00:04:59.440
It's also being very,

117
00:05:00.000 --> 00:05:04.880
antagonistic and not just agreeing with everything that you say. So a lot of times like we'll start

118
00:05:04.880 --> 00:05:10.000
listing things here that might be a feature and it's very quick to say like, hey, you have put

119
00:05:10.000 --> 00:05:15.280
a feature as an outcome. That is not what outcomes are. Outcomes are like a little bit more general

120
00:05:15.280 --> 00:05:20.320
and they're more concrete and we can say that, hey, yes, we arrived at this outcome

121
00:05:20.320 --> 00:05:27.840
versus like, you know, adding a specific dashboard view, you know, as a feature there,

122
00:05:27.840 --> 00:05:32.400
you can kind of add that. And it feels easy like, oh yeah, we do want the dashboard feature,

123
00:05:32.400 --> 00:05:36.080
but we need to be like a little more specific on how we build those outcomes. So these are

124
00:05:36.080 --> 00:05:41.680
going to add guardrails to our entire process, which is very exciting. So we can actually bake

125
00:05:41.680 --> 00:05:46.640
in these skills to the MCP. So when you start pulling it down, you start working on it. Even

126
00:05:46.640 --> 00:05:52.320
if you don't have that cloud skill handy, you can basically use whatever LLM to reference that skill

127
00:05:52.320 --> 00:05:58.480
and we'll essentially provide that as context when you connect into the MCP. So I'm excited

128
00:05:58.480 --> 00:06:05.920
about that. I'm excited about where we're headed with it. We'll keep adding more features here.

129
00:06:05.920 --> 00:06:10.240
So I'll update them on this page and you guys can create your own key and pull those down and test

130
00:06:10.240 --> 00:06:16.960
it out. And there's a bunch of instructions here to get it connected to whatever LLM you want.

131
00:06:17.520 --> 00:06:23.920
So that's MCP. That's what we've been doing there. And it is going to be really cool because we

132
00:06:25.040 --> 00:06:32.000
have access to projects. Everything is being currently imported into this Superbase database.

133
00:06:32.000 --> 00:06:36.080
So we have all of our timesheets. We have all of our Notion projects are getting imported. So when

134
00:06:36.080 --> 00:06:40.000
you have access to the MCP, you actually have access to everything in Notion, and you also

135
00:06:40.000 --> 00:06:44.320
have access to everything in Toggle as well. So there's a lot of things we're going to start to do

136
00:06:44.320 --> 00:06:52.240
as we, let's say, want to use the MCP to create a client update. Well, now it knows that all these

137
00:06:52.240 --> 00:06:58.000
tasks got created. And when they got completed, it knows what time tracking got, what happened

138
00:06:58.000 --> 00:07:02.960
with this project. It knows maybe comments that happened in Notion. And we can basically have it

139
00:07:02.960 --> 00:07:08.160
write an email for us pretty quickly inside of the terminal. So that's kind of where we're headed

140
00:07:08.240 --> 00:07:14.800
with it long term. Also, I just got to say, we've been building this dashboard for a few months,

141
00:07:14.800 --> 00:07:21.200
and you've been hearing me talk about it for months. It took me 90 minutes to get the MCP spun

142
00:07:21.200 --> 00:07:26.800
up. It was insane how fast it came together. So what a time to be alive. I think I was talking

143
00:07:26.800 --> 00:07:33.520
to Janata this week, and we're like, it's just insane. The pace at how fast things are moving,

144
00:07:34.320 --> 00:07:39.280
you just have to be experimenting every single week with something. So this week was me setting

145
00:07:39.280 --> 00:07:45.680
up the MCP. The other thing we're going to talk about next is, of course, OpenClaw, which has

146
00:07:45.680 --> 00:07:51.040
broke the internet recently. And if you are living under a rock and don't know what OpenClaw is,

147
00:07:52.160 --> 00:07:57.760
this is by Peter. I love this tweet, just because it was like his little history here. He's like,

148
00:07:57.760 --> 00:08:05.840
sell his company for $100 million, spend three years, become jacked, come back from retirement.

149
00:08:05.840 --> 00:08:11.600
He vibe coded 43 failed projects. Number 44 was ClawedBot, goes viral. Anthropic, of course,

150
00:08:11.600 --> 00:08:18.080
sends trademark lawsuit, renamed it to MultBot. They hacked their accounts, rebranded to OpenClaw.

151
00:08:18.080 --> 00:08:22.800
180 gift cards get acquired by OpenAI. And then you have, I think one of the other ones I saw

152
00:08:23.600 --> 00:08:28.560
Sam Altman calls you a AI genius or something. It was the final bullet points on there.

153
00:08:29.120 --> 00:08:35.360
And who knows how much, I think you try to find the figure, but it's multiple billions of dollars

154
00:08:35.360 --> 00:08:42.000
that they used to acquire this open source project. So pretty crazy time to be alive.

155
00:08:42.000 --> 00:08:48.480
And so if you're kind of wondering, okay, what is OpenClaw? How does it work? It essentially is

156
00:08:48.480 --> 00:08:54.880
just taking an LLM and giving it full access to a machine. It could be your local machine,

157
00:08:54.880 --> 00:09:00.800
not recommended. It could be a virtual private server. There's a lot of ways to set it up.

158
00:09:02.160 --> 00:09:08.320
So yesterday I did that on our side and I did everything on a digital ocean droplet.

159
00:09:08.320 --> 00:09:15.120
And we have like an Innovo VPN through Nord layer. So what I did is I basically just

160
00:09:15.120 --> 00:09:21.440
whitelisted only that IP. And we also put in like a firewall layer. So there's a digital

161
00:09:21.440 --> 00:09:28.400
ocean firewall as well here that we set up. And so this is how I'm using it at the moment.

162
00:09:28.400 --> 00:09:34.080
And the way that I'm essentially working with this, I will connect through my SSH here

163
00:09:34.640 --> 00:09:39.920
directly through the VPN, through all this to this, and it's all whitelisted.

164
00:09:39.920 --> 00:09:44.240
It's pretty safe. And the other thing I'm doing, of course, is just I'm using a Slack

165
00:09:45.920 --> 00:09:53.680
bot to just talk to it here. So I'm getting over cold. So I'm going to have to mute every now and

166
00:09:53.680 --> 00:09:59.760
again. So Slack bot just chats directly with OpenClaw that we're running here.

167
00:10:00.000 --> 00:10:03.920
And I'd locked it down in a number of different ways.

168
00:10:03.920 --> 00:10:04.840
Because one of the things,

169
00:10:04.840 --> 00:10:06.160
if you guys are playing with this stuff,

170
00:10:06.160 --> 00:10:10.280
like, you know, this is, you are playing with fire.

171
00:10:10.280 --> 00:10:15.040
So like, this is, you can easily give it a lot of control

172
00:10:15.040 --> 00:10:18.000
and it can go off and do things on your behalf.

173
00:10:18.000 --> 00:10:21.240
So be very careful to like give it, you know,

174
00:10:21.240 --> 00:10:23.880
your Gmail access, careful to give it like,

175
00:10:23.880 --> 00:10:25.520
you know, sensitive information.

176
00:10:25.520 --> 00:10:27.720
I saw there's like one password integration.

177
00:10:28.680 --> 00:10:31.040
I'm not testing it with one password.

178
00:10:32.440 --> 00:10:36.400
So yeah, Greg said, don't give anything to OpenClaw

179
00:10:36.400 --> 00:10:38.800
that you wouldn't just post publicly on Twitter.

180
00:10:38.800 --> 00:10:40.480
That's a good example.

181
00:10:40.480 --> 00:10:42.600
If you're setting up, so we set up something here

182
00:10:42.600 --> 00:10:47.600
where we have a, we use the Sentry MCP server.

183
00:10:47.840 --> 00:10:50.280
We use Sentry for our logging.

184
00:10:50.280 --> 00:10:55.280
And so what I did is I created like a read only API key.

185
00:10:58.680 --> 00:11:02.080
Oh my gosh, typing is hard today.

186
00:11:02.080 --> 00:11:05.280
And then we can basically use just that read only API key

187
00:11:05.280 --> 00:11:07.520
to talk to Sentry, for example.

188
00:11:09.000 --> 00:11:11.560
We did that as well for GitHub.

189
00:11:11.560 --> 00:11:16.480
So I have GitHub here and I created basically a read only.

190
00:11:16.480 --> 00:11:19.080
And then I had to actually have it do right here.

191
00:11:19.080 --> 00:11:20.640
And then I gave it some permissions.

192
00:11:20.640 --> 00:11:23.400
This is, you know, TBD to say like, you know,

193
00:11:23.400 --> 00:11:25.800
you're not allowed to, you know,

194
00:11:26.120 --> 00:11:27.440
I think I said not allowed to, you know,

195
00:11:27.440 --> 00:11:29.560
commit to master or whatever,

196
00:11:29.560 --> 00:11:32.160
unless I specifically give you like an instruction.

197
00:11:32.160 --> 00:11:34.200
So it's saying that it's gonna stick with that.

198
00:11:34.200 --> 00:11:37.360
I don't know if it's gonna stick with that, we'll see.

199
00:11:37.360 --> 00:11:40.400
And so basically creating these layers of security

200
00:11:40.400 --> 00:11:45.400
is great because this means that it can only use this MCP

201
00:11:45.480 --> 00:11:47.640
to read what's going on in Sentry

202
00:11:47.640 --> 00:11:49.680
and get information from it.

203
00:11:49.680 --> 00:11:52.680
And then this allows it to essentially talk

204
00:11:52.680 --> 00:11:54.480
through this API key to GitHub.

205
00:11:54.480 --> 00:11:57.520
And I've been extremely locked down on like just some,

206
00:11:57.520 --> 00:12:01.000
I've only testing it on like one repo right now.

207
00:12:01.000 --> 00:12:04.120
So I'm just saying this to the team as well.

208
00:12:04.120 --> 00:12:07.320
Please test it, please play with things, do it safely

209
00:12:07.320 --> 00:12:10.440
because this is like not only our company's data,

210
00:12:10.440 --> 00:12:12.480
but sometimes it's our clients' data.

211
00:12:12.480 --> 00:12:16.280
And so just make sure things are locked down very tightly.

212
00:12:17.200 --> 00:12:21.080
I don't recommend at all running it on our local machine.

213
00:12:21.080 --> 00:12:22.800
I look forward to those options.

214
00:12:22.800 --> 00:12:24.880
I know there's some safe ways to do it,

215
00:12:24.880 --> 00:12:27.000
but this seemed like the safest way for me.

216
00:12:27.000 --> 00:12:28.240
And we were already using DigitalOcean

217
00:12:28.240 --> 00:12:29.160
for all of our hostings.

218
00:12:29.160 --> 00:12:30.640
This made a lot of sense.

219
00:12:30.640 --> 00:12:33.320
And it took me about two hours to set this all up.

220
00:12:34.840 --> 00:12:37.840
And then once I got it connected in Slack,

221
00:12:37.840 --> 00:12:40.480
I've been chatting with it and it's been working pretty well.

222
00:12:40.480 --> 00:12:43.920
So my little test yesterday was I had it go out

223
00:12:43.920 --> 00:12:47.080
and look at tribe and like pull a bunch of things down

224
00:12:47.080 --> 00:12:48.640
and say, hey, what are some of the errors

225
00:12:48.640 --> 00:12:51.120
that you're seeing there?

226
00:12:51.120 --> 00:12:54.080
And I think I can, let me see if I can find the chat history

227
00:12:54.080 --> 00:12:55.200
and just show it to you in Slack

228
00:12:55.200 --> 00:12:57.600
how this actually went down.

229
00:12:59.440 --> 00:13:02.320
Because the first, oh, also I blew through

230
00:13:02.320 --> 00:13:04.240
a few million tokens very quickly.

231
00:13:04.240 --> 00:13:08.120
Cause I was like, let's just use Opus 4.6 on everything.

232
00:13:08.120 --> 00:13:11.640
Like why would, or Sonnet or whatever the 4.6 version is,

233
00:13:11.640 --> 00:13:12.680
the latest Cloud.

234
00:13:12.680 --> 00:13:13.520
I was like, this will be great.

235
00:13:13.520 --> 00:13:14.800
Use it through the API.

236
00:13:14.800 --> 00:13:16.840
I've never really hit any limits.

237
00:13:16.840 --> 00:13:18.880
Turns out that if you're on the max plan on Cloud

238
00:13:18.880 --> 00:13:20.720
and you're in the terminal, there is no limit.

239
00:13:20.720 --> 00:13:22.280
That's why I've never hit a limit.

240
00:13:22.280 --> 00:13:24.240
As soon as you started using the API,

241
00:13:24.240 --> 00:13:26.240
you run through credits super fast.

242
00:13:26.240 --> 00:13:30.280
I think I spent like $25 in like maybe 30 minutes

243
00:13:30.280 --> 00:13:31.600
and then I hit a limit.

244
00:13:31.600 --> 00:13:33.520
Again, I've been so paranoid by it

245
00:13:33.520 --> 00:13:37.120
that I have rate limits on our Anthropic account.

246
00:13:37.120 --> 00:13:38.440
I have a separate workspace for it.

247
00:13:38.440 --> 00:13:40.120
I have different limits put on it.

248
00:13:40.120 --> 00:13:42.960
So as soon as it hit 25, I didn't go and bill like,

249
00:13:42.960 --> 00:13:44.760
you know, two and a half thousand dollars.

250
00:13:44.760 --> 00:13:46.360
At least I could, I got an email

251
00:13:46.360 --> 00:13:49.280
and Anthropic cut off my API key.

252
00:13:49.320 --> 00:13:52.440
So then I was able to go and like set it up a bit better.

253
00:13:52.440 --> 00:13:55.280
So let me grab,

254
00:13:56.200 --> 00:13:59.680
this would be cool to show you guys kind of the flow.

255
00:13:59.680 --> 00:14:01.120
Let me see if I can share it.

256
00:14:02.520 --> 00:14:05.200
Let's replace this window right in here.

257
00:14:05.200 --> 00:14:07.400
So the way that it's working right now

258
00:14:08.240 --> 00:14:11.360
is in my Slack account.

259
00:14:11.360 --> 00:14:16.200
So I have Nova, I'm calling it and it,

260
00:14:17.440 --> 00:14:18.280
let's see here.

261
00:14:18.280 --> 00:14:20.680
So I got it set up and I basically just prompted it

262
00:14:20.680 --> 00:14:23.600
to set up the MCP server itself.

263
00:14:23.600 --> 00:14:25.840
Then it went and grabbed these issues.

264
00:14:25.840 --> 00:14:27.640
It pulled some like random network issues.

265
00:14:27.640 --> 00:14:31.040
We also had a ton of like downtime in one of our clients

266
00:14:31.040 --> 00:14:32.800
and it created a little like list of things

267
00:14:32.800 --> 00:14:34.760
that it found.

268
00:14:34.760 --> 00:14:36.080
And then I said, hey, can you filter

269
00:14:36.080 --> 00:14:38.320
for a specific environment?

270
00:14:38.320 --> 00:14:39.800
Which I don't think it really did.

271
00:14:39.800 --> 00:14:40.640
That's okay.

272
00:14:40.640 --> 00:14:42.520
And it provided links to things I could jump in

273
00:14:42.520 --> 00:14:45.800
and like go and look at those specific issues.

274
00:14:45.800 --> 00:14:47.240
I said, okay, let's look at one.

275
00:14:47.240 --> 00:14:48.440
The root cause is clear.

276
00:14:48.440 --> 00:14:50.800
It's very optimistic at this point.

277
00:14:50.800 --> 00:14:52.680
It goes and like spits out a bunch of code.

278
00:14:52.680 --> 00:14:55.240
And I was like, I asked about context.

279
00:14:55.240 --> 00:14:57.640
We were still around 138,000.

280
00:14:57.640 --> 00:15:00.080
And then also it was very specific.

281
00:15:00.000 --> 00:15:02.400
that it's kind of managing context on its own.

282
00:15:02.400 --> 00:15:04.520
So I'm not sure how I feel about that,

283
00:15:04.520 --> 00:15:06.600
but you don't really have a lot of,

284
00:15:06.600 --> 00:15:09.200
especially through Slack to like start and end sessions

285
00:15:09.200 --> 00:15:10.240
from what I can see.

286
00:15:11.600 --> 00:15:15.200
So Hiza just messaged me like normal.

287
00:15:15.200 --> 00:15:17.480
Okay, let's keep going through this.

288
00:15:17.480 --> 00:15:19.400
And then we set up the, this,

289
00:15:19.400 --> 00:15:21.920
I'm just making sure I'm actually not sharing my,

290
00:15:21.920 --> 00:15:23.200
so I didn't, here's the thing,

291
00:15:23.200 --> 00:15:27.760
like I don't, I didn't put my access token in the chat, okay?

292
00:15:27.800 --> 00:15:29.920
Like that's telling it the key,

293
00:15:29.920 --> 00:15:33.080
but what I did do is I can add it to the config file.

294
00:15:33.080 --> 00:15:37.400
So I go back to my shell and go to the terminal and,

295
00:15:37.400 --> 00:15:42.160
sorry, the SSH and I connect into the server directly.

296
00:15:42.160 --> 00:15:43.320
And then I give it some instruction

297
00:15:43.320 --> 00:15:44.480
to put into the config.

298
00:15:44.480 --> 00:15:48.760
So it knows that it can use that if needed.

299
00:15:48.760 --> 00:15:49.720
So far so good.

300
00:15:49.720 --> 00:15:51.240
Again, I still have it as a read only,

301
00:15:51.240 --> 00:15:52.680
so it's pretty safe.

302
00:15:53.720 --> 00:15:57.280
And then it basically goes through and finds some issues.

303
00:15:57.280 --> 00:15:58.360
This is really boring.

304
00:15:58.360 --> 00:16:00.080
Basically where I got to was,

305
00:16:00.960 --> 00:16:03.520
the cool thing here is kind of thinking of this

306
00:16:03.520 --> 00:16:08.120
as a 24 seven team member.

307
00:16:08.120 --> 00:16:10.960
So I would never, like I was telling Lucien today,

308
00:16:10.960 --> 00:16:14.000
like both of us would never go in

309
00:16:14.000 --> 00:16:15.760
and fix the thing that it fixed.

310
00:16:15.760 --> 00:16:17.320
It's not really like a breaking issue.

311
00:16:17.320 --> 00:16:18.160
It's just that there happens

312
00:16:18.160 --> 00:16:20.360
to be all these like errors in there.

313
00:16:20.360 --> 00:16:21.800
Hopefully it'll fix it up,

314
00:16:21.800 --> 00:16:24.200
but it wasn't even worth our time to really go explore this,

315
00:16:24.200 --> 00:16:28.720
but it's totally worth a bot's time to go explore this.

316
00:16:28.720 --> 00:16:31.160
So what we did is I said,

317
00:16:31.160 --> 00:16:33.720
hey, like go ahead and push this change in.

318
00:16:33.720 --> 00:16:35.320
And then a couple of times a day,

319
00:16:35.320 --> 00:16:36.920
just go and check on this issue

320
00:16:36.920 --> 00:16:38.800
and see if what you're doing is fixing it.

321
00:16:38.800 --> 00:16:40.200
So it can kind of learn from it.

322
00:16:40.200 --> 00:16:42.320
So I would never tell anyone on our team

323
00:16:42.320 --> 00:16:45.080
to go and check something three, four times a day,

324
00:16:45.080 --> 00:16:48.280
but I would totally tell this thing to go do it.

325
00:16:48.280 --> 00:16:49.840
And so it's basically did that.

326
00:16:49.840 --> 00:16:52.280
We went back and forth on a lot of different things.

327
00:16:52.280 --> 00:16:54.440
And then let me just see where we got,

328
00:16:55.440 --> 00:16:56.640
asked it to do a little recap

329
00:16:56.640 --> 00:16:58.760
of everything it did for the day.

330
00:16:58.760 --> 00:17:03.320
And then I was asking it about how we could share this bot.

331
00:17:03.320 --> 00:17:04.720
Basically we can't share.

332
00:17:04.720 --> 00:17:06.800
Let me just get to the end.

333
00:17:06.800 --> 00:17:10.680
So then we also currently have a,

334
00:17:10.680 --> 00:17:11.960
DigitalOcean had some downtime.

335
00:17:11.960 --> 00:17:13.599
So I just shared the link with it.

336
00:17:13.599 --> 00:17:15.800
It went and grabbed the issues here

337
00:17:15.800 --> 00:17:16.960
and it's going to basically continue

338
00:17:16.960 --> 00:17:19.000
to check on DigitalOcean status for me.

339
00:17:19.000 --> 00:17:20.800
And then once it sees that DigitalOcean is good

340
00:17:20.800 --> 00:17:22.480
and it's deployed,

341
00:17:22.480 --> 00:17:24.480
then it will come back and start the sentry checks.

342
00:17:24.480 --> 00:17:26.280
And it's just going to check those logs

343
00:17:26.280 --> 00:17:27.400
every couple hours for me.

344
00:17:27.400 --> 00:17:29.760
And then if it sees something that's useful,

345
00:17:29.760 --> 00:17:31.480
it's just going to report back.

346
00:17:31.480 --> 00:17:33.280
So I just wanted to show this whole flow

347
00:17:33.280 --> 00:17:35.800
and I'm like deep in the weeds of how I'm using it.

348
00:17:35.800 --> 00:17:37.720
And it's also very fresh,

349
00:17:37.720 --> 00:17:40.000
but the shift here is not,

350
00:17:40.000 --> 00:17:41.760
I'm not like prompting it

351
00:17:41.760 --> 00:17:44.520
and it gives me information back.

352
00:17:44.520 --> 00:17:47.000
I'm prompting it to go off and do a bunch of things.

353
00:17:47.000 --> 00:17:50.680
And it's going to keep doing that until I tell it to stop.

354
00:17:51.560 --> 00:17:52.400
And I'm going to forget about it.

355
00:17:52.400 --> 00:17:53.960
And then it's going to come back to me

356
00:17:53.960 --> 00:17:54.920
and start the conversation,

357
00:17:54.920 --> 00:17:56.560
said, hey, I want to bring this to your attention.

358
00:17:56.560 --> 00:17:58.520
I know I saw this.

359
00:17:58.520 --> 00:18:00.360
So it's kind of flipping the,

360
00:18:00.360 --> 00:18:02.360
changing the way that we have conversations

361
00:18:02.360 --> 00:18:04.080
with AI a little bit

362
00:18:04.080 --> 00:18:07.360
because it is this like living, breathing thing.

363
00:18:08.560 --> 00:18:13.560
So that's kind of how I'm using it at the moment.

364
00:18:14.560 --> 00:18:16.640
I thought it'd be helpful to kind of like diagram it.

365
00:18:16.640 --> 00:18:19.000
Again, I'm a little bit into this,

366
00:18:19.000 --> 00:18:20.640
less than 24 hours,

367
00:18:21.480 --> 00:18:23.520
but we're totally starting to see the impact of it.

368
00:18:23.520 --> 00:18:25.520
Obviously you can keep stacking these,

369
00:18:26.720 --> 00:18:28.240
more and more.

370
00:18:28.240 --> 00:18:31.360
There is a great DigitalOcean article

371
00:18:31.360 --> 00:18:33.160
on like how to set OpenCLAW up.

372
00:18:33.160 --> 00:18:36.480
And I actually just took that article and fed it to CLAWD

373
00:18:37.400 --> 00:18:41.280
and I ran CLAWD in this SELI.

374
00:18:41.280 --> 00:18:43.720
And we basically just, it read the document,

375
00:18:43.720 --> 00:18:45.040
it created the plan and then it,

376
00:18:45.040 --> 00:18:47.920
we pulled up terminal and basically prompted it that way.

377
00:18:47.920 --> 00:18:51.440
I think I did use the DigitalOcean MCP for CLAWD

378
00:18:51.440 --> 00:18:53.440
to go set the droplet up.

379
00:18:53.440 --> 00:18:57.080
So CLAWD essentially assisted me in setting up OpenCLAW.

380
00:18:58.120 --> 00:19:00.080
So that was very helpful.

381
00:19:00.080 --> 00:19:03.680
And that's how I would recommend doing it.

382
00:19:03.680 --> 00:19:04.520
Just look for that article.

383
00:19:04.520 --> 00:19:05.520
If you want to do a DigitalOcean,

384
00:19:05.520 --> 00:19:07.640
I just used that because we were already paying

385
00:19:07.640 --> 00:19:09.160
for DigitalOcean and I didn't want to go set up

386
00:19:09.160 --> 00:19:11.000
a brand new account somewhere else.

387
00:19:12.360 --> 00:19:13.200
But lots of free ways.

388
00:19:13.200 --> 00:19:15.080
If you're not wanting to do any of that,

389
00:19:15.080 --> 00:19:17.560
there's a great tool called Emergent

390
00:19:18.200 --> 00:19:19.080
that basically lets you fire it up,

391
00:19:19.080 --> 00:19:23.360
kind of like a lovable style where you just plug it in

392
00:19:23.360 --> 00:19:25.600
and you can be up and running in two minutes.

393
00:19:26.480 --> 00:19:28.280
Again, you still have to be conscious

394
00:19:28.280 --> 00:19:29.360
of all the security stuff,

395
00:19:29.360 --> 00:19:33.280
but a lot more user-friendly if you don't want to be

396
00:19:33.280 --> 00:19:34.880
in the terminal hacking around and stuff.

397
00:19:34.880 --> 00:19:38.600
So it's a great time to be alive.

398
00:19:38.600 --> 00:19:40.960
It's a great time to be coding.

399
00:19:40.960 --> 00:19:43.560
This, I've mentioned this a hundred times,

400
00:19:43.560 --> 00:19:45.600
but I'm going to say it every time we do a call,

401
00:19:46.520 --> 00:19:49.160
we have spent so long doing...

402
00:19:52.080 --> 00:19:54.720
The development process is actually getting much simpler

403
00:19:54.720 --> 00:19:55.880
to build things.

404
00:19:56.920 --> 00:20:00.120
So where we would, and by focusing on these two...

405
00:20:00.000 --> 00:20:03.320
sides of it, where you're framing, you're prototyping,

406
00:20:03.320 --> 00:20:04.300
we're doing task grids.

407
00:20:04.300 --> 00:20:07.160
This is the really like the human strategy side,

408
00:20:07.160 --> 00:20:09.800
is getting to this point of clarity.

409
00:20:09.800 --> 00:20:11.240
Once you have that clarity, of course,

410
00:20:11.240 --> 00:20:14.880
just using AI to build all these things,

411
00:20:14.880 --> 00:20:16.620
fix whatever, deploy stuff.

412
00:20:17.600 --> 00:20:19.600
That's where we need it to bug fix,

413
00:20:19.600 --> 00:20:23.080
to monitor error reports, things like that

414
00:20:23.080 --> 00:20:24.040
can all happen on this side.

415
00:20:24.040 --> 00:20:26.640
And that's all coming from the agent side.

416
00:20:26.640 --> 00:20:29.040
So what we're trying to do is build platform,

417
00:20:29.040 --> 00:20:30.840
which kind of combines those two things

418
00:20:30.840 --> 00:20:33.440
where we can kind of put the framing stuff in

419
00:20:33.440 --> 00:20:34.360
through our dashboard.

420
00:20:34.360 --> 00:20:39.360
We can put information on the task grid.

421
00:20:39.720 --> 00:20:42.400
We're also starting to add transcripts

422
00:20:42.400 --> 00:20:44.600
of all of our calls with customers

423
00:20:44.600 --> 00:20:46.160
or all of our framing sessions.

424
00:20:46.160 --> 00:20:48.240
So we have that as context as well.

425
00:20:48.240 --> 00:20:50.400
So those things will start to become,

426
00:20:50.400 --> 00:20:52.960
will start to show up not just in the MCP side,

427
00:20:52.960 --> 00:20:56.560
but in the content, like we'll start to store that

428
00:20:56.560 --> 00:20:59.520
as part of the database here of the platform.

429
00:20:59.520 --> 00:21:04.200
And so it's, you've got to be experimenting with stuff.

430
00:21:04.200 --> 00:21:05.800
Don't fall behind.

431
00:21:05.800 --> 00:21:07.440
Like you can go a couple of weeks

432
00:21:07.440 --> 00:21:09.480
and all of a sudden you feel like you're a few months

433
00:21:09.480 --> 00:21:12.200
or a year behind, but just be experimenting with stuff.

434
00:21:12.200 --> 00:21:13.760
Just be trying new things.

435
00:21:13.760 --> 00:21:16.000
The models are getting better every week.

436
00:21:17.360 --> 00:21:19.800
We do have to like invest a little bit in this.

437
00:21:19.800 --> 00:21:22.120
Like these tools, some of these tools are not free,

438
00:21:22.120 --> 00:21:24.840
but even if we're spending like,

439
00:21:24.840 --> 00:21:27.720
I think our company's spending well over a thousand,

440
00:21:27.720 --> 00:21:31.520
$2,000 a month on AI stuff,

441
00:21:31.520 --> 00:21:35.840
that's still our lowest paying employee by a long shot.

442
00:21:35.840 --> 00:21:39.800
And so like the amount of work and movement we can have

443
00:21:39.800 --> 00:21:42.600
with very little money, is it crazy?

444
00:21:42.600 --> 00:21:43.640
I mean, it's hard.

445
00:21:43.640 --> 00:21:44.600
Cause like you're looking at like,

446
00:21:44.600 --> 00:21:47.240
oh, do I spend $20 on Cloud or $99 on Cloud?

447
00:21:47.240 --> 00:21:50.080
Like it seems a lot when you think of it as personal level,

448
00:21:50.080 --> 00:21:52.000
what you think as a company

449
00:21:52.000 --> 00:21:53.960
and what that's allowing you to do.

450
00:21:54.320 --> 00:21:57.600
What Cloud is allowing me to do as a founder

451
00:21:57.600 --> 00:22:00.320
to work on our apps, to build all this stuff out.

452
00:22:00.320 --> 00:22:03.280
And I'm using it, I don't know how much,

453
00:22:03.280 --> 00:22:08.280
pretty much a few hours every single day for $99 is insane.

454
00:22:08.600 --> 00:22:10.000
Like it is insane.

455
00:22:10.000 --> 00:22:12.320
It's the highest value, lowest cost thing

456
00:22:12.320 --> 00:22:13.560
in our entire company.

457
00:22:14.520 --> 00:22:17.040
And so like, I'd probably pay it

458
00:22:17.040 --> 00:22:21.200
if it was like maybe 10 or $15,000 a month,

459
00:22:21.200 --> 00:22:22.240
I'd probably still pay it.

460
00:22:22.240 --> 00:22:23.400
So at a hundred bucks a month,

461
00:22:23.400 --> 00:22:25.480
it's just like an absolutely insane.

462
00:22:25.480 --> 00:22:27.480
And maybe I'm like the old guy who's like,

463
00:22:27.480 --> 00:22:30.160
man, this technology is like so amazing,

464
00:22:30.160 --> 00:22:32.280
but it is super incredible.

465
00:22:32.280 --> 00:22:35.360
And I'm still loving all the pieces of it.

466
00:22:36.880 --> 00:22:38.440
So very cool.

467
00:22:38.440 --> 00:22:41.360
Okay, so I think we'll probably end there.

468
00:22:41.360 --> 00:22:43.760
I had one other tweet to show you that I saw from Jason,

469
00:22:43.760 --> 00:22:46.640
which was super cool, is that they're adding,

470
00:22:46.640 --> 00:22:50.040
potentially having like CLI control for Basecamp

471
00:22:50.040 --> 00:22:54.000
and Hey at some point, which is gonna be amazing.

472
00:22:54.000 --> 00:22:55.920
Because unfortunately, as far as I can tell,

473
00:22:55.920 --> 00:22:58.000
like Hey is kind of locked off from all this

474
00:22:58.000 --> 00:23:02.280
because it's not a standardized email tool.

475
00:23:02.280 --> 00:23:06.240
So it'd be cool if we can plug Hey into all of this,

476
00:23:06.240 --> 00:23:09.160
this cool diagram and have your email be context as well.

477
00:23:09.160 --> 00:23:10.720
So cool, we'll end it there.

478
00:23:10.720 --> 00:23:13.240
And then we're just gonna chat as a team, but yeah.