VillaAula
Log in
Course text
Lesson 2 / 3

INSTALL · START · APPROVAL MODES

Install it and say hello

Key idea — the why

Same three steps as any of these tools:

1. Install it once, for the whole computer:

npm install -g @openai/codex

2. Walk into your project and start it:

cd my-project

codex

3. Sign in with your OpenAI account the first time.

Then the important part: how much rope do you give it? Codex asks how freely it may act — whether to check with you before each edit, or to work on its own and show you the result at the end.

Start cautious. Let it ask permission for everything until you've watched it work a few times and you trust what it does. You can always loosen the leash; you can't un-delete a file.

Go deeperThe terminal, for people who've never opened one
Progress0 / 3 correct
🔐

How much freedom to give it

Every one of these agents has some version of this dial, and it's the single most important setting you'll touch. Roughly, it has three positions:

  • Ask me first — it proposes each change and waits for your yes. Slow, and completely safe. Start here.
  • Edit, but ask before running things — it can change files on its own, but stops before running commands.
  • Full speed — it works alone and shows you the result. Fast, and you'd better be in a folder you can afford to lose.

The advice is genuinely simple: stay on the cautious setting until watching it work has become boring. Boredom is the signal that you understand what it does. Until then, every approval prompt is a free lesson in what the tool is actually doing.

And whatever the setting: work in a folder backed up by Git. That way any change can be undone with one command. Nobody is careful enough to skip that.

1

Type the command that starts Codex once it's installed. (One word.)

2

You've just installed Codex and you're about to use it on a real project. Which approval setting should you choose?

3

Keeping your project in Git means a bad change can be undone.

Saved on this device