WEBVTT

1
00:00:00.000 --> 00:00:02.900
So there is a lot about the job

2
00:00:02.930 --> 00:00:05.700
isn't actually that fun that I have

3
00:00:05.730 --> 00:00:08.380
now automated away almost entirely.

4
00:00:09.100 --> 00:00:10.720
And so I'll show you a few of those

5
00:00:10.750 --> 00:00:13.540
here in our automations tab. And we've

6
00:00:13.570 --> 00:00:15.040
got a bunch running now, but we can

7
00:00:15.070 --> 00:00:16.640
run down a few of these because I kind

8
00:00:16.670 --> 00:00:18.260
of have set up a few different types

9
00:00:18.290 --> 00:00:19.500
of automation. And the first type is

10
00:00:19.530 --> 00:00:21.460
just sort of information. I'm asking

11
00:00:21.490 --> 00:00:23.940
Codex to look at the last day of

12
00:00:23.970 --> 00:00:26.140
commits into this section of our

13
00:00:26.170 --> 00:00:28.740
monorepo. And basically group them,

14
00:00:28.920 --> 00:00:31.000
tell me who worked on what, what got

15
00:00:31.030 --> 00:00:32.280
done, what do I need to know about.

16
00:00:32.420 --> 00:00:33.980
And so I wake up in the morning with

17
00:00:34.010 --> 00:00:36.380
almost like a, if you've used JotGPT

18
00:00:36.410 --> 00:00:38.460
Pulse, it's like a personalized pulse

19
00:00:38.490 --> 00:00:40.120
that I walk, I open the app in the

20
00:00:40.150 --> 00:00:41.360
morning and sitting there is like,

21
00:00:41.480 --> 00:00:43.200
here's what happened yesterday in the

22
00:00:43.230 --> 00:00:45.960
code base, which is super,

23
00:00:46.240 --> 00:00:47.620
super useful. So I have one called

24
00:00:47.650 --> 00:00:50.560
Upskill. And what Upskill does is

25
00:00:50.590 --> 00:00:52.720
it looks at the last day of skill

26
00:00:52.750 --> 00:00:55.140
usage. So it says, hey, skills are

27
00:00:55.170 --> 00:00:57.020
really useful, but sometimes they take

28
00:00:57.050 --> 00:00:58.100
a little bit of tinkering to get

29
00:00:58.130 --> 00:01:00.640
right. And so it looks at Codex usage

30
00:01:00.670 --> 00:01:03.620
throughout the past day and detects if

31
00:01:03.650 --> 00:01:05.640
any skills, like if Codex had any

32
00:01:05.670 --> 00:01:07.160
trouble with skills or if any of the

33
00:01:07.190 --> 00:01:10.200
scripts didn't work correctly or if

34
00:01:10.230 --> 00:01:11.820
like something could be sped up. And

35
00:01:11.850 --> 00:01:13.460
it makes improvements to the skills.

36
00:01:13.620 --> 00:01:15.180
So it's upskilling like overnight.

37
00:01:15.480 --> 00:01:16.820
Like I'm going to sleep, I wake up,

38
00:01:16.920 --> 00:01:18.480
Codex is smarter in the morning based

39
00:01:18.510 --> 00:01:19.940
on what we're trying to do here.

40
00:01:20.280 --> 00:01:22.840
Similarly, update AgentsMD, like

41
00:01:22.870 --> 00:01:25.460
this I just have run every, I don't

42
00:01:25.490 --> 00:01:27.120
know, six hours. And it just looks at

43
00:01:27.150 --> 00:01:28.700
what we've been doing. And if there's

44
00:01:28.730 --> 00:01:30.680
any like disagreements or

45
00:01:30.710 --> 00:01:32.080
misunderstandings that I've had with

46
00:01:32.110 --> 00:01:33.960
Codex or things where things took

47
00:01:33.990 --> 00:01:36.380
longer to communicate than, or I used

48
00:01:36.410 --> 00:01:37.800
some shorthands that Codex wasn't

49
00:01:37.830 --> 00:01:39.440
familiar with, it will just add that

50
00:01:39.470 --> 00:01:41.480
to the personalization. So that next

51
00:01:41.510 --> 00:01:43.860
time things can just be quicker.

52
00:01:44.020 --> 00:01:45.440
I've got a few others that are

53
00:01:45.470 --> 00:01:47.840
integrated deeply into our other

54
00:01:47.870 --> 00:01:50.160
tools. And so one of them is Sentry.

55
00:01:50.780 --> 00:01:52.140
This is kind of a different type of

56
00:01:52.170 --> 00:01:54.360
automation where it's going to go

57
00:01:54.390 --> 00:01:56.460
through on whatever schedule, whatever

58
00:01:56.490 --> 00:01:58.500
cadence, and it picks off one of the

59
00:01:58.530 --> 00:02:00.440
top Sentry issues. So that could be

60
00:02:00.470 --> 00:02:01.940
like a performance regression or

61
00:02:01.970 --> 00:02:04.700
a crash or an error that's being

62
00:02:04.730 --> 00:02:07.880
thrown in the app. And it like goes

63
00:02:07.910 --> 00:02:09.400
through all of the information that we

64
00:02:09.430 --> 00:02:12.180
have about it, the logs, the maps,

65
00:02:12.260 --> 00:02:13.900
everything that Sentry has, it looks

66
00:02:13.930 --> 00:02:16.340
at the code base and it picks

67
00:02:16.370 --> 00:02:18.460
something to fix basically. And

68
00:02:18.490 --> 00:02:20.600
automations have memory. So it

69
00:02:20.630 --> 00:02:22.560
remembers what it tried to solve last

70
00:02:22.590 --> 00:02:23.660
time. And so you're not going to get a

71
00:02:23.690 --> 00:02:25.500
PR like solving the number one issue

72
00:02:25.530 --> 00:02:28.160
every hour, right? But it's really

73
00:02:28.190 --> 00:02:30.100
good because what this, you know, what

74
00:02:30.130 --> 00:02:32.020
this type of automation does is it

75
00:02:32.050 --> 00:02:35.000
allows us to focus on what is going to

76
00:02:35.030 --> 00:02:37.480
make the Codex app great to use and

77
00:02:37.510 --> 00:02:40.500
useful and joyful and all of the

78
00:02:40.530 --> 00:02:42.780
things that like, you know,

79
00:02:43.460 --> 00:02:45.240
bugs and things that fall through

80
00:02:45.270 --> 00:02:46.580
cracks that like aren't quite as

81
00:02:46.610 --> 00:02:47.920
fun to figure out, at least for me.

82
00:02:48.020 --> 00:02:50.020
I know some people love it.

83
00:02:51.040 --> 00:02:52.640
That stuff can happen kind of behind

84
00:02:52.670 --> 00:02:54.560
the scenes, right? And so it's really

85
00:02:54.590 --> 00:02:57.120
common that you run into merge

86
00:02:57.150 --> 00:02:58.420
conflicts when you try to merge your

87
00:02:58.450 --> 00:02:59.600
thing. And like you find, you know,

88
00:02:59.740 --> 00:03:01.900
you iterate on your approach and

89
00:03:01.930 --> 00:03:03.640
you've got like different types of

90
00:03:03.670 --> 00:03:05.120
people giving reviews and then you're

91
00:03:05.150 --> 00:03:06.760
finally ready to merge something and

92
00:03:06.790 --> 00:03:08.280
there's a conflict. Your CI is failing

93
00:03:08.310 --> 00:03:10.340
for, you know, some small reason.

94
00:03:10.500 --> 00:03:12.040
You got to kind of dive into that. And

95
00:03:12.070 --> 00:03:14.180
so I don't like dealing with any of

96
00:03:14.210 --> 00:03:17.140
that. Maybe, you know. Most people

97
00:03:17.170 --> 00:03:19.020
probably don't. Some people love doing

98
00:03:19.050 --> 00:03:20.960
that and they work on CI tools.

99
00:03:22.400 --> 00:03:24.840
But I have a green PRs automation here

100
00:03:24.870 --> 00:03:26.200
that uses some of our skills. So

101
00:03:26.230 --> 00:03:28.920
we use BuildKai, we use GitHub. And so

102
00:03:28.950 --> 00:03:31.140
what this does is it checks if I have

103
00:03:31.170 --> 00:03:34.100
any open PRs and I usually have like

104
00:03:34.130 --> 00:03:35.940
at any given time between 10 and

105
00:03:35.970 --> 00:03:38.240
20 PRs these days open at a time

106
00:03:38.270 --> 00:03:41.280
because of the Codex app. Separate

107
00:03:41.310 --> 00:03:43.260
problem. And this is going to go

108
00:03:43.290 --> 00:03:45.560
through and it's going to say like, do

109
00:03:45.590 --> 00:03:48.060
any have CI failures because of like,

110
00:03:48.300 --> 00:03:50.780
you know, something that like linted

111
00:03:50.810 --> 00:03:53.260
wrong or like didn't get caught in the

112
00:03:53.290 --> 00:03:55.500
pre -push? Or maybe it's going to

113
00:03:55.530 --> 00:03:57.100
merge conflict because someone is like

114
00:03:57.130 --> 00:03:59.280
also changing it because we're rushing

115
00:03:59.310 --> 00:04:01.200
to, you know, finish up a project or

116
00:04:01.230 --> 00:04:03.340
something like that. And this is going

117
00:04:03.370 --> 00:04:04.360
to go through and it's going to make

118
00:04:04.390 --> 00:04:06.100
sure that all my PRs are green. It's

119
00:04:06.130 --> 00:04:07.220
going to update the base branch.

120
00:04:07.340 --> 00:04:09.420
It's going to intelligently resolve

121
00:04:09.450 --> 00:04:10.820
merge conflicts by looking at like

122
00:04:10.850 --> 00:04:12.880
what have people been trying to do. So

123
00:04:12.910 --> 00:04:15.320
it's not just a factual like, you

124
00:04:15.350 --> 00:04:17.520
know, I'm going to clean up the like

125
00:04:17.550 --> 00:04:19.760
conflict markers. It can look at,

126
00:04:20.540 --> 00:04:21.800
oh, like Joey was putting in this

127
00:04:21.830 --> 00:04:23.400
feature. So we changed this block for

128
00:04:23.430 --> 00:04:25.240
this reason. I'm trying to do this.

129
00:04:25.380 --> 00:04:26.540
I'm changing it and there's a conflict

130
00:04:26.570 --> 00:04:28.440
and like kind of knows how to do that.

131
00:04:28.470 --> 00:04:30.280
And so that's a very long way of

132
00:04:30.310 --> 00:04:31.960
saying my PRs are always green.


