WEBVTT

1
00:00:00.000 --> 00:00:01.555
Before we configure the project,

2
00:00:01.613 --> 00:00:05.619
we need to understand which account
path and tools the course actually uses.

3
00:00:06.315 --> 00:00:10.727
This lesson will leave you with a short
setup record. It will identify the editor,

4
00:00:10.843 --> 00:00:12.678
the selected AI interface,

5
00:00:12.921 --> 00:00:16.590
and the status of access without
putting credentials into your project.

6
00:00:16.973 --> 00:00:19.736
Installation, sign-in, permissions,

7
00:00:19.887 --> 00:00:23.022
and successful execution
are separate observations.

8
00:00:23.406 --> 00:00:27.260
We use browser chat for introductory
explanations and Codex in an editor

9
00:00:27.330 --> 00:00:31.300
for project work. A browser
response can explain supplied text.

10
00:00:31.625 --> 00:00:35.120
An editor agent can also use
permitted tools to inspect files,

11
00:00:35.294 --> 00:00:39.764
execute commands, or make edits.
An API client is another path:

12
00:00:40.008 --> 00:00:42.864
it is software you build or
configure to call a service.

13
00:00:43.189 --> 00:00:47.438
The course does not require that API
path or a key stored beside the firmware.

14
00:00:47.763 --> 00:00:51.664
Account eligibility and usage
limits can change. Use the current

15
00:00:51.711 --> 00:00:55.403
official information and the controls
shown in your account. The edition's

16
00:00:55.472 --> 00:00:58.329
bounded pilot verified that
a dedicated Free account

17
00:00:58.375 --> 00:01:01.696
could perform a small Codex task
in its recorded environment.

18
00:01:02.137 --> 00:01:05.713
That is useful evidence of that
access path, but it is not a promise

19
00:01:05.759 --> 00:01:09.207
of unlimited use for every lesson
or every future product release.

20
00:01:09.590 --> 00:01:12.690
If you reach a limit, save
your brief and current files.

21
00:01:13.016 --> 00:01:16.696
You can analyze the original reference
response, write requirements,

22
00:01:16.754 --> 00:01:21.526
inspect code, read diffs, and run local
checks while waiting for access to return.

23
00:01:21.851 --> 00:01:25.926
Record which interaction you actually
performed and which supplied example

24
00:01:25.984 --> 00:01:30.558
you examined. Do not describe an
offline analysis as a new model run,

25
00:01:30.674 --> 00:01:32.822
and do not silently change billing routes.

26
00:01:33.333 --> 00:01:36.537
Start the setup record with the
operating system and architecture.

27
00:01:36.921 --> 00:01:42.354
The demonstrated environment is Windows on
ARM, which is different from x64 Windows.

28
00:01:42.633 --> 00:01:46.394
The recorded editor used
an ARM64 user installation.

29
00:01:46.719 --> 00:01:48.728
If you use another supported environment,

30
00:01:48.844 --> 00:01:52.640
follow its official installer instructions
and record the actual versions.

31
00:01:53.023 --> 00:01:55.694
A screenshot showing
one architecture is not

32
00:01:55.740 --> 00:01:58.364
proof that every dependency
supports another.

33
00:01:58.805 --> 00:02:03.855
Open the official Visual Studio Code setup
page and select the appropriate installer.

34
00:02:04.297 --> 00:02:08.290
The user installation supports ordinary
editor work under a standard account.

35
00:02:08.732 --> 00:02:10.891
Follow the current
documentation and restart

36
00:02:10.926 --> 00:02:12.841
the application after installation.

37
00:02:13.538 --> 00:02:16.812
We do not need the author's
production tools, hosting accounts,

38
00:02:16.963 --> 00:02:19.622
or password manager inside
the learner workbench.

39
00:02:20.005 --> 00:02:23.209
The project folder and its supported
development tools are enough.

40
00:02:23.813 --> 00:02:27.087
In the Extensions view, locate
the official Codex component

41
00:02:27.180 --> 00:02:30.500
and verify its publisher against
the official documentation.

42
00:02:31.011 --> 00:02:33.751
Similar names are not a
reliable identity check.

43
00:02:34.262 --> 00:02:37.129
Record the installed extension
version and editor version.

44
00:02:37.571 --> 00:02:40.137
An installed extension means
the component is present.

45
00:02:40.520 --> 00:02:44.874
It does not yet show that the intended
account is authenticated or that the agent

46
00:02:44.920 --> 00:02:48.647
can inspect the correct project.
Sign-in is a private step.

47
00:02:48.972 --> 00:02:52.965
The video can show the safe entry screen
and the neutral project view afterward,

48
00:02:53.140 --> 00:02:56.634
with the private interval omitted.
Do not capture passwords,

49
00:02:56.727 --> 00:03:00.442
recovery codes, tokens, or
a password-manager surface.

50
00:03:00.721 --> 00:03:04.471
Complete any login challenge yourself,
then return to the project.

51
00:03:04.750 --> 00:03:08.302
There is no educational benefit
in displaying credentials as proof

52
00:03:08.360 --> 00:03:12.017
that authentication occurred.
Check the resulting access path.

53
00:03:12.342 --> 00:03:16.429
If the interface offers subscription
sign-in, use the selected course route.

54
00:03:16.673 --> 00:03:20.713
Do not assume that an API option is
required just because it appears nearby.

55
00:03:20.992 --> 00:03:24.533
If you cannot determine which route
is active, inspect the official help

56
00:03:24.591 --> 00:03:28.295
and account controls before proceeding.
Your setup record should say what

57
00:03:28.329 --> 00:03:32.242
you actually used rather than infer it
from a successful-looking welcome screen.

58
00:03:33.055 --> 00:03:35.540
Next consider what
information a request shares.

59
00:03:36.143 --> 00:03:38.953
A short excerpt may answer
an explanation question.

60
00:03:39.394 --> 00:03:42.320
An agent task may need
the intended repository.

61
00:03:42.831 --> 00:03:47.324
Neither requires unrelated documents,
private messages, or other projects.

62
00:03:47.835 --> 00:03:50.540
Use a practice folder whose
contents you understand.

63
00:03:51.144 --> 00:03:54.395
Later we will inspect the exact
folder and the agent's actions

64
00:03:54.511 --> 00:03:57.506
so that project access has
an observable boundary.

65
00:03:58.110 --> 00:04:00.536
Instructions and permissions
have different roles.

66
00:04:00.977 --> 00:04:05.900
A prompt can say inspect only and do
not edit. That expresses the task.

67
00:04:06.411 --> 00:04:09.894
Runtime controls determine what
operations are technically permitted.

68
00:04:10.172 --> 00:04:13.075
Read both. A broad
permission setting does not

69
00:04:13.121 --> 00:04:16.059
mean every available
operation belongs in the task,

70
00:04:16.233 --> 00:04:19.936
and a narrow-sounding prompt does not
create a technical barrier by itself.

71
00:04:20.262 --> 00:04:22.781
The setup record should
distinguish four stages.

72
00:04:23.222 --> 00:04:27.529
First, the interface is installed.
Second, the intended account is signed in.

73
00:04:28.040 --> 00:04:30.316
Third, project access is configured.

74
00:04:30.757 --> 00:04:34.565
Fourth, a bounded task has executed
and its result has been checked.

75
00:04:34.948 --> 00:04:37.444
We complete the final
stages in the next lesson.

76
00:04:37.827 --> 00:04:41.891
Keeping them separate helps diagnose a
failure without reinstalling everything

77
00:04:41.961 --> 00:04:45.873
or changing unrelated settings.
Consider a few interruptions.

78
00:04:46.314 --> 00:04:48.961
A missing executable is
a local tool problem.

79
00:04:49.403 --> 00:04:52.212
An account limit is an
access-capacity problem.

80
00:04:52.491 --> 00:04:55.010
A wrong project folder is a path problem.

81
00:04:55.336 --> 00:04:58.981
A compiler diagnostic is a
program or dependency problem.

82
00:04:59.306 --> 00:05:02.894
They may occur in the same session,
but they call for different remedies.

83
00:05:03.219 --> 00:05:07.955
Preserve the exact message and context so
the next step addresses the actual cause.

84
00:05:08.338 --> 00:05:13.029
For your exercise, classify three
activities: a browser explanation,

85
00:05:13.110 --> 00:05:17.870
an editor agent reading project files,
and an API client requiring a key.

86
00:05:18.114 --> 00:05:21.411
Then identify the path used
by this course and one useful

87
00:05:21.481 --> 00:05:24.419
local action you can continue
if the service is limited.

88
00:05:24.802 --> 00:05:27.542
Fill in your actual
versions and access status

89
00:05:27.576 --> 00:05:30.502
without copying private
metadata into the notebook.

90
00:05:30.827 --> 00:05:35.018
A version record is useful only if it
describes your actual installation.

91
00:05:35.402 --> 00:05:39.210
Copying the edition's version table
into a result field would hide

92
00:05:39.256 --> 00:05:42.820
differences that might explain
a later failure. Keep the table

93
00:05:42.855 --> 00:05:46.954
as a comparison reference and enter
your own observed values separately.

94
00:05:47.279 --> 00:05:51.980
If the interface does not expose a detail,
mark it unavailable rather than infer it.

95
00:05:52.305 --> 00:05:55.765
You can still record the concrete
operation that succeeded or failed

96
00:05:55.858 --> 00:06:00.154
and the date of that observation. You
are ready to continue when the record

97
00:06:00.212 --> 00:06:04.774
makes your setup understandable and
honest. If authentication remains pending,

98
00:06:05.018 --> 00:06:07.920
mark it pending and continue
the independent local work.

99
00:06:08.245 --> 00:06:11.589
If it succeeds, record the
neutral result without secrets.

100
00:06:11.914 --> 00:06:15.954
The next lesson will connect this account
and interface to a named project folder,

101
00:06:16.129 --> 00:06:20.111
a documented software check, and
an inspection-only agent task.