WEBVTT

00:00:00.220 --> 00:00:03.740
So the setup is the first important step.

00:00:03.780 --> 00:00:07.700
The base usage we also kind of saw
already, though there's a bit more to

00:00:07.740 --> 00:00:11.580
that. But what's also important
is configuring Claude

00:00:11.660 --> 00:00:14.080
Code or knowing how to configure it.

00:00:14.140 --> 00:00:17.900
And regarding that, you got a couple of

00:00:17.980 --> 00:00:21.040
options. You can configure Claude Code

00:00:21.340 --> 00:00:25.300
globally on your system. Actually,
as an enterprise, you

00:00:25.340 --> 00:00:28.150
can even configure it for all your team
members.

00:00:28.160 --> 00:00:31.780
But here,
we'll focus on individual installations on

00:00:31.790 --> 00:00:34.220
So then you can configure it globally.

00:00:34.240 --> 00:00:38.120
For example, here on Mac,
I have a global.claude folder on my

00:00:38.200 --> 00:00:40.780
system in my current user's home
directory.

00:00:40.850 --> 00:00:44.480
In there is a bunch of stuff,
but one of the things in there is a

00:00:44.540 --> 00:00:48.400
settings.json file. And when you open
that settings file, you'll be

00:00:48.440 --> 00:00:51.000
able to set up some global settings.

00:00:51.010 --> 00:00:54.920
You can also tweak those settings though
from inside Claude

00:00:54.960 --> 00:00:58.550
Code. If you run /config, it'll bring up

00:00:58.600 --> 00:01:01.960
that configuration menu where you can
browse

00:01:02.160 --> 00:01:06.080
through the various settings it has
and the current values,

00:01:06.140 --> 00:01:10.000
and also change those values. For example,
if you wanna

00:01:10.040 --> 00:01:13.920
change that theme you initially picked,
you can select that here, bring up

00:01:13.980 --> 00:01:17.040
that theme picker in this case,
and choose a different theme.

00:01:17.060 --> 00:01:19.740
Though I'll stay with the default dark
mode here.

00:01:19.760 --> 00:01:22.390
And you can do that for all these
settings.

00:01:22.420 --> 00:01:26.160
For example, if you wanna save tokens
and you know you don't have complex tasks,

00:01:26.200 --> 00:01:29.720
you could turn off thinking mode
and set this to false.

00:01:29.800 --> 00:01:33.200
And you'll see that now, for example,
in this global settings

00:01:33.500 --> 00:01:37.100
file here, this Always Thinking Enabled

00:01:37.420 --> 00:01:41.080
value here changed to false, and
is now set to false

00:01:41.100 --> 00:01:44.160
because I made this change in my Claude

00:01:44.360 --> 00:01:48.280
CLI.
Because whenever you change a config

00:01:48.360 --> 00:01:52.240
by default, at least right now
when I'm recording this,

00:01:52.320 --> 00:01:55.840
settings. Now,
Claude Code has a long list of

00:01:55.900 --> 00:01:59.780
available settings,
which of course also changes over time as

00:01:59.840 --> 00:02:03.700
changed, and so on.
Attached 3D offer finder link to the

00:02:03.780 --> 00:02:06.720
that you can see the most recent version
of that list.

00:02:06.800 --> 00:02:10.780
One setting which I find important,
which is not set by

00:02:10.800 --> 00:02:14.580
default, at least right now
when I'm recording this, is this

00:02:14.780 --> 00:02:17.420
permissions setting here though.

00:02:17.540 --> 00:02:21.150
Here you can allow or deny certain

00:02:21.440 --> 00:02:25.160
things. And you wanna deny Claude Code

00:02:25.800 --> 00:02:29.320
reading your .env files, for example,
where you might be

00:02:29.380 --> 00:02:33.000
keeping secrets or other kind of sensitive

00:02:33.040 --> 00:02:36.170
information you don't want Claude Code to
read.

00:02:36.170 --> 00:02:40.030
And the way this permissions system works
is

00:02:40.060 --> 00:02:43.760
such that you specify the tool Claude Code
may be

00:02:43.820 --> 00:02:47.620
using.
And there are various built-in tools,

00:02:47.700 --> 00:02:51.520
ones for this context are read
and write and bash,

00:02:51.580 --> 00:02:55.420
which allow Claude, you guessed it,
to read or write or execute

00:02:55.600 --> 00:02:59.380
bash commands. And you can then specify

00:02:59.480 --> 00:03:03.160
some restrictions essentially related to
which files you want to

00:03:03.180 --> 00:03:06.900
deny using these tools.
Because of course I don't wanna generally

00:03:06.980 --> 00:03:10.840
Claude Code from using the read
or write tools, but I want to

00:03:10.880 --> 00:03:14.780
deny it using these tools on any files
stored anywhere

00:03:14.840 --> 00:03:18.560
that are called.env. And that
is in the end

00:03:18.640 --> 00:03:21.620
what this rule set up here should achieve.

00:03:21.660 --> 00:03:25.420
Now I'll switch Always Thinking Enabled
back to true here, by the way, because

00:03:25.540 --> 00:03:29.220
I want it to use thinking mode.
Another place where

00:03:29.260 --> 00:03:33.040
settings can be stored
is inside of your project folder,

00:03:33.080 --> 00:03:36.470
this next folder. In there,
you can add a .claude

00:03:36.940 --> 00:03:40.600
folder. And in there,
you can also add a settings.json

00:03:40.720 --> 00:03:44.680
file. And then in here,
you can set up Claude settings

00:03:44.690 --> 00:03:47.680
the global settings for this project.

00:03:47.740 --> 00:03:51.580
You can also add a settings.local.json
file,

00:03:51.620 --> 00:03:55.420
which will also be a project-specific
settings file that will overwrite

00:03:55.430 --> 00:03:58.900
the global settings and
that will also overwrite the

00:03:58.940 --> 00:04:01.500
settings from the settings.json file.

00:04:01.510 --> 00:04:05.269
And the idea behind settings.local
is simply that it's not

00:04:05.320 --> 00:04:09.130
checked into source control.
So it's not part of

00:04:09.160 --> 00:04:13.109
your GitHub repository, for example,
so that individual users,

00:04:13.140 --> 00:04:16.500
if you're in a team
and you're working on a project,

00:04:16.540 --> 00:04:19.779
settings that extend
or overwrite parts of the

00:04:19.820 --> 00:04:23.080
project-specific or global settings.