WEBVTT

1
00:00:00.020 --> 00:00:03.280
It's really important for us that Codex works anywhere you like to code.

2
00:00:03.600 --> 00:00:05.760
For many of you, that place is your JetBrains IDE.

3
00:00:06.420 --> 00:00:10.700
So we're super excited to announce that one of our most requested features is finally here.

4
00:00:11.140 --> 00:00:12.700
Codex now works in JetBrains.

5
00:00:13.140 --> 00:00:16.960
You can now collaborate with Codex directly within JetBrains IDEs

6
00:00:17.480 --> 00:00:21.940
using your ChatGPT subscription, API key, or your JetBrains AI subscription.

7
00:00:22.340 --> 00:00:24.240
And with me, I got Gleb from JetBrains,

8
00:00:24.380 --> 00:00:27.060
who's going to give us a quick tour of Codex in JetBrains.

9
00:00:27.380 --> 00:00:30.600
We know developers use our products on complex problems.

10
00:00:31.090 --> 00:00:34.440
And that's where JetBrains and Codex really shine.

11
00:00:34.880 --> 00:00:38.400
So I wanted to show you Codex's work on real projects inside my IDE.

12
00:00:39.120 --> 00:00:42.040
It's a multi-platform Kotlin codebase for our conference.

13
00:00:42.700 --> 00:00:45.400
It runs on mobile, web, and even desktop.

14
00:00:45.960 --> 00:00:49.260
I'll show you how Codex helps with debugging and feature implementation

15
00:00:49.920 --> 00:00:52.000
on that scale right within your IDE.

16
00:00:53.040 --> 00:01:01.120
So let's start probably with the fact that you don't need to use JetBrains AI subscription to log into Codex.

17
00:01:01.760 --> 00:01:09.100
You can use your ChatGPT account to log in or add the API key to do that.

18
00:01:09.460 --> 00:01:15.780
So I'm going to log in in my Codex account, which is already done.

19
00:01:16.380 --> 00:01:21.480
And then I want to, first of all, ask what this project is about, totally.

20
00:01:21.700 --> 00:01:22.380
Totally, it makes sense.

21
00:01:22.720 --> 00:01:28.140
Good way to start. So we can see Codex beginning to look at different files,

22
00:01:28.560 --> 00:01:33.740
reading the file system. Exactly. Yeah. So it collects some context and understanding of what

23
00:01:33.960 --> 00:01:39.020
does the project do. So as you can see, it's our Kotlin Conf app. By the way, you're welcome.

24
00:01:41.060 --> 00:01:48.139
And so, yeah, it runs on Android, iOS, desktop, and web using the framework called Compose

25
00:01:48.160 --> 00:01:54.340
multi-platform. So I will try to build this project right now to see how it actually looks like on iOS.

26
00:01:55.040 --> 00:02:00.100
Cool. So this is compiling it for iOS and then

27
00:02:00.230 --> 00:02:07.920
It compiles the project for iOS using Gradle technology. We're using the IntelliJ tools for

28
00:02:07.970 --> 00:02:13.659
that. But as you can see, there are some errors, right? So, and I will probably need

29
00:02:13.680 --> 00:02:17.360
to help of Codex to solve that.

30
00:02:18.200 --> 00:02:21.660
So what I do is I'm just simply copy and pasting everything

31
00:02:22.100 --> 00:02:28.020
that is read here and asking Codex to help me solving that.

32
00:02:29.980 --> 00:02:34.220
So we can now see Codex is jumping through different tasks,

33
00:02:34.380 --> 00:02:37.300
looking at the files that might be impacted based

34
00:02:37.360 --> 00:02:38.320
on the stack trace.

35
00:02:38.700 --> 00:02:39.180
Exactly.

36
00:02:39.680 --> 00:02:41.860
And you see what exactly Codex does.

37
00:02:42.020 --> 00:02:46.260
So it provides some reasoning on the certain actions that it does.

38
00:02:46.960 --> 00:02:49.280
It shows the files that it's read and so on.

39
00:02:49.560 --> 00:02:55.820
And this is the same Codex that I get when I run Codex CLI or if I use it in a different idea?

40
00:02:55.820 --> 00:03:08.280
It is exactly the same Codex just because inside JetBrains we run evaluation to make sure the quality of CLI Codex is exactly the same as the one that users receive inside AI systems.

41
00:03:08.520 --> 00:03:08.760
Amazing.

42
00:03:09.880 --> 00:03:11.880
And it looks like it did some file changes here.

43
00:03:12.000 --> 00:03:12.100
Yeah.

44
00:03:12.850 --> 00:03:17.140
So actually, we can take a look on the exact changes

45
00:03:17.550 --> 00:03:20.060
to make sure that they actually make sense.

46
00:03:21.160 --> 00:03:23.660
You see the Codex has finished its work.

47
00:03:24.060 --> 00:03:26.920
And we can try to build the project again, right?

48
00:03:28.700 --> 00:03:29.680
Fingers crossed.

49
00:03:30.500 --> 00:03:31.240
See if it builds.

50
00:03:32.379 --> 00:03:35.140
These are just warnings, so it's not a problem.

51
00:03:41.320 --> 00:03:42.400
And it builds.

52
00:03:42.740 --> 00:03:43.140
All right.

53
00:03:44.120 --> 00:03:44.600
Does it run?

54
00:03:45.860 --> 00:03:50.140
Developers usually don't like dealing with the build issues,

55
00:03:50.340 --> 00:03:52.960
and it's quite difficult to understand what exactly is happening

56
00:03:53.420 --> 00:03:55.220
when the project is building.

57
00:03:55.610 --> 00:03:59.780
So Codex does an amazing job understanding what exactly needs to be done here.

58
00:03:59.980 --> 00:04:01.560
Yeah, we didn't really have to give it any guidance.

59
00:04:01.710 --> 00:04:03.940
It just runs around and we figure things out.

60
00:04:03.940 --> 00:04:08.520
We didn't even need to read through the errors that are here, right?

61
00:04:09.060 --> 00:04:10.440
So, yeah, the app is working.

62
00:04:11.980 --> 00:04:17.220
and now I guess it's time to give Codex a little bit more complex task, right?

63
00:04:18.659 --> 00:04:24.320
We know that the biggest problem for all the mobile developers is localization, right?

64
00:04:24.720 --> 00:04:27.580
So just because it's quite a mundane, complex task

65
00:04:28.080 --> 00:04:31.480
that does not involve a lot of kind of visual changes,

66
00:04:31.840 --> 00:04:33.600
but at the same time it is extremely important.

67
00:04:35.420 --> 00:04:37.340
Probably the best task to give to an agent.

68
00:04:37.560 --> 00:04:38.040
Sounds great.

69
00:04:38.220 --> 00:04:40.220
I have a problem that I'm going to base here.

70
00:04:40.780 --> 00:04:45.900
and I'm going to ask, create a localization to Spanish

71
00:04:46.520 --> 00:04:49.180
for the conference app that we have.

72
00:04:49.320 --> 00:04:50.400
Awesome. Let's fire it off.

73
00:04:53.550 --> 00:04:56.280
While Codex is working, we still can oversee

74
00:04:56.730 --> 00:04:59.600
what kind of files it looks at,

75
00:05:00.020 --> 00:05:02.680
what kind of reasoning behind looking at these files.

76
00:05:03.120 --> 00:05:04.820
When it runs the bash commands,

77
00:05:05.340 --> 00:05:07.820
we can see what kind of commands it runs.

78
00:05:08.420 --> 00:05:15.000
At the same time, so different developers have different tolerance towards what agent does, right?

79
00:05:15.260 --> 00:05:27.900
And this is something that we consider inside our integration, where user can select different types of access modes to agent, right?

80
00:05:28.140 --> 00:05:31.960
So we can restrict agent 2 from editing any file.

81
00:05:32.140 --> 00:05:42.620
So it would be just read-only, extremely suitable for understanding complex code bases, or let's say search when a user just doesn't know where the certain file is located.

82
00:05:43.600 --> 00:05:56.220
Agent mode allows to run commands, but at the same time it requires user approval for every command so that some quite sensitive commands would be user-reviewed.

83
00:05:56.700 --> 00:06:08.040
And full access, which I currently have, actually allows agent to run any command they want, apart from the riskiest ones, and change the code files.

84
00:06:08.480 --> 00:06:08.920
Awesome.

85
00:06:11.520 --> 00:06:15.940
And then you can see, are you able to click on the actual files that it's checking out?

86
00:06:16.160 --> 00:06:18.260
Yeah, so you can take a look at the file.

87
00:06:18.860 --> 00:06:26.180
So it opens in IDE, so you can take a look at what exactly is written in this file

88
00:06:26.760 --> 00:06:28.000
as the changes come.

89
00:06:28.780 --> 00:06:29.140
That's awesome.

90
00:06:29.400 --> 00:06:31.060
And I think one of the things that's interesting

91
00:06:31.240 --> 00:06:33.160
is it looked like Codex was doing a lot of research

92
00:06:33.410 --> 00:06:34.240
across the code base

93
00:06:34.420 --> 00:06:36.920
so that if you have a complex code base,

94
00:06:37.020 --> 00:06:39.220
it's going to go and first understand all the context

95
00:06:39.480 --> 00:06:42.060
because we didn't give it any guidance, right?

96
00:06:42.160 --> 00:06:43.760
We just sort of like say, here's the problem.

97
00:06:44.320 --> 00:06:46.000
But now it's sort of like locked in

98
00:06:46.100 --> 00:06:48.720
and it's just like hammering out code change after code change.

99
00:06:48.820 --> 00:06:49.640
Exactly, exactly.

100
00:06:49.940 --> 00:06:52.200
It's like you put a developer

101
00:06:52.460 --> 00:06:55.880
that does not know a thing about this code base to a task.

102
00:06:56.220 --> 00:06:58.940
So the first thing they do is to research the code.

103
00:06:59.080 --> 00:06:59.400
That's right.

104
00:06:59.580 --> 00:07:02.560
So agent here exactly mimics these actions.

105
00:07:03.120 --> 00:07:07.540
Doing the research is not changing anything just because they don't know yet about the codebase.

106
00:07:08.000 --> 00:07:11.460
But so once the research is done, the code changes are coming.

107
00:07:11.840 --> 00:07:12.200
Amazing.

108
00:07:12.880 --> 00:07:17.900
It feels like it's like everything is still very much right inside your IDE.

109
00:07:18.460 --> 00:07:18.660
Exactly.

110
00:07:18.940 --> 00:07:21.360
You don't have to change any of your behaviors that you're used to.

111
00:07:21.740 --> 00:07:24.280
So it's just a sidebar, right?

112
00:07:24.360 --> 00:07:31.780
So while agent is working, you can even close this tab and start a new conversation and asking about something else.

113
00:07:32.380 --> 00:07:36.600
Or you can continue working on the files that you worked with.

114
00:07:36.780 --> 00:07:42.900
So the work of an agent is paralleled with the work that developer does.

115
00:07:43.400 --> 00:07:45.300
And it does not intervene with that.

116
00:07:45.300 --> 00:07:50.720
So a developer does not need to wait for agent to finish working to continue their work.

117
00:07:51.140 --> 00:07:53.520
They kind of coexist elegantly and parallel.

118
00:07:53.580 --> 00:07:55.500
So now it's running a shell command here.

119
00:07:56.140 --> 00:07:57.480
So it looks like it's running Gradle.

120
00:07:58.120 --> 00:08:00.320
It tries to compile everything.

121
00:08:00.670 --> 00:08:00.800
Yeah.

122
00:08:01.240 --> 00:08:03.360
And this is like one of the interesting things about Codex.

123
00:08:03.420 --> 00:08:05.860
Codex always tries to verify its own work.

124
00:08:06.140 --> 00:08:10.040
So being able to then tap into the build tools and using them.

125
00:08:10.320 --> 00:08:12.900
And that's an amazing part, right?

126
00:08:12.950 --> 00:08:15.400
So just because just writing code is not enough.

127
00:08:15.450 --> 00:08:20.320
You need to make sure that the code actually works and reiterate on that if it doesn't.

128
00:08:20.620 --> 00:08:23.160
And as you can see, some of the commands are skipped.

129
00:08:23.240 --> 00:08:24.280
and it's done.

130
00:08:24.490 --> 00:08:24.900
You see?

131
00:08:25.220 --> 00:08:28.840
So the Codex listed the files that were changed, right?

132
00:08:29.040 --> 00:08:31.960
So we can take a look at the lines

133
00:08:31.990 --> 00:08:34.539
that were actually updated or removed.

134
00:08:35.700 --> 00:08:37.520
We can see them in a commit tool window

135
00:08:37.659 --> 00:08:38.680
that they are uncommitted yet.

136
00:08:38.979 --> 00:08:41.740
So we can push them to the repo.

137
00:08:42.240 --> 00:08:44.340
But first of all, let's make sure that it actually works

138
00:08:44.820 --> 00:08:48.700
and rerun the app to see whether the localization

139
00:08:48.830 --> 00:08:49.420
actually takes place.

140
00:08:49.640 --> 00:08:49.760
Cool.

141
00:08:50.160 --> 00:08:51.699
And for that, we're just using the same tools

142
00:08:51.720 --> 00:08:53.440
that we're used to in the IDE already.

143
00:08:53.520 --> 00:08:54.380
Exactly, yeah.

144
00:08:54.900 --> 00:09:00.300
So it's building, starting up the iOS simulator.

145
00:09:01.200 --> 00:09:05.300
It starts the simulator, and I'd expect the app to be already in Spanish.

146
00:09:05.720 --> 00:09:07.180
Cool. Let's see.

147
00:09:07.500 --> 00:09:10.020
Oh, yeah, I can see your simulator is set to Spanish already.

148
00:09:10.080 --> 00:09:13.880
It's set to Spanish just because the app is going to take the localization from the system.

149
00:09:14.560 --> 00:09:20.500
So if everything went fine, the app would be already in Spanish.

150
00:09:21.920 --> 00:09:24.620
And that's how Codex is natively integrated in our products.

151
00:09:25.040 --> 00:09:31.720
What I showed you was all done in IntelliJ, but it also works in other JetBrains products like PyCharm, WebStorm, or Rider.

152
00:09:32.400 --> 00:09:32.840
Thanks, Gleb.

153
00:09:33.540 --> 00:09:36.740
These are just a few of the things that you can build with Codex inside JetBrains.

154
00:09:37.240 --> 00:09:44.320
To get started, go to openai.com/codex or choose Codex inside the AI chat of your JetBrains IDE of choice.

155
00:09:44.820 --> 00:09:46.500
Thank you, and we can't wait to see what you build.


