firstprompt
Inicia sesión
Todos los cursos

temario

0 / 40 · 0%
  • Instala Claude Code8m
  • Tu primer archivo6m
  • ¿A dónde se fue ese archivo?6m
  • Cuando Claude se equivoca6m
  • Lo que Claude tiene permitido hacer5m
  • Resumen del módulo 13m
  • Checkpointquiz + publicar
0/40

Estás leyendo sin cuenta: tu progreso solo se guarda en este dispositivo.

Panel/Módulo 1/Lección 5
GratisInstala Claude Code

Lo que Claude tiene permitido hacer

5 min de lectura·Lección 5 de Instala Claude Code

O escúchala

Lo que Claude tiene permitido hacer

2:31 · versión en audio de esta lección

0:002:31

Every time Claude wants to change a file or run a command, it stops and asks you first. That prompt is the most important safety feature you have, and it is also the one people learn to click through without reading.

Anthropic's own measurements found people approve about 93% of these prompts. When you approve nearly everything, the prompt has stopped protecting you — it is just a key you press to continue.

Read the plan, not the vibe

When Claude asks for approval, it tells you what it is about to do. Two questions are worth ten seconds:

  1. Which file? Look at the path. "Edit notes.md" and "Edit .env" are very different requests.
  2. Is it deleting or moving anything? Creating and editing are recoverable with /rewind. Deleting through a command is not, as you saw in the last lesson.

If either answer surprises you, decline and ask what it is trying to achieve. That is not rudeness, and it costs you five seconds.

The four modes

Press Shift + Tab inside Claude to cycle through permission modes. The mode you are in is shown near the input.

ModeWhat it doesWhen to use it
defaultAsks before every changeStart here. Stay here while learning.
planClaude proposes the work but changes nothingLarge or unfamiliar tasks. Read the plan first.
acceptEditsAuto-approves file editsA repetitive job you have already seen it do correctly
autoRuns a background safety check and blocks risky actionsAvailable on some accounts

Plan mode is underused and worth the habit. For anything touching more than one file, switch to plan mode, read what it intends to do, then let it run. You catch the misunderstanding before it edits anything, rather than after.

About "always allow"

Some prompts offer to stop asking for that kind of action. It is genuinely useful for something narrow and repetitive.

Be careful with it for anything that deletes or overwrites. Once you have granted it, Claude will not check with you again this session, and the thing you were half-watching becomes the thing you were not watching at all.

práctica

Prueba esta lección en una terminal guiada.

Siguiente

Resumen del módulo 1

Try it now

Start Claude in your project folder and press Shift + Tab until you are in plan mode. Then ask for something that spans a few files:

add a README.md describing this project, and a .gitignore suitable for it

Claude will write out what it intends to do, and change nothing. Read it. Then approve it and watch it execute exactly that plan.

That gap — between "here is what I will do" and "I did it" — is where you get to be right.

What you just learned

  • The approval prompt is your safety net, and only if you read it.
  • Check which file, and whether anything is being deleted or moved.
  • Shift + Tab cycles permission modes; default is the right place to learn.
  • Plan mode shows you the work before any file changes.
  • "Always allow" is fine for narrow, repetitive actions and risky for destructive ones.

Next: a short recap, then your first real prompts.

Siguiente

Tu progreso

0

0 / 40

lecciones

En este módulo

Instala Claude Code

  1. 1Instala Claude Code8m
  2. 2Tu primer archivo6m
  3. 3¿A dónde se fue ese archivo?6m
  4. 4Cuando Claude se equivoca6m
  5. 5Lo que Claude tiene permitido hacer5m
  6. 6Resumen del módulo 13m
Hacer el checkpoint