WEBVTT

1
00:00:00.000 --> 00:00:02.840
are back here just doing another team meeting.

2
00:00:02.840 --> 00:00:05.400
So we're gonna jump on and just hop on today

3
00:00:05.400 --> 00:00:08.440
and talk through some shaping projects we're doing

4
00:00:08.440 --> 00:00:11.960
to shape up some of the agentic workflows we have.

5
00:00:11.960 --> 00:00:14.080
So this is gonna be just a chat with our team.

6
00:00:14.080 --> 00:00:17.160
I'll bring everybody on if they wanna be on here.

7
00:00:17.160 --> 00:00:19.960
And just to open it up,

8
00:00:19.960 --> 00:00:22.680
like just open up, like the symphony came out

9
00:00:22.680 --> 00:00:25.320
like a few days ago, a few hours ago,

10
00:00:25.320 --> 00:00:26.680
and I watched this video

11
00:00:26.680 --> 00:00:27.940
and I sent it to our team last night

12
00:00:27.940 --> 00:00:29.200
and not everybody had a chance to watch it

13
00:00:29.200 --> 00:00:30.540
cause it was like 11 o'clock at night.

14
00:00:30.540 --> 00:00:33.340
So we'll watch it real quick right now

15
00:00:33.340 --> 00:00:36.980
and just wanna see what you guys think of it

16
00:00:36.980 --> 00:00:37.980
and then talk about some stuff.

17
00:00:37.980 --> 00:00:40.980
So let me share this,

18
00:00:43.260 --> 00:00:45.700
make sure I don't totally blow up everything.

19
00:00:45.700 --> 00:00:47.300
So this was from Ryan Carson.

20
00:00:47.300 --> 00:00:49.300
If you guys saw this tweet,

21
00:00:49.300 --> 00:00:50.820
he shared this thing about symphonies.

22
00:00:50.820 --> 00:00:52.300
I just thought this would be fun to watch.

23
00:00:52.300 --> 00:00:57.300
Hey everybody, I've got the new symphony orchestration

24
00:00:57.640 --> 00:00:59.760
set up with codecs and it's amazing.

25
00:00:59.760 --> 00:01:00.680
So I wanna show you this.

26
00:01:00.680 --> 00:01:03.320
So here is the TUI.

27
00:01:03.320 --> 00:01:06.240
So you can see symphony is running.

28
00:01:06.240 --> 00:01:09.760
It's got five agents running concurrently,

29
00:01:10.800 --> 00:01:14.360
throughputs 40,000 tokens per second.

30
00:01:14.360 --> 00:01:18.080
This particular run has been up running five minutes,

31
00:01:19.480 --> 00:01:21.440
eight million tokens in so far.

32
00:01:23.960 --> 00:01:26.960
This is the project that it's running.

33
00:01:27.780 --> 00:01:31.100
So symphony is connected into a linear.

34
00:01:31.100 --> 00:01:32.900
So let me just show you that

35
00:01:32.900 --> 00:01:35.260
in case you don't know what I'm talking about.

36
00:01:39.940 --> 00:01:42.420
He's running on a 50 inch Dell monitor,

37
00:01:42.420 --> 00:01:43.260
if anybody wants to know.

38
00:01:43.260 --> 00:01:45.500
So this is a spec basically the OpenAI released

39
00:01:46.700 --> 00:01:47.980
called symphony.

40
00:01:47.980 --> 00:01:52.980
And it essentially turns your repo into a code factory.

41
00:01:53.960 --> 00:01:57.120
Now you have to do some work here to get it working,

42
00:01:57.120 --> 00:01:59.480
but it was pretty plug and play.

43
00:02:00.560 --> 00:02:04.520
So you get that running, you boot it up

44
00:02:04.520 --> 00:02:06.720
and you can see that it's working right now

45
00:02:07.760 --> 00:02:11.960
on five different issues in linear.

46
00:02:11.960 --> 00:02:15.800
So here's codecs running a little sneak behind the scenes.

47
00:02:15.800 --> 00:02:19.320
So I've got, I switched to work trees

48
00:02:19.320 --> 00:02:21.360
just cause it's kind of built here.

49
00:02:21.380 --> 00:02:22.880
Okay, so this is linear.

50
00:02:24.420 --> 00:02:27.380
This is in the default view.

51
00:02:27.380 --> 00:02:32.140
You can also view this as a board if you want.

52
00:02:32.980 --> 00:02:35.740
I'll go super big just so you can see for a second.

53
00:02:35.740 --> 00:02:38.980
So you've got, this is the symphony project.

54
00:02:38.980 --> 00:02:41.580
So you've got backlog, you've got to do,

55
00:02:41.580 --> 00:02:46.580
you've got in progress, rework, human review.

56
00:02:47.420 --> 00:02:50.060
So this one is ready for me to look at.

57
00:02:50.080 --> 00:02:53.040
Merging is, so what I'll do is I'll go in

58
00:02:53.040 --> 00:02:55.640
and I'll review this and then I'll drag it over to merging

59
00:02:55.640 --> 00:02:59.720
and then it automatically uses a skill called land

60
00:03:00.880 --> 00:03:04.720
which helps merge the PR and then you can see done.

61
00:03:04.720 --> 00:03:08.840
So that's kind of cranking.

62
00:03:08.840 --> 00:03:11.420
And let's go back to the list view.

63
00:03:13.360 --> 00:03:15.640
So one is currently emerging.

64
00:03:15.640 --> 00:03:19.620
It's actually, this was a task with 20 subtasks

65
00:03:20.240 --> 00:03:22.020
and we've got a few more issues.

66
00:03:22.020 --> 00:03:23.120
Cool.

67
00:03:23.120 --> 00:03:24.320
Okay, I think you guys get the idea.

68
00:03:24.320 --> 00:03:27.700
So let me share this, sorry.

69
00:03:29.160 --> 00:03:31.100
So hopefully you guys could hear that.

70
00:03:32.580 --> 00:03:34.060
So pretty cool, a couple of things

71
00:03:34.060 --> 00:03:36.480
that I thought were like wild with it

72
00:03:37.460 --> 00:03:42.460
was just like the ability to kind of,

73
00:03:44.640 --> 00:03:45.780
I mean, we've seen some of these before.

74
00:03:45.780 --> 00:03:47.140
This one is just very simple.

75
00:03:47.140 --> 00:03:49.540
The symphony is obviously it's coming from OpenAI

76
00:03:49.620 --> 00:03:52.060
we have a number of tools.

77
00:03:52.060 --> 00:03:55.260
Like this is kind of the sweet spot would be to move now

78
00:03:55.260 --> 00:03:57.420
like from like, I told someone recently,

79
00:03:57.420 --> 00:04:00.460
like we're going from like me working

80
00:04:00.460 --> 00:04:02.600
to like me using AI as a resource.

81
00:04:02.600 --> 00:04:04.540
Like, let me look this thing up and it gets me an answer

82
00:04:04.540 --> 00:04:06.220
and I come back to my coding.

83
00:04:06.220 --> 00:04:09.000
Then it's like, now I'm working with agents

84
00:04:09.000 --> 00:04:11.040
and it's like kind of coding alongside me.

85
00:04:11.040 --> 00:04:12.360
And then now then it was just like,

86
00:04:12.360 --> 00:04:15.100
hey, we're just prompting it to do various things.

87
00:04:15.100 --> 00:04:18.440
Sort of the next layer up is like now orchestrating

88
00:04:19.000 --> 00:04:23.800
multiple parallel agents at once to do multiple tasks.

89
00:04:23.800 --> 00:04:25.200
Cause like don't, you can't sit there

90
00:04:25.200 --> 00:04:28.280
in the terminal or whatever interface you're using

91
00:04:28.280 --> 00:04:29.720
and then like prompt the next thing

92
00:04:29.720 --> 00:04:31.480
and fix this and do this.

93
00:04:31.480 --> 00:04:33.740
Now it's like, go work on all this stuff

94
00:04:33.740 --> 00:04:35.660
and then come back and I will just review it

95
00:04:35.660 --> 00:04:36.500
and make sure it's-

96
00:04:36.500 --> 00:04:39.500
So we'll like,

97
00:04:39.500 --> 00:04:44.500
so I was curious, he has a few,

98
00:04:49.580 --> 00:04:52.420
if you guys want to follow his link here

99
00:04:52.420 --> 00:04:55.780
in the chat for the team, but just look him up.

100
00:04:55.780 --> 00:04:58.740
He's got some, he's had some content today,

101
00:04:58.740 --> 00:05:00.020
but one of the,

102
00:05:00.000 --> 00:05:06.000
this morning was like he woke up and he had had like a bunch of stuff working last night

103
00:05:06.000 --> 00:05:11.200
and then when he woke up this morning they had it had found a new bug that was not part of the

104
00:05:11.200 --> 00:05:16.480
original scope and it created its own ticket in linear and then it moved it into the backlog so

105
00:05:16.480 --> 00:05:21.840
he like basically he was like oh it's this is like the first version of AGI now like it's like kind of

106
00:05:22.640 --> 00:05:29.600
finding stuff on its own and logging his own own bug so it's interesting i think there's like a lot

107
00:05:29.600 --> 00:05:36.960
of different time with looking at the AO orchestrator i think maybe gen that potentially

108
00:05:37.760 --> 00:05:41.200
have you messed with that that look one you were using when i saw it

109
00:05:43.440 --> 00:05:51.520
yeah uh it's actually uh it's that's funny because right now one thing i've been thinking

110
00:05:51.520 --> 00:06:01.520
a lot it's like how much of my time should be dedicated to like creating tools that orchestrates

111
00:06:01.520 --> 00:06:07.840
agents or like tools adjacent to agents because like everyone is looking at it this now but

112
00:06:07.840 --> 00:06:18.080
basically uh what i was building was a stretcher where i can handle and delegate work more easily

113
00:06:18.080 --> 00:06:24.000
to those agents and especially like how to add the necessary context to to do it

114
00:06:25.040 --> 00:06:33.680
and this in symphony in a way it's it's uh pretty much uh some of this but what i've

115
00:06:33.680 --> 00:06:42.720
been thinking a lot like uh to be honest i think the real value right now is to taking those open

116
00:06:42.800 --> 00:06:48.800
source things taking all those tools that are being uh launched and doing what we are trying

117
00:06:48.800 --> 00:06:56.720
to do which is basically okay how do we fit this in into our workflow so we become uh that

118
00:06:56.720 --> 00:07:06.400
agent native team uh that uh the the joffrey humbly talks about where you are actually a team

119
00:07:06.960 --> 00:07:12.880
of people that are specialists in managing agents and make sure that agents work

120
00:07:12.880 --> 00:07:20.240
because in the end uh it's coding like the agent breaks and you have to basically debug the agent

121
00:07:20.240 --> 00:07:27.840
and you go and see the sessions and two calls and it's pretty much the same thing and i think

122
00:07:27.920 --> 00:07:34.560
right now a bunch of different tools are spawning to make it easier for you to see

123
00:07:35.200 --> 00:07:42.400
uh to see what's what is what the agents are doing i was also testing mission control doesn't

124
00:07:42.400 --> 00:07:49.600
know do you guys yeah i started playing with mission control too um very cool like it loads

125
00:07:49.600 --> 00:07:57.440
up all dot codecs are dot clouds from your local files and show them in a nice dashboard like all

126
00:07:57.440 --> 00:08:03.120
the agents are the sessions it's very interesting yeah that's good i think like this is just

127
00:08:03.120 --> 00:08:09.040
something to be experimenting with like so uh one i just want to like talk about that today like

128
00:08:09.040 --> 00:08:13.520
this is just it's cool it's out like we should we should figure out how to um there's another

129
00:08:13.520 --> 00:08:23.440
janata that wants to join i was i was ready to show what it does like yeah scans are all open

130
00:08:23.440 --> 00:08:30.400
sessions and all history uh basically because all this is stored in your machine so it takes

131
00:08:30.400 --> 00:08:36.960
all this data and shows you on a on a nice nice dashboard and you can see like memory for the

132
00:08:36.960 --> 00:08:43.600
agents the skills and stuff uh this one doesn't see all my items because i'm running it on a

133
00:08:43.600 --> 00:08:49.600
closed environment but i'm seeing it for test like it created this one where basically it's a

134
00:08:49.600 --> 00:08:56.160
uh codex agent and it shows here but like it's a local uh it's just a md file on my computer

135
00:08:56.160 --> 00:09:04.000
inside to to see it better let's say very it's but it's interesting um can you drop the link uh

136
00:09:04.640 --> 00:09:13.680
to that one yeah sure we have we'll get a good list of links going um yeah one like just

137
00:09:13.680 --> 00:09:17.840
experimenting i know you've spent a lot of time experiencing with a lot of these different ones

138
00:09:17.840 --> 00:09:21.840
the the confusing thing is they're all starting to do the same thing which is when you get into

139
00:09:21.840 --> 00:09:27.120
the ai like everybody's like oh open claw started then there was like tons of forks of open claw now

140
00:09:27.120 --> 00:09:33.680
there's like you know a lot of versions of symphony and then um i saw perplexity computer out as well

141
00:09:33.680 --> 00:09:40.080
so there was like a web browser version of that um and i had a friend who went deep into perplexity

142
00:09:40.080 --> 00:09:44.480
computer and he was running his whole business on it and then basically maxed it out in like three

143
00:09:44.480 --> 00:09:50.240
days um of his like the highest plan of whatever he like maxed it out and so it was gonna be like

144
00:09:50.240 --> 00:09:55.120
a few thousand dollars a month to keep it going at that rate so he basically found something else

145
00:09:55.120 --> 00:09:59.840
but they just released like a local um version

146
00:10:00.000 --> 00:10:07.880
of that, which kind of runs in your toolbar to do various tasks.

147
00:10:07.880 --> 00:10:11.600
It's getting towards this thing I talked, I can't remember if it was with you guys.

148
00:10:11.600 --> 00:10:19.680
There's a great podcast from Darkesh and Elon Musk on all the future of agentic things.

149
00:10:19.680 --> 00:10:21.040
So it's like three hours long.

150
00:10:21.040 --> 00:10:24.160
I do recommend checking it out because it's very technical.

151
00:10:24.160 --> 00:10:31.000
It's the co-founder of Stripe and an engineer, so they stay very technical on a lot of it.

152
00:10:31.000 --> 00:10:37.580
And so generally where all this is going is like, what can a computer do or how would

153
00:10:37.580 --> 00:10:38.760
I work with someone?

154
00:10:38.760 --> 00:10:43.620
Like I'm kind of working with you guys, like where my entire interaction is like assigning

155
00:10:43.620 --> 00:10:50.020
tasks or talking in Slack, or maybe there's kind of conversation back and forth.

156
00:10:50.020 --> 00:10:53.780
How can we get it to where you can do everything that you could do through the interface of

157
00:10:53.780 --> 00:10:54.780
a computer?

158
00:10:54.780 --> 00:10:59.040
That's kind of where it needs to get to for these like sort of virtual employees, these

159
00:10:59.040 --> 00:11:02.500
agentic employees.

160
00:11:02.500 --> 00:11:06.300
And then of course the next step is in like bringing it into like a robot and actually

161
00:11:06.300 --> 00:11:07.540
interacting with the real world.

162
00:11:07.540 --> 00:11:12.020
So that's like the next piece, but before we get there, it has to be like basically

163
00:11:12.020 --> 00:11:17.460
as efficient as if you hired an employee like in another country and you just worked like

164
00:11:17.460 --> 00:11:22.260
remotely with that person, it should be able to do everything that that person's doing.

165
00:11:22.260 --> 00:11:24.220
And so that's just an interesting thought.

166
00:11:24.220 --> 00:11:29.180
There's a lot of cool nuggets in there as far as like the future and where that's all

167
00:11:29.180 --> 00:11:30.180
going to go.

168
00:11:30.180 --> 00:11:34.900
And like the fact that there's a very small chance that any of this AI will be able to

169
00:11:34.900 --> 00:11:38.020
control like for building something so much smarter and more powerful.

170
00:11:38.020 --> 00:11:43.700
And there's so many more AI intelligence versus like human intelligence.

171
00:11:43.700 --> 00:11:46.460
Like why would we have a chance at controlling that?

172
00:11:46.460 --> 00:11:47.460
It's really good.

173
00:11:47.460 --> 00:11:53.420
I still feel really positive and uplifted from the, it's kind of like ends in a pretty

174
00:11:53.420 --> 00:12:00.620
depressing state, but like bringing it back here is like now we're trying to figure out

175
00:12:00.620 --> 00:12:06.260
like how do we take a lot of this work, which you again, kind of being like almost like

176
00:12:06.260 --> 00:12:12.700
the manager role, like it was you managing like one employee, like you're a junior developer,

177
00:12:12.700 --> 00:12:13.700
like do this.

178
00:12:13.700 --> 00:12:14.700
Then he like does something.

179
00:12:14.700 --> 00:12:15.700
You're like, do it this way.

180
00:12:15.700 --> 00:12:16.700
Now do it that way.

181
00:12:16.940 --> 00:12:21.100
So you're just kind of like, you know, over their shoulder, micromanaging this one poor

182
00:12:21.100 --> 00:12:22.100
employee.

183
00:12:22.100 --> 00:12:23.860
Now it's kind of like backing up a little bit and they're getting a little bit more

184
00:12:23.860 --> 00:12:28.780
reliable to where you can have multiple running in parallel and having it kind of chop up

185
00:12:28.780 --> 00:12:29.780
things.

186
00:12:29.780 --> 00:12:33.940
And I think specifically for like, I think as it applies to us, like reactive work specifically

187
00:12:33.940 --> 00:12:39.060
I think would be massive, although the span of a reactive task could be everything from

188
00:12:39.060 --> 00:12:43.140
like a bug to like a minor feature request to like something that really should be a

189
00:12:43.140 --> 00:12:45.140
project that somehow landed in reactive.

190
00:12:45.140 --> 00:12:53.620
So we have to kind of like filter through these different lenses, but I think just saying

191
00:12:53.620 --> 00:12:58.860
just keep experimenting with stuff and like officially for our team as well.

192
00:12:58.860 --> 00:13:01.900
Like I know we said, you know, get the max plan, get whatever.

193
00:13:01.900 --> 00:13:08.180
Like I'll I was thinking like we should each just have like 200 bucks a month to just spend

194
00:13:08.180 --> 00:13:11.620
on whatever AI experimentation you want.

195
00:13:11.620 --> 00:13:16.980
So just like have $200 and just like set it on fire and don't even think about it.

196
00:13:16.980 --> 00:13:18.580
But I mean, don't do that.

197
00:13:18.580 --> 00:13:21.220
But like basically just don't overthink it.

198
00:13:21.220 --> 00:13:27.020
Like because for such, this is a crazy time in history where like for so little money,

199
00:13:27.020 --> 00:13:32.500
like so ridiculously small amount of money, you could 5X, 10X your output.

200
00:13:32.500 --> 00:13:34.700
It's just unbelievable.

201
00:13:34.700 --> 00:13:38.060
So we'll figure that out admin wise.

202
00:13:38.060 --> 00:13:42.540
But like I just I think like I talked to another founder and they're like, oh my gosh, like

203
00:13:42.540 --> 00:13:47.780
I'm like the AI subscriptions are taking over our business, like all the SAS subscriptions

204
00:13:47.780 --> 00:13:48.780
used to do.

205
00:13:48.780 --> 00:13:49.780
And I was like, great.

206
00:13:49.780 --> 00:13:54.340
Like like hand like give them a get everybody a credit card and just let them go crazy with

207
00:13:54.340 --> 00:13:55.340
it.

208
00:13:55.340 --> 00:13:58.940
Like if one person figures out one workflow that saves the company a ton of time, like

209
00:13:58.940 --> 00:14:06.100
great, like go hack it and test stuff and you know, right.

210
00:14:06.820 --> 00:14:13.100
So that's how I would, yes, that's kind of my thoughts so far on it, like just keep experimenting

211
00:14:13.100 --> 00:14:14.100
with it.

212
00:14:14.100 --> 00:14:18.260
I've wasted a lot of time, well not wasted, I'd say like researched a lot of spent a lot

213
00:14:18.260 --> 00:14:24.100
of research time on OpenClaw and went down a bad rabbit hole trying to make it super

214
00:14:24.100 --> 00:14:25.100
secure.

215
00:14:25.100 --> 00:14:26.100
Didn't work out very well.

216
00:14:26.100 --> 00:14:28.340
Now I'm back like trying some other things.

217
00:14:28.340 --> 00:14:34.340
But I think I'm going to try to my next experiment was to kind of experiment with the orchestration

218
00:14:34.340 --> 00:14:36.180
components a little bit.

219
00:14:36.180 --> 00:14:40.780
And one thing we landed on, so one thing I do want to do as a team is like just go back

220
00:14:40.780 --> 00:14:45.420
to framing and some breadboarding on a good next step for what's something we know we

221
00:14:45.420 --> 00:14:46.420
could build right now.

222
00:14:46.420 --> 00:14:49.820
Because there's a lot of unknowns, there's a lot of like rabbit holes of like things

223
00:14:49.820 --> 00:14:52.020
we can go and experiment with and play with.

224
00:14:52.020 --> 00:14:53.020
And that's where I got lost.

225
00:14:53.020 --> 00:14:57.380
I was like, oh, cool, I got OpenClaw set up and all this stuff and like, what do I even

226
00:14:57.380 --> 00:14:58.380
want this thing to do?

227
00:14:58.380 --> 00:15:00.020
Like, like, I kind of like have built.

228
00:15:00.000 --> 00:15:02.740
built a robot, and then I don't actually need a robot.

229
00:15:02.740 --> 00:15:05.500
I just built it because it was cool.

230
00:15:05.500 --> 00:15:07.500
So kind of starting a little bit with, OK,

231
00:15:07.500 --> 00:15:10.260
let's take a real workflow.

232
00:15:10.260 --> 00:15:12.540
How would we go and attack reactive work?

233
00:15:12.540 --> 00:15:16.380
Or how would we attack something else in the team,

234
00:15:16.380 --> 00:15:18.260
like something that's a little more concrete?

235
00:15:18.260 --> 00:15:19.940
So we landed, we chatted yesterday

236
00:15:19.940 --> 00:15:25.020
with Lucian Chinada a little bit about a plan to kind of what

237
00:15:25.020 --> 00:15:27.820
we could do for the team, and really came down

238
00:15:27.820 --> 00:15:33.580
to an Anovo CLI, or CLI, as Chinada says.

239
00:15:33.580 --> 00:15:36.300
And then we would have a way that you guys could interact.

240
00:15:36.300 --> 00:15:40.380
I also saw Perplexity, the founder of Perplexity,

241
00:15:40.380 --> 00:15:43.580
was basically telling people MCPs are dead.

242
00:15:43.580 --> 00:15:44.420
They're super slow.

243
00:15:44.420 --> 00:15:48.100
I saw Peter Levels tweet the same thing this morning.

244
00:15:48.100 --> 00:15:50.500
So immediately, I was like, well, forget MCPs.

245
00:15:50.500 --> 00:15:51.660
Let's delete that.

246
00:15:51.660 --> 00:15:54.780
Those are gone and dead to us.

247
00:15:54.780 --> 00:15:56.660
MCPs were so last week.

248
00:15:56.660 --> 00:16:02.820
Those were so like February 2026.

249
00:16:02.820 --> 00:16:05.300
But yeah, we can't wait.

250
00:16:05.300 --> 00:16:06.780
What was that?

251
00:16:06.780 --> 00:16:08.380
That's 2000 and late.

252
00:16:08.380 --> 00:16:10.460
Yeah, 2000 late.

253
00:16:10.460 --> 00:16:14.220
But so having something where it kind of gives us

254
00:16:14.220 --> 00:16:17.100
all the flexibility to experiment with stuff,

255
00:16:17.100 --> 00:16:19.620
and then, but you're going to need us like,

256
00:16:19.620 --> 00:16:25.020
because there's like, you need some hard data or data

257
00:16:25.020 --> 00:16:29.140
that we can interact with on the, like,

258
00:16:29.140 --> 00:16:32.060
so I think having a CLI or something that can talk

259
00:16:32.060 --> 00:16:35.140
directly to the APIs, because the whole Anovo dashboard

260
00:16:35.140 --> 00:16:36.260
is built on APIs.

261
00:16:36.260 --> 00:16:37.940
So all of that stuff is accessible.

262
00:16:37.940 --> 00:16:40.940
We could figure out a way to prep that.

263
00:16:40.940 --> 00:16:44.700
So it's like very easy for LLM to process where everything

264
00:16:44.700 --> 00:16:46.380
is in the structure.

265
00:16:46.380 --> 00:16:47.820
But that's kind of one thing.

266
00:16:47.820 --> 00:16:50.100
So we're going to move to that in a minute.

267
00:16:50.100 --> 00:16:52.540
But first, isn't it, and you're going

268
00:16:52.540 --> 00:16:56.540
to say something about the orchestration structure, maybe?

269
00:17:00.140 --> 00:17:00.860
And you're muted.

270
00:17:00.860 --> 00:17:02.620
Sorry, I muted you because you're a dog.

271
00:17:05.619 --> 00:17:08.859
You removed my power to talk.

272
00:17:08.859 --> 00:17:14.420
I just said, my dog's going to start barking down here.

273
00:17:14.420 --> 00:17:15.420
It's a symphony.

274
00:17:19.220 --> 00:17:21.780
I shouldn't say it's something I found this morning

275
00:17:21.780 --> 00:17:24.940
in those lines of, like, everything now

276
00:17:24.940 --> 00:17:26.700
needs to be a CLI.

277
00:17:26.700 --> 00:17:31.180
And maybe we can use this tool to turn

278
00:17:31.180 --> 00:17:33.220
the dashboard into a CLI.

279
00:17:33.220 --> 00:17:36.100
It's basically a tool to scan the repository

280
00:17:36.100 --> 00:17:39.620
and expose the API and expose whatever

281
00:17:39.620 --> 00:17:42.860
you need to be exposed as a CLI.

282
00:17:42.860 --> 00:17:45.380
It's the current CLI, all the things.

283
00:17:45.380 --> 00:17:47.260
Yeah.

284
00:17:47.260 --> 00:17:49.700
Yeah, no.

285
00:17:49.700 --> 00:17:54.380
I'm now experimenting with Obsidian for my personal notes

286
00:17:54.380 --> 00:17:57.500
because of their CLI.

287
00:17:57.500 --> 00:17:59.060
It's so good.

288
00:17:59.060 --> 00:18:04.300
And also, I think it's more agent-oriented

289
00:18:04.300 --> 00:18:08.580
because now everything on agents is just an MD file.

290
00:18:08.580 --> 00:18:11.660
And the Obsidian files are just an MD file.

291
00:18:11.660 --> 00:18:15.620
So I feel it's more closer to what the language

292
00:18:15.620 --> 00:18:17.380
the agent is talking.

293
00:18:17.380 --> 00:18:18.220
Yeah.

294
00:18:18.460 --> 00:18:20.540
I don't know how to use that.

295
00:18:20.540 --> 00:18:23.060
Yeah, we're deeply integrated with Notion.

296
00:18:23.060 --> 00:18:26.980
So I see an end to that at some point.

297
00:18:26.980 --> 00:18:29.580
Like, we'll figure that out.

298
00:18:29.580 --> 00:18:32.500
But it's not going to make sense to have it all.

299
00:18:32.500 --> 00:18:36.780
And the incentive for Notion is to not allow you to, like,

300
00:18:36.780 --> 00:18:38.420
they allow you to export your data.

301
00:18:38.420 --> 00:18:40.580
But the incentive for them at this point

302
00:18:40.580 --> 00:18:45.900
is to create the closet as much as possible.

303
00:18:45.900 --> 00:18:48.100
So I don't know if that's good for us,

304
00:18:48.100 --> 00:18:51.420
especially us that we know how to create our own software,

305
00:18:51.420 --> 00:18:52.700
which is cool.

306
00:18:52.700 --> 00:18:55.540
Like, we can create something like the dashboard,

307
00:18:55.540 --> 00:18:56.660
very personalized.

308
00:18:56.660 --> 00:18:58.340
So that's fun.

309
00:18:58.340 --> 00:18:59.540
Yeah, for sure.

310
00:18:59.540 --> 00:19:04.700
So I think always going back in true form,

311
00:19:04.700 --> 00:19:07.580
like, OK, sounds awesome.

312
00:19:07.580 --> 00:19:09.900
Now what?

313
00:19:09.900 --> 00:19:11.860
And how did that happen?

314
00:19:15.940 --> 00:19:17.220
Cool.

315
00:19:17.220 --> 00:19:20.460
Are you getting that, or is that me?

316
00:19:20.460 --> 00:19:22.140
Give us a thumbs up.

317
00:19:22.140 --> 00:19:25.660
I've gathered you here to tell you about it.

318
00:19:25.660 --> 00:19:28.580
I'm getting that.

319
00:19:28.580 --> 00:19:31.700
Welcome to my TED Talk.

320
00:19:31.700 --> 00:19:32.820
Anyway, I'll leave it there.

321
00:19:32.820 --> 00:19:37.260
Maybe it's like, OK, we'll see if it jumps.

322
00:19:37.260 --> 00:19:40.340
So just coming back to our good old trustee process here,

323
00:19:40.340 --> 00:19:42.540
like, a little bit of a frame of, like,

324
00:19:42.540 --> 00:19:44.900
if we were going to go do the next batch of work,

325
00:19:44.900 --> 00:19:47.140
like, where would we want to land on the now?

326
00:19:47.140 --> 00:19:48.780
Like, what are the actual problems here?

327
00:19:48.780 --> 00:19:50.660
I started this just before the call.

328
00:19:50.660 --> 00:19:55.180
But obviously, we're currently experimenting with, like,

329
00:19:55.180 --> 00:19:56.500
we're all experimenting stuff, but we're

330
00:19:56.500 --> 00:19:58.580
having to recreate a lot of connections in and out

331
00:19:58.580 --> 00:20:00.140
of Lenovo.

332
00:20:00.000 --> 00:20:12.000
And so I think one of the things, you know, eventually what I was seeing is like, there's some sort of like data hub, or some sort of, and I'm not going to a solution of like, oh, it's definitely a CLI, or it's definitely MCP.

333
00:20:12.000 --> 00:20:25.000
But the idea would be that you could feed your whatever agentic workflow orchestration system, like in like dynamic data that's in a controlled way, and it's logged.

334
00:20:25.000 --> 00:20:44.000
Like, that was the other thing I was going to say is that like, all access and, you know, changes are logged, you know, so we could say like this, we can kind of blame, you know, Janata's, you know, AO, like orchestrator or whatever, you know, for a task, like we can say, oh, this thing changed on this date or whatever.

335
00:20:45.000 --> 00:21:02.000
I do think like, we don't currently have, like tasks are not a part, or I'll be specific, Notion tasks are not part of the Innova-Dash like right now. I'm gonna drop the link just so you guys have it in case, jump in.

336
00:21:04.000 --> 00:21:05.000
But like,

337
00:21:07.000 --> 00:21:08.000
the,

338
00:21:08.000 --> 00:21:32.000
so we don't have, we're not part of the dashboard yet. But we do have like, sort of the task grid idea. But it doesn't really, you know, that might work. I think what's, what I'm seeing work really well with the linear approach, and don't worry, we're not gonna like switch to linear, you know, tomorrow, which I was like, oh, forget Notion, we're all in on linear now, like,

339
00:21:33.000 --> 00:21:59.000
but is the is kind of the same thing is kind of how Notion works. There's like a task level, like, here's the headline of the task. And when you click into it, there's like, there's a whole lot of detail in there. And that's what we're gonna have to have to make this work, like a task grid is not gonna work for an LLM, because it just is one sentence. And really, to me, it's a scratch pad of like ideas, like, I need to do this thing, do that thing, whatever.

340
00:21:59.000 --> 00:22:28.000
It's not, it's not like, it's not breaking down, like what the actual issue is, and referencing files and like giving a lot of context. Because I think part of it will be having we talked about yesterday was like, can we have tasks come in and then send it off to an agent to go properly shape it up and get deep? It's not, I would say shape it up, but just to define it more to get clarity to make it more concrete, like, users are saying button doesn't work, I hit the button, it breaks.

341
00:22:29.000 --> 00:22:50.000
You know, something crashes, whatever. Can we send that off with like, and it's like, oh, it's on this screen on this thing. Yeah, when you hit this, it's missing a whatever argument, something. And then it gets more specific. And you can look and be like, yep, that makes sense. Fire that off, off it goes. And then you just, you know, when you get to the review state, can you click on it, view it, make sure it's good.

342
00:22:50.000 --> 00:23:19.000
But it's the time in between, like letting that thing go sit for, you know, a while. And even, it's not so much like, oh, well, I could that one's gonna take five to 10 minutes to go fix and come back and then I'll do the next task. It's that like, you actually don't care when this happens. Like, I'm just gonna queue up like a bunch of work for my Thursday, fire it off, off it goes. And then like, you're gonna get like, at some point, it will alert me that I'm back in review process. And I'll just come back and then I'll like pick it up again.

343
00:23:20.000 --> 00:23:35.000
Versus like kind of being in this like single, single thread, it's like having a single core CPU, like you're just able to do this one thing, and like advance the next thing in like a very linear approach. But this will let you go like multi thread, essentially, to have a lot of different things going.

344
00:23:35.000 --> 00:24:02.000
And I have seen in the sym, like when you set symphony up, it is really, as far as I can see, like set up for a specific app or specific project, I believe, like you actually install symphony, like in the repo. And so like you kind of set that up, let's say for like tribe just by itself. And then again, it would be sort of like tribe flutter, maybe we can find it, like put them in one, you know, directory with both repos that you know, however, that works.

345
00:24:03.000 --> 00:24:20.000
But we would need to like, that's one approach, just kind of setting up on like a project level. But anything else you guys are like thinking as far as this could work? And like, I'll start with the bad part out bounds area here.

346
00:24:21.000 --> 00:24:37.000
Well, are there any natural, I guess, guardrails or stage gates where you don't want them to do something? I guess, without being sequentially approved, you know, like something with billing or sending invoices or something like that.

347
00:24:37.000 --> 00:25:00.000
That would be on like sort of the workflow piece. I'm thinking there's like a hub of data, just that, like concrete, factual data that like there is a client and its client's name is this, there's a project, the project name is this, there's like these tasks for this project here with details.

348
00:25:00.000 --> 00:25:05.080
Um, you know, if there's more information about those, we'll give it like a nice

349
00:25:05.080 --> 00:25:10.360
interface to like, get me tasks, get me like, Hey, I want to work on this project.

350
00:25:10.360 --> 00:25:14.820
It fetches like a couple tasks you work on, you know, go through something, shape

351
00:25:14.820 --> 00:25:17.400
them up or whatever, um, and then fire them off.

352
00:25:17.840 --> 00:25:20.800
Um, what I don't want to do is be, I don't, I want to kind of keep it like

353
00:25:21.020 --> 00:25:25.640
workflow and agent agnostic so that like, Janata can try something and

354
00:25:25.640 --> 00:25:28.160
Lucia can try something and I can try something and Greg, like we all try our

355
00:25:28.280 --> 00:25:30.560
own little spin on it and see what works.

356
00:25:31.120 --> 00:25:36.440
Um, cause I don't want to necessarily like, like, uh, lock in on like, Oh,

357
00:25:36.440 --> 00:25:38.860
it has to be these seven steps.

358
00:25:38.920 --> 00:25:41.040
And then, you know, cause I don't know if we're there yet.

359
00:25:41.040 --> 00:25:46.720
I don't think we're yet there yet to like, uh, sort of hard code the workflow yet.

360
00:25:47.640 --> 00:25:48.160
Um,

361
00:25:50.920 --> 00:25:51.880
ever made the context.

362
00:25:51.880 --> 00:25:53.600
Thank you for keeping me honest.

363
00:25:54.280 --> 00:25:55.080
It's not a problem.

364
00:25:55.280 --> 00:25:56.040
It's just a thing.

365
00:25:56.040 --> 00:25:56.720
It's just a fact.

366
00:25:58.800 --> 00:26:03.160
Uh, one question, uh, is this initial version, are we thinking about it read

367
00:26:03.160 --> 00:26:07.800
only or it, or it allow the agent to also update the data back to the system?

368
00:26:07.800 --> 00:26:09.400
I think it needs to update too.

369
00:26:09.520 --> 00:26:14.560
So you can say that like, um, yeah, I would say read and, you know, right.

370
00:26:15.520 --> 00:26:15.960
Um,

371
00:26:16.920 --> 00:26:19.000
yeah, my suggestion.

372
00:26:19.560 --> 00:26:20.040
Okay.

373
00:26:20.080 --> 00:26:21.480
I'll change it up here.

374
00:26:21.480 --> 00:26:22.800
Read it up here.

375
00:26:23.120 --> 00:26:23.620
Yeah.

376
00:26:23.960 --> 00:26:27.920
This one was like, uh, it's, it's

377
00:26:28.280 --> 00:26:30.920
and you could, we could do this actually.

378
00:26:30.960 --> 00:26:34.040
Let's just be really prescriptive here.

379
00:26:34.360 --> 00:26:39.000
Um, cause you don't really, you're reading client data.

380
00:26:39.440 --> 00:26:45.240
Um, you're going to like, uh, read and write tasks.

381
00:26:45.360 --> 00:26:46.440
We'll just say projects.

382
00:26:47.360 --> 00:26:47.860
Um,

383
00:26:49.800 --> 00:26:52.400
and projects are the frame and that's great.

384
00:26:53.040 --> 00:26:57.160
Or, and also like metadata, like where, when it starts, when it ends.

385
00:26:57.160 --> 00:26:57.660
Right.

386
00:26:58.120 --> 00:26:58.620
Yeah.

387
00:26:58.620 --> 00:27:02.480
And I think like having, yeah, meted, like basically reading everything, the

388
00:27:02.480 --> 00:27:06.320
framing, the task grid, also the, whatever notion tasker, because when we say

389
00:27:06.320 --> 00:27:10.520
project, the project in the dashboard is the same project as notion.

390
00:27:10.520 --> 00:27:11.720
So they're one in the same.

391
00:27:12.040 --> 00:27:15.320
It just, there happens to be like, uh, it's stored in the database.

392
00:27:15.520 --> 00:27:17.920
Um, so like, I'm going to do the same thing.

393
00:27:18.800 --> 00:27:22.160
One-to-one like super base notion, basically.

394
00:27:22.600 --> 00:27:23.120
Exactly.

395
00:27:23.120 --> 00:27:27.240
Actually, if you go down here, um, you can, I'll just, I'll

396
00:27:27.240 --> 00:27:32.680
make this just for context, but there's like, we'll call it notion projects

397
00:27:32.680 --> 00:27:34.960
and they have an ID and that's just things like that.

398
00:27:35.640 --> 00:27:38.840
Um, and this would be like, you know, name.

399
00:27:39.520 --> 00:27:42.440
And how this, this is getting synced today.

400
00:27:42.440 --> 00:27:43.600
It's a Chrome job or?

401
00:27:43.680 --> 00:27:45.120
Every five minutes it syncs.

402
00:27:45.160 --> 00:27:45.520
Yeah.

403
00:27:45.520 --> 00:27:49.800
It's pretty, it's pretty in sync and it does a two way, um, it

404
00:27:49.840 --> 00:27:51.720
merges everything two way.

405
00:27:52.400 --> 00:27:56.400
That seems to be, it's on an edge function right now.

406
00:27:57.360 --> 00:27:59.200
Just for context right here.

407
00:27:59.200 --> 00:28:00.160
Chrome drops.

408
00:28:03.800 --> 00:28:07.600
So my, and I would say the source of truth is the dashboard.

409
00:28:08.000 --> 00:28:13.640
Um, like if I deleted our notion account, technically I could like dump everything

410
00:28:13.640 --> 00:28:19.080
back in, like all, I set up all the projects again, not fully true.

411
00:28:19.080 --> 00:28:23.880
Like we have a lot of other information in notion, but like from a standpoint,

412
00:28:23.880 --> 00:28:25.520
like the projects are backed up.

413
00:28:26.120 --> 00:28:28.120
Maybe that would be an outcome.

414
00:28:28.440 --> 00:28:31.200
Like we make sure that source of truth of projects.

415
00:28:31.200 --> 00:28:32.160
That's the current state.

416
00:28:32.240 --> 00:28:35.640
Source of truth of projects is a context.

417
00:28:36.200 --> 00:28:36.520
Yeah.

418
00:28:46.760 --> 00:28:48.320
Maybe that could be a outcome.

419
00:28:48.320 --> 00:28:52.440
You know, the source of truth of tasks is in the dashboard.

420
00:28:54.320 --> 00:28:55.040
That's interesting.

421
00:28:55.120 --> 00:29:00.600
And I think that's, I mean, probably like a morning or something like that.

422
00:29:00.600 --> 00:29:01.640
So we can make it work.

423
00:29:02.640 --> 00:29:05.880
They all say it's a new source of truth for tasks.

424
00:29:06.080 --> 00:29:10.920
Cause I think like the way that notion works, it's, it's, uh, like we're

425
00:29:10.920 --> 00:29:13.240
syncing the project database right now.

426
00:29:13.360 --> 00:29:17.360
I just literally have to like, it'll take me 15 minutes to like also sync the

427
00:29:17.360 --> 00:29:20.800
task database because all the relationship fields and how it's all linked and all

428
00:29:20.800 --> 00:29:22.360
that is already in there.

429
00:29:22.800 --> 00:29:23.520
Um, okay.

430
00:29:23.640 --> 00:29:24.160
Question.

431
00:29:24.200 --> 00:29:28.640
Does a task in notion, how does a task of, uh, who, where were the questions?

432
00:29:29.280 --> 00:29:30.080
Oh, did someone delete?

433
00:29:30.160 --> 00:29:30.720
Oh, sorry.

434
00:29:30.720 --> 00:29:31.400
I deleted.

435
00:29:32.000 --> 00:29:39.080
I'll leave it out here as a sticky cause I like, um, does a task in notion

436
00:29:39.160 --> 00:29:43.840
equal a task in a, um, slice or task grid?

437
00:29:47.240 --> 00:29:50.280
I think ideally they would be one-to-one.

438
00:29:50.360 --> 00:29:51.120
I think like,

439
00:29:53.720 --> 00:29:55.600
I would fall back to like the problem.

440
00:29:55.600 --> 00:29:57.680
Cause I feel it's not crispy enough yet.

441
00:29:57.720 --> 00:30:00.000
It's like pretty good.

442
00:30:00.000 --> 00:30:06.000
Though like many small reactive tasks is just like a lot of load and I really like the thing of like

443
00:30:11.520 --> 00:30:16.960
Like we can consider that like we've tackled this problem if we have somehow the ability to like

444
00:30:17.600 --> 00:30:23.760
Queue up queue up a bunch of things and kind of like break the dependency of like one-to-one like i'm watching a task

445
00:30:24.240 --> 00:30:29.840
I can just say like oh I want this done like fire off. I'll come back and review a batch, you know

446
00:30:30.480 --> 00:30:31.600
so

447
00:30:31.600 --> 00:30:37.440
If you're focusing on like just this like problem and solution then task grid is kind of not

448
00:30:38.800 --> 00:30:41.300
We could decide like projects or it's just a reactive

449
00:30:41.920 --> 00:30:43.520
project problem

450
00:30:43.520 --> 00:30:45.520
Yeah, we could drill into it more

451
00:30:45.760 --> 00:30:49.440
And to be honest, uh, I don't know about you guys, but for me

452
00:30:50.080 --> 00:30:52.080
uh, if i'm using task grid

453
00:30:52.960 --> 00:30:59.200
Uh, usually notion just becomes a backfill like I do it after like just for the tracking purpose

454
00:30:59.280 --> 00:31:01.280
Like I do everything on the that's like

455
00:31:01.840 --> 00:31:06.400
That should be a problem right now. Like the fact that you even have to do that is kind of silly

456
00:31:07.520 --> 00:31:09.520
like that's

457
00:31:10.160 --> 00:31:15.200
I usually I usually just keep on the on the notion for like tracking purpose, but

458
00:31:16.080 --> 00:31:17.840
uh, because

459
00:31:17.840 --> 00:31:20.000
yeah, I feel because I think like

460
00:31:21.680 --> 00:31:27.440
It's it's a bit slower to to move on on on the on the notion

461
00:31:28.320 --> 00:31:29.840
Structure so

462
00:31:29.840 --> 00:31:33.040
I usually like just have the tasks and I just go like

463
00:31:34.160 --> 00:31:38.000
How i'm doing it now is basically I take I copy the task grid

464
00:31:38.480 --> 00:31:43.140
And then I break it down into markdown files for the implementation

465
00:31:43.920 --> 00:31:45.920
And then I have the agents running it

466
00:31:46.400 --> 00:31:48.800
Uh, and I just have like amd file

467
00:31:48.880 --> 00:31:54.320
That's basically a representation of the task grid on my local repo and updates it locally

468
00:31:54.400 --> 00:31:58.960
And when I finish my session, I just go to the task grid and I update it there

469
00:31:59.600 --> 00:32:00.720
um

470
00:32:00.720 --> 00:32:06.560
So in this workflow, you see I don't I didn't have to touch the notion tasks itself

471
00:32:07.280 --> 00:32:08.320
um

472
00:32:08.320 --> 00:32:13.440
so yeah, because I also that's something we may need to question about our process like

473
00:32:14.400 --> 00:32:18.800
how much do we need notion tasks if we have the task grid now like

474
00:32:19.520 --> 00:32:22.160
I don't know if i'm i'm questioning too much but like

475
00:32:22.720 --> 00:32:27.920
I do. Do you really need the notion tasks at this point? How you guys are using it?

476
00:32:29.040 --> 00:32:33.680
Yeah, I want to I want to chime in on this because to me they're like fundamentally totally different

477
00:32:34.080 --> 00:32:37.520
Like task group is fantastic tool to get like a map, you know

478
00:32:37.600 --> 00:32:42.160
I'm building like this thing. It's like this slice and like I make progress in the slice

479
00:32:43.040 --> 00:32:45.040
and I use a lot the

480
00:32:45.120 --> 00:32:48.800
Tasks in notion for taking notes, you know, I do deep research on something

481
00:32:50.000 --> 00:32:52.000
yeah, so

482
00:32:52.160 --> 00:32:54.880
They have like a layer deeper, right? Like you're actually

483
00:32:55.600 --> 00:33:01.360
um, this is like great if you just want to sketch out like quick thoughts that you want but like I think what you're doing

484
00:33:01.440 --> 00:33:02.880
is they're like

485
00:33:02.880 --> 00:33:05.600
What also we may be able to do is if if we click into?

486
00:33:06.400 --> 00:33:09.760
like this would just be the title of a task and we click in it and it does have like

487
00:33:10.240 --> 00:33:15.200
Maybe there's a notion icon next to it and you could open it in notion. Oh, that doesn't mean perfect

488
00:33:15.440 --> 00:33:17.600
Yeah, because if we like the same way we go

489
00:33:18.160 --> 00:33:20.720
Up here and we click notion for the project level

490
00:33:21.200 --> 00:33:22.880
we should be able to like

491
00:33:22.880 --> 00:33:24.640
Click on the task level

492
00:33:24.640 --> 00:33:28.560
and go to a notion task because that way I could do is I could I just I could like create create create create

493
00:33:28.880 --> 00:33:32.880
And then if I need to go deeper I can tap on it and there's already a notion task that exists

494
00:33:32.880 --> 00:33:34.880
So all it would do is open it up

495
00:33:34.960 --> 00:33:36.960
and if I and then I can also go into the

496
00:33:37.200 --> 00:33:40.960
Project level and I could look at my this one doesn't actually oh here it is

497
00:33:41.280 --> 00:33:43.600
This one has like whatever projects are here

498
00:33:44.160 --> 00:33:45.600
and we could actually

499
00:33:45.600 --> 00:33:47.600
These would be one in the same. So like you could

500
00:33:48.320 --> 00:33:52.720
If you want to look at it through this way, I can have these different statuses. That's still accurate

501
00:33:53.040 --> 00:33:56.640
but you could kind of see it here. The only difference is we probably have to have like a

502
00:33:57.280 --> 00:33:59.040
catch all like

503
00:33:59.040 --> 00:34:01.680
notion no slice associated box

504
00:34:02.480 --> 00:34:08.000
Right if we created that there's uh, I want to kind of like drive further on this because

505
00:34:08.560 --> 00:34:11.040
To me like the bigger pain point to me

506
00:34:11.040 --> 00:34:16.560
They're very distinct the way I work on the project and the way I work on reactive is like totally different worlds

507
00:34:17.280 --> 00:34:18.400
that's

508
00:34:18.400 --> 00:34:19.520
if

509
00:34:19.520 --> 00:34:21.520
if we focus just on like

510
00:34:21.820 --> 00:34:23.360
reactive because

511
00:34:23.360 --> 00:34:25.920
Like you're working in the task grid. It's like

512
00:34:27.040 --> 00:34:32.080
Yes, I can take like more notes on a specific task, but essentially it's like sequentially, you know

513
00:34:32.480 --> 00:34:36.000
First task and the next task has to happen some parallelization may happen

514
00:34:36.320 --> 00:34:41.280
But then reactive is like almost 100 like they're just unrelated I just like can fire them off

515
00:34:41.920 --> 00:34:43.179
all off

516
00:34:43.179 --> 00:34:45.440
separately, so I think if we

517
00:34:46.560 --> 00:34:53.440
My worry is that if we just get kind of carried away to like connect task grid with like notion tasks and ai agents

518
00:34:54.080 --> 00:34:58.720
We'll create like more work than like we could have focused on just like a more specific problem

519
00:34:59.040 --> 00:35:01.040
Which is like reactive?

520
00:35:00.000 --> 00:35:04.680
tasks are just like too many small things and then we would kind of cut out

521
00:35:04.680 --> 00:35:12.480
a bunch of like problems to solve for which is that tighter frame maybe we

522
00:35:12.480 --> 00:35:18.840
maybe if we focus on on reactive and I think that's a good a good decision for

523
00:35:18.840 --> 00:35:26.240
us to just like talk reactive maybe we don't need to to to worry about like the

524
00:35:26.240 --> 00:35:34.400
source of truth we can remove it or we can make it so that reactive project is

525
00:35:34.400 --> 00:35:39.880
a different type of project on our dashboard and then instead of using the

526
00:35:39.880 --> 00:35:45.360
task grid module we just show a cam bone module which would show that one to one

527
00:35:45.360 --> 00:35:51.400
of the tasks in ocean and then this is kind of solved for the reactive

528
00:35:51.400 --> 00:35:56.520
structure because that's true like reactive is just like this this line of

529
00:35:56.520 --> 00:35:59.880
work it's really combined style like I have everything you have to do and

530
00:35:59.880 --> 00:36:05.920
usually you can execute a lot of stuff in parallel but like we ironically the

531
00:36:05.920 --> 00:36:12.120
the statuses for projects are the statuses for tasks right now I think I

532
00:36:12.120 --> 00:36:17.080
think they're exactly matched so like we could I think I'm with you like we could

533
00:36:17.080 --> 00:36:21.840
actually task grid is a tool like you know Ryan gave us is a good tool for the

534
00:36:21.840 --> 00:36:25.960
job like if it depends on the right product if you're like in a new feature

535
00:36:25.960 --> 00:36:30.920
build you're sketching out a bunch of ideas but I do agree like we may have a

536
00:36:30.920 --> 00:36:34.720
ticket come through as a reactive task that's kind of like this thing that has

537
00:36:34.720 --> 00:36:40.360
to move through the system so it's kind of like a small it's a mini project you

538
00:36:40.360 --> 00:36:43.400
know but it's kind of in the wrapper of a project because we have to have

539
00:36:43.440 --> 00:36:46.800
something to build and track time and clients and all that too so it's like a

540
00:36:46.800 --> 00:36:51.240
it's like a child project of a real project that's what is beautiful about

541
00:36:51.240 --> 00:36:55.000
notion is you can just kind of keep going in this like as deep as you want

542
00:36:55.000 --> 00:36:59.480
so if you started making like notes and sub pages and all kinds of stuff that's

543
00:36:59.480 --> 00:37:05.760
great for notion to just go crazy with all your research notes but I think what

544
00:37:05.760 --> 00:37:11.320
we need now for the and I do think that the that layer of depth to it is as a

545
00:37:11.320 --> 00:37:15.400
hundred percent needed for anything agent like we're gonna have to load up

546
00:37:15.400 --> 00:37:19.400
all the research and then even when it comes and proposes its plan it's got to

547
00:37:19.400 --> 00:37:23.320
put it somewhere so it's got to go into a thing it's I can't just right now like

548
00:37:23.320 --> 00:37:28.000
so maybe like one of the I don't know if this is a problem or a context but just

549
00:37:28.000 --> 00:37:34.200
like right now like you know tasks what we call task in the in the dashboard are

550
00:37:34.200 --> 00:37:39.000
basically just like a single line you know text note or something it's like

551
00:37:39.000 --> 00:37:46.240
there's no you know page or depth to it at all and so that that's I put in the

552
00:37:46.240 --> 00:37:50.680
problem status because it's it is plan that's blocking us right now to come to

553
00:37:50.680 --> 00:37:54.640
the outcome of being able to use this for agentic workflow and so what we

554
00:37:54.640 --> 00:37:57.520
could do is like I put under here if you're good or there's like no changes

555
00:37:57.520 --> 00:38:03.720
to the task grid just focus on notion tasks just and I'll just say notion tasks

556
00:38:03.720 --> 00:38:10.760
sync so right we will end up with from a data standpoint we have tasks and I'll

557
00:38:10.760 --> 00:38:16.520
just say like if there's no task ID a slice ID then it just won't be in the

558
00:38:16.520 --> 00:38:26.400
right because this could have like a notion task ID here yeah and these lies

559
00:38:26.400 --> 00:38:32.360
could be a property like if you want like a new notion property on tasks if

560
00:38:32.360 --> 00:38:40.240
we want to make this tracking the other way go notion back to the yellow if if

561
00:38:40.240 --> 00:38:45.920
we want to like if we want to have that task on notion associated with a

562
00:38:45.920 --> 00:38:52.080
specific slice we could just add a slice property on notion and basically uses

563
00:38:52.080 --> 00:38:59.560
the same name or because then would kind of just for that we could add that later

564
00:38:59.560 --> 00:39:04.000
on I just want to because that's yeah you're really like what kind of in sync

565
00:39:04.000 --> 00:39:09.640
like what I was thinking about is exactly that like our structure of like

566
00:39:09.640 --> 00:39:15.920
the columns I think like a couple of some years ago or like months ago we had

567
00:39:15.920 --> 00:39:20.320
like discussions about naming like proper naming the column and I think we

568
00:39:20.320 --> 00:39:25.760
really have like good columns for the process like inbox is like something you

569
00:39:26.120 --> 00:39:31.640
client complained or you know and like shaping is like okay we decided that we

570
00:39:31.640 --> 00:39:35.080
should do something about it so let's research like what is even this thing

571
00:39:35.080 --> 00:39:41.020
what are the steps to reproduce and then move to like dev ready like the problem

572
00:39:41.020 --> 00:39:46.280
is clear and we can just go and like fix it and that lends itself well to like

573
00:39:46.280 --> 00:39:50.600
automation thing you know we can just like move it to shaping an agent picks

574
00:39:50.680 --> 00:39:57.680
it up like does the investigation moves it to dev ready and I mean that that's

575
00:39:57.680 --> 00:40:01.960
not like tight enough but also like that

576
00:40:00.000 --> 00:40:05.880
That's open like a lot of things because like we need to give like the agent like independent

577
00:40:05.880 --> 00:40:13.680
access to like read logs, read like digital ocean metrics, like the server crash or whatever,

578
00:40:13.680 --> 00:40:15.640
like click through the app.

579
00:40:15.640 --> 00:40:21.640
So it's kind of like there's a lot that could be done just on like that small thing.

580
00:40:21.640 --> 00:40:27.160
I would say like, I think there's a good hard line, like a wall to build here on the out

581
00:40:27.160 --> 00:40:32.440
of bounds, like just like the task grid is good for us for now.

582
00:40:32.440 --> 00:40:35.640
I think we're all looking at it like from an architectural standpoint, you're like,

583
00:40:35.640 --> 00:40:41.160
yeah, but there's tasks in a slice and there's tasks in a Kanban board, like tasks are tasks.

584
00:40:41.160 --> 00:40:43.680
So yes, let's totally merge it later.

585
00:40:43.680 --> 00:40:47.480
And like I could see a version where we like start up, because you may also have this thing

586
00:40:47.480 --> 00:40:53.560
where you like are in a project and I would grab just a random one here and we have a

587
00:40:53.560 --> 00:40:57.960
bunch of tasks like, and you're like, oh, actually I want to go deeper into this and

588
00:40:57.960 --> 00:41:02.360
maybe like I click into this and I can have the notion page that's associated with this

589
00:41:02.360 --> 00:41:03.360
down the road.

590
00:41:03.360 --> 00:41:07.080
I don't think it needs to be a now thing, but like that way it kind of gives, you could

591
00:41:07.080 --> 00:41:10.720
use whatever tool you want and you're not feeling like, what I don't want to do is end

592
00:41:10.720 --> 00:41:15.080
up with like a question of like, do I use the task grid or do I use the Kanban board?

593
00:41:15.080 --> 00:41:18.000
Like, cause they go like, you're down two different paths.

594
00:41:18.000 --> 00:41:19.200
And I like the idea of it.

595
00:41:19.200 --> 00:41:25.080
Like I could start task grid and then move it into like a different thing if I need to.

596
00:41:25.080 --> 00:41:28.760
But I think the, all we have to think of right now is like, let's just leave that off the

597
00:41:28.760 --> 00:41:35.640
table because it's safe to say that like, this is super not useful to an agent right

598
00:41:35.640 --> 00:41:36.640
now.

599
00:41:36.640 --> 00:41:42.300
Cause it's like, this just has like random thoughts of, you know, and it's all like whoever

600
00:41:42.300 --> 00:41:47.600
the developer is like, this really only means something to Janata who's building.

601
00:41:47.920 --> 00:41:49.880
I don't even know what this necessarily would be like.

602
00:41:49.880 --> 00:41:53.560
This just says, you know, and not all of these are just, some of them are like admin tasks.

603
00:41:53.560 --> 00:41:57.560
Some of them are like, get this thing, you know, fix that button.

604
00:41:57.560 --> 00:42:01.600
It's just enough information for us to remind ourselves and to not miss something when we're

605
00:42:01.600 --> 00:42:05.520
having a competition with a client, we can just quickly throw them on the board.

606
00:42:05.520 --> 00:42:10.760
So I think it's a great tool again, just, I think for this, we're actually wanting to

607
00:42:10.760 --> 00:42:15.680
go very deep on each task because each task is going to be like a thing that the agent

608
00:42:15.680 --> 00:42:18.160
works on and needs a lot of information.

609
00:42:18.160 --> 00:42:21.800
And then even if we only give it a little information, it needs a place to put lots

610
00:42:21.800 --> 00:42:25.280
of information and a good plan.

611
00:42:25.280 --> 00:42:26.280
So I'm good.

612
00:42:26.280 --> 00:42:27.280
I'm good with that for now.

613
00:42:27.280 --> 00:42:31.360
And just, we'll just scope it to a different project or else you have to make a lot of

614
00:42:31.360 --> 00:42:32.360
design decisions.

615
00:42:32.360 --> 00:42:37.640
I'd link Lucian is what you're saying is like, do we go like, and even then Janata was like,

616
00:42:37.640 --> 00:42:40.440
let's make like a way for us to like add slices in Notion.

617
00:42:40.440 --> 00:42:45.480
And then so I specifically said like no accessing task grid in Notion, cause I already, I did

618
00:42:45.480 --> 00:42:48.120
think about that when I was building it.

619
00:42:48.120 --> 00:42:51.040
And it kind of goes down like, it's a weird thing.

620
00:42:51.040 --> 00:42:55.040
It doesn't quite match like the way that, you know, if you haven't, cause you can label

621
00:42:55.040 --> 00:42:56.760
a slice anything.

622
00:42:56.760 --> 00:43:01.120
So just keeping them track so they don't have like certain slices aren't showing up in the

623
00:43:01.120 --> 00:43:05.320
wrong projects and tasks anyway.

624
00:43:05.320 --> 00:43:06.960
I think that's good.

625
00:43:06.960 --> 00:43:12.080
Is there anything else problem-wise we should think of?

626
00:43:12.080 --> 00:43:30.160
One interesting problem to add is about like, no, actually that's good.

627
00:43:30.160 --> 00:43:36.280
It's probably for another shape in the, what I was going to say that this is good.

628
00:43:36.280 --> 00:43:39.400
I'm just curious what it is anyway.

629
00:43:39.400 --> 00:43:47.040
It was about like, because one of the contents that we have, like one of the pieces of data

630
00:43:47.040 --> 00:43:51.680
that we have in our system is the communication with the client.

631
00:43:51.680 --> 00:43:59.120
Like the reports, everything they send, their complaints about what we did and it's all

632
00:43:59.120 --> 00:44:02.600
linked on different channels.

633
00:44:02.600 --> 00:44:07.520
But I think that would be a different project because what you need probably is something

634
00:44:07.640 --> 00:44:13.400
to first kind of grab everything and everything, like organize it on the same place.

635
00:44:13.400 --> 00:44:18.920
And then we need probably some layer of a agent that would help us filter this out and

636
00:44:18.920 --> 00:44:23.360
then create tasks that would be executed in a flow.

637
00:44:23.360 --> 00:44:28.000
But that would be like a separate piece of the workflow, I imagine.

638
00:44:28.000 --> 00:44:29.000
One, okay.

639
00:44:29.000 --> 00:44:30.000
Yes.

640
00:44:30.000 --> 00:44:37.280
So maybe like client communication, like with Slack and email and all of that will like

641
00:44:38.040 --> 00:44:42.320
And just, I don't mean like agent answering customer, I just mean like

642
00:44:42.320 --> 00:44:45.120
Just context, building the context.

643
00:44:45.120 --> 00:44:46.120
Yeah.

644
00:44:46.120 --> 00:44:52.000
But so one thing that we can do though, is all of the comments are synced from Notion

645
00:44:52.000 --> 00:44:53.280
back to the dashboard.

646
00:44:53.280 --> 00:44:57.680
So we actually do have like every single comment is in a comment database.

647
00:44:57.680 --> 00:44:59.760
So worst case.

648
00:45:00.000 --> 00:45:03.300
Like you could screenshot the Slack message,

649
00:45:03.300 --> 00:45:05.320
you could copy paste the message.

650
00:45:05.320 --> 00:45:09.040
And what's cool is it actually creates over here

651
00:45:09.040 --> 00:45:10.940
like a thread, right?

652
00:45:10.940 --> 00:45:12.740
Of like everything that's being said.

653
00:45:15.460 --> 00:45:18.100
If I send an image, it will start?

654
00:45:18.100 --> 00:45:19.420
It should show the image, yeah.

655
00:45:19.420 --> 00:45:20.260
Let me find it.

656
00:45:20.260 --> 00:45:21.100
Nice, that's perfect.

657
00:45:21.100 --> 00:45:22.260
It even shows the video.

658
00:45:22.260 --> 00:45:23.740
If you show like a Loom video,

659
00:45:23.740 --> 00:45:25.640
it like puts a little player in there.

660
00:45:25.640 --> 00:45:27.060
Nice, that's so cool.

661
00:45:27.060 --> 00:45:29.780
But yeah, you would need to extract, you know, the text,

662
00:45:29.780 --> 00:45:31.620
but if an LLM ran into an image,

663
00:45:31.620 --> 00:45:33.340
it would know what to do with the image.

664
00:45:33.340 --> 00:45:36.200
Yeah, every local with you,

665
00:45:36.200 --> 00:45:39.340
that basically it's like a extractor of content.

666
00:45:39.340 --> 00:45:42.420
And for a video, it does like every five seconds,

667
00:45:42.420 --> 00:45:44.580
it screenshots and adds transcription.

668
00:45:44.580 --> 00:45:47.300
So like the model knows when I send a video,

669
00:45:47.300 --> 00:45:49.620
like this is a video about this feature

670
00:45:49.620 --> 00:45:52.900
and does this kind of transcription.

671
00:45:52.900 --> 00:45:55.620
The other thing that came up yesterday was like,

672
00:45:55.620 --> 00:45:58.880
we need, we don't really have like,

673
00:45:58.920 --> 00:46:03.920
I'll just say like an LLM friendly, like-

674
00:46:05.880 --> 00:46:07.080
Knowledge base.

675
00:46:07.080 --> 00:46:11.800
Yeah, knowledge base or context, you know,

676
00:46:11.800 --> 00:46:14.620
of a like a particular project.

677
00:46:14.620 --> 00:46:17.040
So it could be cool if over here,

678
00:46:17.040 --> 00:46:19.640
we could have a way to like add resources

679
00:46:19.640 --> 00:46:22.440
to a client level.

680
00:46:22.440 --> 00:46:23.480
That's the trick.

681
00:46:23.480 --> 00:46:27.440
It's not a project level.

682
00:46:27.960 --> 00:46:29.640
It's something that needs to be at the client level,

683
00:46:29.640 --> 00:46:30.480
you know, it's-

684
00:46:30.480 --> 00:46:33.020
It could be the equivalent of an area

685
00:46:33.020 --> 00:46:35.000
in the paramethodology.

686
00:46:35.000 --> 00:46:38.040
It's something that if we don't have an end in mind,

687
00:46:38.040 --> 00:46:41.000
like clients can stay as with, hopefully forever.

688
00:46:41.000 --> 00:46:42.560
And-

689
00:46:42.560 --> 00:46:43.800
Just a little parenthesis,

690
00:46:43.800 --> 00:46:45.720
this kind of like in solution space,

691
00:46:45.720 --> 00:46:48.320
maybe not the solution for this, or maybe it is,

692
00:46:48.320 --> 00:46:51.920
but like area is like, you could have like credentials

693
00:46:51.920 --> 00:46:53.720
and also like executors, you know,

694
00:46:53.720 --> 00:46:57.000
like a agent that reads logs, you know.

695
00:46:57.760 --> 00:46:59.280
And you can like manage access,

696
00:46:59.280 --> 00:47:02.400
like let's say, Junaid, you're working on X tech

697
00:47:02.400 --> 00:47:03.960
and like no one else is.

698
00:47:03.960 --> 00:47:06.560
So maybe you have like the API key to Innovo

699
00:47:06.560 --> 00:47:09.220
that knows that you're working on X tech

700
00:47:09.220 --> 00:47:12.540
and you see et cetera, everything.

701
00:47:12.540 --> 00:47:14.360
You're not like admin, so you don't see billing

702
00:47:14.360 --> 00:47:15.540
and that's it.

703
00:47:15.540 --> 00:47:18.600
So that would be part of like area, you know,

704
00:47:18.600 --> 00:47:20.480
in my mind, like the agents,

705
00:47:20.480 --> 00:47:24.020
like that read logs or whatever.

706
00:47:25.080 --> 00:47:26.400
Nice, that's cool.

707
00:47:26.400 --> 00:47:30.040
So probably, yeah, I mean,

708
00:47:30.040 --> 00:47:32.440
like this does already have in the dashboard,

709
00:47:32.440 --> 00:47:35.600
probably the CLI or, I mean,

710
00:47:35.600 --> 00:47:37.400
we are literally talking solution now,

711
00:47:37.400 --> 00:47:42.400
but I mean, the CLI probably will need some form of logging

712
00:47:43.000 --> 00:47:44.360
or some stuff, right?

713
00:47:44.360 --> 00:47:49.360
So it knows like I am the user that's accessing this data.

714
00:47:49.600 --> 00:47:51.080
We know it's Junaid, yeah, for sure.

715
00:47:51.080 --> 00:47:51.920
Perfect.

716
00:47:51.920 --> 00:47:52.760
Yeah.

717
00:47:52.760 --> 00:47:53.640
That's nice.

718
00:47:53.640 --> 00:47:55.200
Yeah, that will leave us space

719
00:47:55.200 --> 00:47:57.240
for doing some very cool stuff.

720
00:47:57.240 --> 00:48:02.240
Cool, so let's ask the source here.

721
00:48:02.920 --> 00:48:03.880
Let's get some good questions.

722
00:48:03.880 --> 00:48:07.360
What feels, who feels this pain the most?

723
00:48:07.360 --> 00:48:09.680
It's us, everyone on the team.

724
00:48:09.680 --> 00:48:10.520
Yeah.

725
00:48:10.520 --> 00:48:11.560
Yeah, it's everyone.

726
00:48:12.760 --> 00:48:14.160
Let's just do two.

727
00:48:14.160 --> 00:48:15.760
Why do you even give me like-

728
00:48:15.760 --> 00:48:17.600
Yeah, I mean, this is one thing about-

729
00:48:17.600 --> 00:48:19.680
You mean nothing to us.

730
00:48:19.680 --> 00:48:20.520
Yeah, like.

731
00:48:21.520 --> 00:48:25.360
AI, okay, so what's the why now?

732
00:48:25.360 --> 00:48:26.920
What changed recently?

733
00:48:27.920 --> 00:48:29.520
Team is actively building agents now

734
00:48:29.520 --> 00:48:31.360
and each person is reinventing the wheel.

735
00:48:31.360 --> 00:48:32.680
I think that's good.

736
00:48:32.680 --> 00:48:33.520
Yeah.

737
00:48:33.520 --> 00:48:35.400
Breaking the shallow task grid

738
00:48:35.400 --> 00:48:36.920
and notion disconnect is causing,

739
00:48:36.920 --> 00:48:38.040
that's not really a problem.

740
00:48:38.040 --> 00:48:40.960
No, I think the problem is first one.

741
00:48:40.960 --> 00:48:43.200
When you say read and write to notion tasks,

742
00:48:43.200 --> 00:48:46.120
is the core, let me make this bigger for you guys.

743
00:48:47.000 --> 00:48:50.920
Is the core, when you say read and write notion,

744
00:48:50.920 --> 00:48:53.760
is the core, needs an API that agents can call

745
00:48:53.760 --> 00:48:55.920
or is it that about improving what humans see

746
00:48:55.920 --> 00:48:57.480
in the dashboard UI?

747
00:48:57.480 --> 00:48:59.880
I think it's just the MCP.

748
00:48:59.880 --> 00:49:01.600
Yeah, calling agents.

749
00:49:01.600 --> 00:49:03.600
And not sure, and I mean like,

750
00:49:03.600 --> 00:49:07.640
doesn't even need to be an MCP like, but-

751
00:49:07.640 --> 00:49:10.880
Yeah, I'll just say API and dashboard,

752
00:49:10.880 --> 00:49:13.240
agents need access and the dashboard needs to show

753
00:49:13.280 --> 00:49:14.480
because I think-

754
00:49:14.480 --> 00:49:16.120
Show richer tasks, yeah.

755
00:49:16.120 --> 00:49:18.160
Yeah, because you will need to see,

756
00:49:18.160 --> 00:49:20.000
you'll need to see the tasks being done.

757
00:49:20.000 --> 00:49:22.680
I don't know, I don't think dashboard really matters

758
00:49:22.680 --> 00:49:25.320
because we're just focusing on reactive, right?

759
00:49:25.320 --> 00:49:27.800
So it's just about moving them forward.

760
00:49:27.800 --> 00:49:30.320
Yes, the cool magic trick I want though, Lucian,

761
00:49:30.320 --> 00:49:32.160
is I wanna wake up and I wanna like have this board

762
00:49:32.160 --> 00:49:34.240
like we saw in the video where like,

763
00:49:34.240 --> 00:49:35.840
there's like all the columns that I'm dragging.

764
00:49:35.840 --> 00:49:37.280
I'm like, look at all my agents working

765
00:49:37.280 --> 00:49:39.480
because what could happen is like,

766
00:49:39.480 --> 00:49:40.960
here's what's crazy is like,

767
00:49:41.000 --> 00:49:43.280
Janata could be like jumping in

768
00:49:43.280 --> 00:49:45.080
and doing some tasks in there.

769
00:49:45.080 --> 00:49:45.920
Either he signed like,

770
00:49:45.920 --> 00:49:48.240
he's two or three agents are working on one part of it.

771
00:49:48.240 --> 00:49:49.880
I could be working on two or three other tasks,

772
00:49:49.880 --> 00:49:52.280
but like, we'd all have kind of a live view of like,

773
00:49:52.280 --> 00:49:53.320
where all these things are going.

774
00:49:53.320 --> 00:49:55.040
Because that central hub,

775
00:49:55.040 --> 00:49:57.480
and that way it's not like we're locked into his way

776
00:49:57.480 --> 00:49:58.760
or my way.

777
00:49:58.760 --> 00:50:00.360
It just lets us like experiment.

778
00:50:00.000 --> 00:50:01.680
That would be cool. That would be cool.

779
00:50:02.200 --> 00:50:07.120
Also, it's probably also because we have the Kanban board built and it's already

780
00:50:07.120 --> 00:50:11.040
linked to Notion. So like when you drag things around in the Kanban,

781
00:50:11.080 --> 00:50:12.720
it updates the status in Notion.

782
00:50:12.720 --> 00:50:16.960
We can easily have that just duplicate it for the task level.

783
00:50:17.600 --> 00:50:20.080
We can create a, um,

784
00:50:20.720 --> 00:50:25.240
I think probably the best solution would be a hook,

785
00:50:25.280 --> 00:50:29.800
like a harnesses hook that would connect to Codex or to the cloud.

786
00:50:30.240 --> 00:50:34.800
But the idea that is that when you pick up a task with that agent,

787
00:50:34.800 --> 00:50:39.800
like when you say, Oh, I'm working on this, like, then it would, uh,

788
00:50:40.720 --> 00:50:45.720
update that, that, uh, task with your, uh,

789
00:50:46.280 --> 00:50:50.600
user, but also maybe identifier for the agent,

790
00:50:50.600 --> 00:50:55.320
like maybe the session ID or like anything that we could identify the agents

791
00:50:55.720 --> 00:50:59.080
locally, because then I can go back and see like, okay,

792
00:50:59.080 --> 00:51:03.600
I worked on this task and this could even be like an array of sessions.

793
00:51:03.600 --> 00:51:08.600
Like every time I connected to this task with agents,

794
00:51:08.640 --> 00:51:11.560
the, we track the session that we are using,

795
00:51:11.960 --> 00:51:16.120
because then I can use it to, to debug it locally. Like, Oh, okay. I,

796
00:51:16.120 --> 00:51:20.480
I worked on this in this session and I can go there and see, uh,

797
00:51:20.520 --> 00:51:25.000
it says metadata, metadata field or yeah.

798
00:51:25.000 --> 00:51:28.200
It's not like a minimal structure, but like flexible structure I think would be

799
00:51:28.240 --> 00:51:30.480
better. It's like everyone be able to.

800
00:51:31.160 --> 00:51:36.160
Perfect. So we have like this agent metadata of like, uh,

801
00:51:36.560 --> 00:51:41.560
history of the test and we can use it freely because I think like the next step

802
00:51:43.280 --> 00:51:46.120
would be for this, like the next, next,

803
00:51:46.120 --> 00:51:49.280
maybe would be to have a, uh,

804
00:51:49.320 --> 00:51:54.320
VPS where you can basically in from our CLI we can decide,

805
00:51:55.120 --> 00:51:55.680
Hey,

806
00:51:55.680 --> 00:52:00.680
I will work on this on my local machine or I work on this on the VPS.

807
00:52:01.800 --> 00:52:03.400
And when you send to the VPS,

808
00:52:03.440 --> 00:52:07.360
it's basically all of them reports to the same dashboard,

809
00:52:07.360 --> 00:52:10.440
meaning they will update and report the same stuff. Yeah.

810
00:52:10.520 --> 00:52:12.440
Just like the mission control does,

811
00:52:12.760 --> 00:52:17.480
but you can choose between running locally or on the Innovo VPS.

812
00:52:17.920 --> 00:52:22.920
And we have this one place with all the security checks and everything that we

813
00:52:23.560 --> 00:52:26.000
can kind of send our agents to work together,

814
00:52:26.120 --> 00:52:28.440
but we can also work locally if we want to.

815
00:52:29.720 --> 00:52:32.400
I think it's cool. I mean the, yeah,

816
00:52:32.640 --> 00:52:36.040
I think if we focus on this little like hub part and the data in and out

817
00:52:36.040 --> 00:52:40.760
problem, that's what's probably the bottleneck. Cause then like you could try,

818
00:52:41.200 --> 00:52:44.080
like I said, you could do so many variations of this and it doesn't,

819
00:52:44.360 --> 00:52:48.520
we have to reinvent the, we have to rebuild this central hub. Um, like,

820
00:52:48.640 --> 00:52:51.720
you know, we always going to have projects, we're always going to have tasks,

821
00:52:51.720 --> 00:52:55.680
we're always going to have clients. So like that interchanges can be fine. Um,

822
00:52:55.680 --> 00:52:57.840
I just want to point out how smart Claude is like, Hey,

823
00:52:57.840 --> 00:53:00.080
would you like me to write this to the dashboard for you?

824
00:53:02.280 --> 00:53:06.560
It said, uh, but let's go back to the plan here. Um,

825
00:53:07.400 --> 00:53:10.520
it said we're experiencing the AI agents. Meanwhile,

826
00:53:10.520 --> 00:53:14.280
task grid is a single line to get some of the context. Your age, I agent,

827
00:53:14.360 --> 00:53:18.080
I agents can't access another data without oops, sorry, I shouldn't double click.

828
00:53:18.520 --> 00:53:21.920
Um, there's no audit trail, no depth to it.

829
00:53:21.920 --> 00:53:25.360
Context switching over at the team juggles between notion dashboard and various

830
00:53:25.360 --> 00:53:29.800
agents. Sure. We're actively adopting different workflows. Okay.

831
00:53:29.800 --> 00:53:34.800
So the team members can plug into a project and task data with their own agent

832
00:53:35.520 --> 00:53:40.040
without building custom integrations. It's agent to agent agnostic.

833
00:53:40.800 --> 00:53:44.200
The dashboard can source a truth tasks and that syncs with notion.

834
00:53:44.240 --> 00:53:49.080
All read and writes by humans or AI agents are logged with attribution so you

835
00:53:49.080 --> 00:53:51.240
can see who or what changed for each task.

836
00:53:52.080 --> 00:53:56.080
Projects have an LLM friendly knowledge base framing docs tasks.

837
00:53:56.080 --> 00:54:00.120
We already have some of that. Um, but yeah, there's additional resources.

838
00:54:00.160 --> 00:54:02.680
This would be at the, at the client level.

839
00:54:03.160 --> 00:54:07.240
I don't think it would be at the project level, but maybe they could,

840
00:54:07.320 --> 00:54:09.960
I guess they could have resources attached either. Yeah.

841
00:54:09.960 --> 00:54:14.960
I'm going to ignore the scope. We're not standardizing stuff.

842
00:54:15.320 --> 00:54:17.240
We're changing, we're not changing the task grid.

843
00:54:17.600 --> 00:54:21.120
We're not messing with task grid and notion, not dealing with communication.

844
00:54:21.120 --> 00:54:26.120
We'll deal with notion comments though. We'll include that. Um, you know,

845
00:54:26.120 --> 00:54:29.160
we didn't really list that up here in the outcomes. Did we say that?

846
00:54:30.120 --> 00:54:31.760
I think we missed that, that, um,

847
00:54:32.360 --> 00:54:36.800
there's task and the comment chat needs to be part of the context. Uh,

848
00:54:36.840 --> 00:54:41.440
no notion right backs for task grid. That's fine. No, you face for AI.

849
00:54:42.440 --> 00:54:46.680
Yeah. This is just going to be like, um, there anything else?

850
00:54:46.720 --> 00:54:50.440
The one thing I want to like kind of, uh,

851
00:54:50.640 --> 00:54:55.480
elicit a bit more crispiness because it's like a bit blurry between like two

852
00:54:55.480 --> 00:54:59.200
problems. One is like managing knowledge.

853
00:55:00.000 --> 00:55:05.340
Um, and like the context for tasks and the other is like the bottleneck of

854
00:55:05.340 --> 00:55:07.980
having like multiple tasks all at once.

855
00:55:08.920 --> 00:55:13.280
And, um, some of them are like, for example, if like, we want to tackle

856
00:55:13.280 --> 00:55:19.640
like the problem of bottlenecks, then we got to do like the, um, maybe a hosted

857
00:55:20.040 --> 00:55:25.160
VPS that like takes multiple tasks or like a part of the task lifecycle,

858
00:55:25.160 --> 00:55:26.560
just investigation, for example.

859
00:55:27.520 --> 00:55:31.160
Or if like the problem of the one attack is like more knowledge management and

860
00:55:31.160 --> 00:55:36.720
like allowing your local thing to talk to like the task, uh, that's like

861
00:55:36.720 --> 00:55:38.760
slightly different solution space.

862
00:55:39.000 --> 00:55:39.640
Does that make sense?

863
00:55:40.280 --> 00:55:40.800
Totally.

864
00:55:41.160 --> 00:55:48.440
I think, I think probably the second part, I think is the, in my view would

865
00:55:48.440 --> 00:55:55.360
be, is the one that needs to focus first, like on organizing the data and

866
00:55:55.360 --> 00:56:00.000
making it accessible to our local workflows, because then we will use it

867
00:56:00.000 --> 00:56:02.400
and we will find the best ways to use it.

868
00:56:02.600 --> 00:56:10.600
And then we can probably like streamline this into a, uh, shared space in a VPS,

869
00:56:10.600 --> 00:56:17.280
for instance, in a set of a cloud or codex agents that are always on.

870
00:56:17.640 --> 00:56:23.840
And you can just say, okay, uh, spawn this agent, which would basically start a

871
00:56:23.840 --> 00:56:27.880
cloud session with that agent context loaded on the VPS.

872
00:56:28.280 --> 00:56:31.320
And then you pick a task and you start a run.

873
00:56:31.720 --> 00:56:36.480
And what that will do is you pick the task from our, from our knowledge base.

874
00:56:36.720 --> 00:56:41.960
And the run is basically what we see in a single terminal window is like the whole

875
00:56:41.960 --> 00:56:47.600
stream of work and all the two colleagues that will represent a run on our server.

876
00:56:47.800 --> 00:56:52.600
And I think that's kind of, it's not a complicated structure to build.

877
00:56:52.600 --> 00:56:56.800
I think like, to be honest, probably we just need a script where when you spawn a

878
00:56:56.800 --> 00:56:59.320
agent, it creates its own workspace.

879
00:56:59.320 --> 00:57:05.280
It has its own safe credentials, so it doesn't, it can't like merge to the, to

880
00:57:05.280 --> 00:57:06.520
the branch or anything like that.

881
00:57:06.520 --> 00:57:09.160
We can create this safe, uh, setup.

882
00:57:09.280 --> 00:57:13.520
It can even like be, uh, its own container, like inside the VPS.

883
00:57:14.080 --> 00:57:15.200
Um, and.

884
00:57:15.200 --> 00:57:16.760
We can, that's a good question.

885
00:57:16.760 --> 00:57:23.000
Like, are we, uh, what is the, we need almost need like a, and like a skill or a

886
00:57:23.000 --> 00:57:30.120
file that all agents will need to have context of like where stuff is my, every

887
00:57:30.120 --> 00:57:33.080
time I post something, please leave a comment when work is like, do we need

888
00:57:33.080 --> 00:57:36.440
something where it's like, as if we're training the employee handbook of like,

889
00:57:36.440 --> 00:57:40.400
Hey, all these army of agents that are about to show up, like we have standards.

890
00:57:40.400 --> 00:57:43.840
Like when you change this, you need to leave a comment in notion, or if you do

891
00:57:43.840 --> 00:57:48.200
this, like make that like when, um, I don't know, just, just to make sure that

892
00:57:48.200 --> 00:57:49.360
we're getting stuff in and out.

893
00:57:49.360 --> 00:57:52.520
Like it doesn't start working on the task and forget to change the status.

894
00:57:52.720 --> 00:57:54.680
Like it needs to know some of the rules.

895
00:57:56.080 --> 00:58:01.360
So the best way I know to force this is to do something like they are doing with

896
00:58:01.360 --> 00:58:04.960
this, uh, GitHub, you, you should try this.

897
00:58:04.960 --> 00:58:06.120
It's very interesting.

898
00:58:06.120 --> 00:58:10.840
It has comments like map your code base and has specific sequences

899
00:58:10.840 --> 00:58:12.240
of comments that it follows.

900
00:58:12.240 --> 00:58:17.560
So if you do, we can do something like we can start with face slash framing and it

901
00:58:17.560 --> 00:58:21.080
will call automatically days like shaping when we finished.

902
00:58:21.080 --> 00:58:23.760
And then it will start working on it on parallel.

903
00:58:23.760 --> 00:58:31.040
Like we can, um, make, uh, chain, uh, calls of commands and workflows that are

904
00:58:31.040 --> 00:58:33.160
running on the harnesses on there.

905
00:58:33.160 --> 00:58:37.400
And you can, I think this one is just for cloud code, or I don't know if it's

906
00:58:37.400 --> 00:58:42.840
updated for codex already, but, uh, it making one for codex, just like translating

907
00:58:42.840 --> 00:58:45.160
to the API that codex use.

908
00:58:45.640 --> 00:58:53.680
So it's very, you, you basically place your harnesses, your harness on a guardrail,

909
00:58:53.760 --> 00:58:57.360
like on a specific flow that it has always to follow.

910
00:58:57.360 --> 00:59:02.960
So we can adopt like, Oh, if I'm working on a novel project, then we will be using

911
00:59:02.960 --> 00:59:11.280
the, uh, in oval, uh, GSD, which would follow our, our, uh, workflow and hook by

912
00:59:11.280 --> 00:59:14.360
the end where it's always update on the dashboard.

913
00:59:14.360 --> 00:59:15.520
Like, that's what we can do.

914
00:59:15.520 --> 00:59:18.080
Like it was a day to draw a sketch from there.

915
00:59:18.080 --> 00:59:19.320
It will know where things is.

916
00:59:19.320 --> 00:59:22.400
But is, is it, uh, where does it pull it?

917
00:59:22.440 --> 00:59:23.320
Like, where is it stored?

918
00:59:23.320 --> 00:59:25.600
Is it stored in the dashboard and it pulls it down?

919
00:59:25.800 --> 00:59:27.360
No, it creates all locally.

920
00:59:27.360 --> 00:59:32.840
When you run, uh, the command, when you install this, this, uh, tool, it creates

921
00:59:32.840 --> 00:59:36.960
like on the dot, it sets up your dot cloud, uh, locally.

922
00:59:37.000 --> 00:59:41.280
So you can get it from the, it's got to have somewhere it's pulling it from

923
00:59:41.280 --> 00:59:48.200
centrally, it's a, it's a, it's a, um, I think it's a node package, like when you

924
00:59:48.200 --> 00:59:50.560
install it, like it's all into the dashboard.

925
00:59:51.120 --> 00:59:52.480
So we put it on our dashboard.

926
00:59:52.480 --> 00:59:59.760
Uh, no, I mean, this, uh, I'm, uh, this one, the, the, this, uh, Gatsby.

927
01:00:00.000 --> 01:00:06.480
done one it's it's all it doesn't it it's all self-contained so all the when you run the node

928
01:00:06.480 --> 01:00:13.840
command to install this it will install all the sequence of commands and everything on your cloud

929
01:00:13.840 --> 01:00:21.920
files so it's basically a way of placing it on on rails we can have this uh in in our dashboard for

930
01:00:21.920 --> 01:00:28.720
our solution if you want but we need we need a place where we can like adjust that slightly just

931
01:00:28.720 --> 01:00:32.240
so that we're all picking from the same i mean because i think what you're saying is like this

932
01:00:32.240 --> 01:00:37.920
is a good framework just like that standardizes it but we may want to just like tweak it so

933
01:00:37.920 --> 01:00:43.680
there's some rules yeah we need our own version of it like that's what i mean that this is just

934
01:00:43.680 --> 01:00:50.240
a reference of how we can implement this in a way that our agents like our innoval agents

935
01:00:50.960 --> 01:00:58.640
will always know how to use the novel tools this can be done in a simpler way using like just

936
01:00:58.640 --> 01:01:06.400
cloud.md or agents.md and a set of rules and stuff but i think this tool is a lot more

937
01:01:07.200 --> 01:01:14.160
you place more strictly uh you have to follow it the model has to follow it more closely

938
01:01:14.240 --> 01:01:22.320
it's it's more um yeah like we could have like a novo framer like framing piece and then like

939
01:01:22.320 --> 01:01:27.760
drive debugger on a novo like transcoder debugger like you know we could have specific things that

940
01:01:27.760 --> 01:01:33.200
can be shared across projects and it's very easy to install because you just install at the project

941
01:01:33.200 --> 01:01:39.440
level so it doesn't mess with all your cloud setup it just installs at that project so it creates a

942
01:01:39.760 --> 01:01:45.360
cloud at the project level and inside that project has all the setup with you need with

943
01:01:45.360 --> 01:01:51.440
all the agents with all the workflows with all the commands and we would just i'm understanding

944
01:01:51.440 --> 01:01:55.760
it's just committed at the project level because we're not managing like hundreds we have like

945
01:01:55.760 --> 01:02:01.120
you know we might get like a new custom client every like few months and then we just like

946
01:02:01.120 --> 01:02:07.600
kind of copy the is it the good like skills you know it's because the repo right it's going to

947
01:02:07.680 --> 01:02:13.440
like the it would be at the regular level yeah i got you now but i've been doing this but like

948
01:02:13.440 --> 01:02:22.000
if we have a command line interface i want to step back to something else here um i agree like uh

949
01:02:22.000 --> 01:02:27.200
janelle you answered my question i was wondering like you know do we do kind of parallelization

950
01:02:27.200 --> 01:02:32.880
or knowledge management and i think knowledge management management makes a lot of sense

951
01:02:32.880 --> 01:02:37.280
because it's like the foundation also that could be like an outcome it's a foundation for us to

952
01:02:37.520 --> 01:02:45.040
have our vps that like intelligently does stuff but like for this project it's it would be easy

953
01:02:45.040 --> 01:02:48.880
to get carried away so like how would we know that we're done you know like where would we

954
01:02:49.840 --> 01:02:56.640
kind of say like oh yes we fit in like solve the knowledge management agent connection piece

955
01:03:00.080 --> 01:03:05.200
uh in my right an outcome would be like you could you could basically kick off a session

956
01:03:06.000 --> 01:03:12.560
pull down all the context um for a particular task or something or in my flow would be like

957
01:03:12.560 --> 01:03:19.680
you'd you'd pull up like a few tasks and like you know have it maybe process it to to like

958
01:03:20.400 --> 01:03:25.200
plan those tasks and then you could fire off or execute them or whatever i don't know if i want

959
01:03:25.200 --> 01:03:31.360
to like prescribe the the flow too much but i would say like i don't have to go to notion and

960
01:03:31.360 --> 01:03:36.560
then the dashboard and then like some something in slack like ideally we're kind of the the

961
01:03:37.280 --> 01:03:43.200
habit change behavior here would have us to have to be like keeping a lot of notes in in notion

962
01:03:43.200 --> 01:03:48.960
comments which we kind of do already um but like if we wanted to weigh in on stuff or copy a bunch

963
01:03:48.960 --> 01:03:55.280
of text we could just paste it into the notion comments for more context but that's how i would

964
01:03:55.280 --> 01:04:00.880
think this is done when like bridging can spin up a terminal and like pull down a task work on it

965
01:04:00.960 --> 01:04:09.040
kick it back in a very simple model now you could then go in multi like agent mode with like three

966
01:04:09.040 --> 01:04:12.880
or four of these things running at the same time or like john was saying like i have something

967
01:04:12.880 --> 01:04:18.400
that's running on my bps this is running locally this is running wherever um that's how i would

968
01:04:18.400 --> 01:04:25.200
kind of see this as being done yeah i like that that that now becomes like extremely sharp because

969
01:04:25.760 --> 01:04:30.640
we're kind of like shifting like you do like everything that you're doing and you keep

970
01:04:30.640 --> 01:04:35.040
developing your own workflow but just the only connection you don't have to go to notion anymore

971
01:04:35.040 --> 01:04:41.120
you can just like tell your your agent like do the investigation yourself and then write back

972
01:04:41.120 --> 01:04:46.320
like automatically but it's not whatever uh janata's drawing so i'm curious what he's drawing

973
01:04:46.880 --> 01:04:51.360
because the dotion projects and tasks would be like underneath the dashboard but what do you

974
01:04:51.360 --> 01:04:59.840
think uh yeah like they are basically the yeah it's access the same the same information but like

975
01:05:00.000 --> 01:05:04.960
It's like this, so.

976
01:05:04.960 --> 01:05:07.120
But then the question becomes like,

977
01:05:07.120 --> 01:05:10.280
why not just like Notion MCP?

978
01:05:10.280 --> 01:05:12.160
Directly, yeah, that's what I'm,

979
01:05:12.160 --> 01:05:16.160
like, what are we gaining from this extra layer, right?

980
01:05:16.160 --> 01:05:20.820
What are we integrating to this CLI to make it easier to?

981
01:05:22.880 --> 01:05:24.680
A Notion doesn't actually work,

982
01:05:24.680 --> 01:05:28.800
but what I've seen, like, it's not very fast for one,

983
01:05:28.800 --> 01:05:31.080
like, getting data in and out.

984
01:05:31.080 --> 01:05:35.560
And I've, and the MCP's not great.

985
01:05:35.560 --> 01:05:36.840
I think, because one thing,

986
01:05:36.840 --> 01:05:38.360
if you can go through the dashboard,

987
01:05:38.360 --> 01:05:41.120
we can link in those client knowledge stuff.

988
01:05:41.120 --> 01:05:44.400
We could link in, like, general things about the task,

989
01:05:44.400 --> 01:05:45.360
like time tracking.

990
01:05:45.360 --> 01:05:46.200
We could link, you know,

991
01:05:46.200 --> 01:05:48.600
it could have different questions or context, comments.

992
01:05:48.600 --> 01:05:50.180
I mean, you'd have the comments in the Notion part,

993
01:05:50.180 --> 01:05:54.680
but I also, if we're building something kind of the future,

994
01:05:54.680 --> 01:05:56.120
I'd love the idea of it

995
01:05:56.120 --> 01:05:59.160
not being totally locked in on Notion.

996
01:06:00.040 --> 01:06:02.440
I do think we're gonna outgrow Notion at some point

997
01:06:02.440 --> 01:06:03.440
with this.

998
01:06:03.440 --> 01:06:05.640
At some point, we'll be writing projects and tasks

999
01:06:05.640 --> 01:06:07.040
directly to the super base,

1000
01:06:07.040 --> 01:06:09.360
but the dashboard and just working at it there,

1001
01:06:09.360 --> 01:06:12.740
we may not need the Notion view.

1002
01:06:12.740 --> 01:06:13.580
I am using Notion-

1003
01:06:13.580 --> 01:06:16.880
We can be tool agnostic then.

1004
01:06:18.040 --> 01:06:19.680
Yeah, I mean, I don't wanna, like,

1005
01:06:19.680 --> 01:06:21.720
be, like, scared of it and not use it,

1006
01:06:21.760 --> 01:06:22.600
but we could,

1007
01:06:25.640 --> 01:06:26.800
yeah, I mean, the only other thing,

1008
01:06:26.800 --> 01:06:28.280
like, if you wanna sort of draw it,

1009
01:06:28.280 --> 01:06:29.680
there is that happening,

1010
01:06:29.680 --> 01:06:32.160
but there's, you know, toggles in here.

1011
01:06:33.760 --> 01:06:34.800
And there's also,

1012
01:06:38.160 --> 01:06:39.560
you know, we also have, like,

1013
01:06:39.560 --> 01:06:42.380
Mercury and, like, all the payment information as well,

1014
01:06:42.380 --> 01:06:43.520
so you can kind of see.

1015
01:06:44.640 --> 01:06:45.480
Like, it'd be cool.

1016
01:06:45.480 --> 01:06:47.000
You could actually ask it, like,

1017
01:06:47.000 --> 01:06:49.200
like, how much am I gonna make this month?

1018
01:06:49.560 --> 01:06:50.560
That's cool.

1019
01:06:52.320 --> 01:06:53.280
No, that's gonna be a problem,

1020
01:06:53.280 --> 01:06:55.240
because it may not be,

1021
01:06:55.240 --> 01:06:58.000
I'm gonna go and, like, ask the,

1022
01:06:59.280 --> 01:07:00.120
ask what-

1023
01:07:00.120 --> 01:07:01.600
Yeah, because, like, I can,

1024
01:07:01.600 --> 01:07:02.440
it's difficult because, like,

1025
01:07:02.440 --> 01:07:05.200
I can ask how much solution we'll make this month.

1026
01:07:05.200 --> 01:07:07.520
Well, it won't, because technically you'll have a,

1027
01:07:07.520 --> 01:07:08.640
you'll have your own token,

1028
01:07:08.640 --> 01:07:10.840
so we wouldn't know who it is,

1029
01:07:10.840 --> 01:07:12.840
so it wouldn't be quite that hard, but-

1030
01:07:13.760 --> 01:07:15.320
Yeah, but then the security,

1031
01:07:15.320 --> 01:07:17.720
the access level of this list-

1032
01:07:17.720 --> 01:07:19.400
The next thing in the future, though,

1033
01:07:19.400 --> 01:07:21.560
this is where it's gonna get powerful,

1034
01:07:21.560 --> 01:07:22.640
is, you know, then we,

1035
01:07:22.640 --> 01:07:24.560
in the future, we would add Slack.

1036
01:07:24.560 --> 01:07:27.120
In the future, we would add, like, email.

1037
01:07:27.120 --> 01:07:30.120
You know, that's where the magic will start to happen.

1038
01:07:30.120 --> 01:07:31.320
So, yeah, because it's kind of simple.

1039
01:07:31.320 --> 01:07:33.640
Yeah, right now, we could just totally-

1040
01:07:33.640 --> 01:07:34.720
In addition to this,

1041
01:07:34.720 --> 01:07:38.760
even, like, agents and workflows would be shared, like, here.

1042
01:07:40.440 --> 01:07:41.280
Would be shared, like-

1043
01:07:41.280 --> 01:07:42.760
True.

1044
01:07:42.760 --> 01:07:45.080
Like, I can see, yeah.

1045
01:07:45.080 --> 01:07:46.360
No, not, like, agents.

1046
01:07:46.360 --> 01:07:48.840
I'm running, like, agents templates, let's say,

1047
01:07:48.840 --> 01:07:50.520
that you can use, but, like,

1048
01:07:50.520 --> 01:07:53.280
they are shared between the team.

1049
01:07:53.280 --> 01:07:56.400
Or eventually, even, like, runtime, like-

1050
01:07:56.400 --> 01:07:57.240
Yeah.

1051
01:07:57.240 --> 01:08:00.760
It's, like, Innovo owned, you know, Innovo's VPS.

1052
01:08:00.760 --> 01:08:02.800
I just want one screen where it's, like,

1053
01:08:02.800 --> 01:08:04.640
a group of all Lucian's bots running,

1054
01:08:04.640 --> 01:08:06.920
and Gennady's, and my, like, everybody's, like,

1055
01:08:06.920 --> 01:08:07.760
you know, people-

1056
01:08:07.760 --> 01:08:08.600
That's, yeah, we are-

1057
01:08:08.600 --> 01:08:10.200
There's 30 agents running right now.

1058
01:08:10.200 --> 01:08:14.040
Yesterday, I was able to make this working, like,

1059
01:08:14.480 --> 01:08:15.320
our-

1060
01:08:15.320 --> 01:08:18.800
It now knows where, when I have a diamond

1061
01:08:18.800 --> 01:08:20.000
running on my machine,

1062
01:08:20.000 --> 01:08:23.880
and I can just, like, do a slash slash local,

1063
01:08:23.880 --> 01:08:25.720
or slash slash remote,

1064
01:08:25.720 --> 01:08:28.399
and it will decide whether it will run the task

1065
01:08:28.399 --> 01:08:30.040
on my local or my remote.

1066
01:08:30.040 --> 01:08:30.880
So it's-

1067
01:08:30.880 --> 01:08:32.600
And I was, like, man, that's so cool.

1068
01:08:32.600 --> 01:08:33.840
And we are-

1069
01:08:33.840 --> 01:08:37.319
We literally can, in a couple months,

1070
01:08:37.319 --> 01:08:40.160
probably, like, really make that thing

1071
01:08:40.160 --> 01:08:42.000
where we can have this dashboard,

1072
01:08:42.000 --> 01:08:44.920
and can be even animated with my agents

1073
01:08:44.920 --> 01:08:46.720
going to the Lucian agents,

1074
01:08:46.720 --> 01:08:48.120
and, like, handling some stuff,

1075
01:08:48.120 --> 01:08:49.800
and we can be, like, watching.

1076
01:08:49.800 --> 01:08:53.600
It's awesome.

1077
01:08:53.600 --> 01:08:54.920
That's funny.

1078
01:08:54.920 --> 01:08:55.760
Great.

1079
01:08:57.439 --> 01:08:59.640
Cool, I know we ran over time, so this is good, though.

1080
01:08:59.640 --> 01:09:00.479
I know we, like-

1081
01:09:00.479 --> 01:09:03.080
We kind of went down this yesterday on the call,

1082
01:09:03.080 --> 01:09:03.920
and then we-

1083
01:09:03.920 --> 01:09:05.840
It was good to kind of close it up

1084
01:09:05.840 --> 01:09:08.080
and to have something framed.

1085
01:09:08.120 --> 01:09:12.000
But, yeah, let's keep working on it.

1086
01:09:12.000 --> 01:09:13.720
I think this is exciting times.

1087
01:09:13.720 --> 01:09:14.560
I just-

1088
01:09:14.560 --> 01:09:16.680
What I wanted to do was make sure-

1089
01:09:16.680 --> 01:09:18.479
I was starting to set up some of this stuff

1090
01:09:18.479 --> 01:09:19.319
to make it all sync,

1091
01:09:19.319 --> 01:09:20.520
but I didn't want us to all-

1092
01:09:20.520 --> 01:09:22.720
It sounds like we're one missing piece away,

1093
01:09:22.720 --> 01:09:24.720
which is this Notion task issue.

1094
01:09:26.399 --> 01:09:29.319
And then the other thing that, again, with Notion,

1095
01:09:29.319 --> 01:09:31.080
like, I think with the database would be good,

1096
01:09:31.080 --> 01:09:35.399
is having that crazy, like, detailed activity log

1097
01:09:35.600 --> 01:09:38.840
of, like, Luchans, like, terminaled on this thing

1098
01:09:38.840 --> 01:09:40.520
on this date, changed this project,

1099
01:09:40.520 --> 01:09:43.680
did this thing, committed these files to the repo.

1100
01:09:43.680 --> 01:09:45.200
I think the other thing we're out of scope here

1101
01:09:45.200 --> 01:09:47.800
is there's no connection between the Novo dashboard

1102
01:09:47.800 --> 01:09:48.800
and the repo.

1103
01:09:48.800 --> 01:09:51.800
Like, you're just gonna have to tell the agent, like,

1104
01:09:51.800 --> 01:09:53.319
this is the repo we're working on.

1105
01:09:53.319 --> 01:09:54.800
I think, like, some of those things, I think,

1106
01:09:54.800 --> 01:09:57.480
are a little, like, gray area we didn't really talk about,

1107
01:09:57.480 --> 01:09:58.560
but those are things I'm assuming.

1108
01:09:58.560 --> 01:10:00.960
If we didn't talk about it, it's not on the list.

1109
01:10:00.000 --> 01:10:06.660
So sweet nice nice awesome guys

1110
01:10:13.320 --> 01:10:15.320
Sweet alright guys

1111
01:10:17.200 --> 01:10:19.200
Good stuff