E7 · The first task
20 minMake request 1 (read only), then request 2. Open the page with start index.html and ask for a change.
Done when: the page opens in the browser, and you asked the agent for at least one correction.
Lesson 4 · 18 min
First the agent reads, then it makes changes
“Fix the project” mixes diagnosis and changes: if something goes wrong, you won’t know which part caused it. Separating reading from changes, giving the minimum permission needed, and asking for a wrap-up that says what was checked turns the agent into someone you can manage.
Start the lesson
In this lesson, you will
- 1Ask the agent to read without editing, then check which files it used
- 2Allow one small, clearly named change
- 3Write an authorization in five parts
- 4Require a wrap-up: done, checked, pending
Objective: give the agent a task with a clear scope, check what it read and changed, and ask for at least one correction.
01Inspection before renovation
The order of the first task, in four steps.
Scroll down: each step below lights up its part of the diagram.
- 1/5
Inspect
No files change in this step. Be explicit: don’t edit. Ask it to say which files it read so you can compare that with
dir /b. - 2/5
Plan
The list of what’s missing is your reference. If it said it didn’t open a file, the plan doesn’t know what’s in it yet: tell it in your next request what to use as its basis.
- 3/5
Make changes
Say which file can be created or changed. If the agent asks before editing, check that it’s only that file and approve. If it’s another file, decline.
- 4/5
Validate
The final decision is yours. Open the result and compare it with what you asked for. Ask for at least one correction: assigning the task, checking, and deciding is management.
- 5/5
Using × managing
A user asks and accepts. A manager separates reading from changing, authorizes a specific scope, and checks before approving. The difference is in the habit, not the tool.
It works the same in Claude Code and Codex: both read AGENTS.md and work in the folder where they were opened.
02Autonomy means authorization with a clear scope
Five parts that fit on a sticky note.
1. Goal and files
Say what to produce and what it can read. "Draft the September report, using only the September spreadsheet."
A small folder with only the task materials already limits what it can access.
Example
Goal: index.html about me. Files: AGENTS.md only.
2. Actions and stopping point
Say which actions are allowed and which are prohibited: reading and creating, yes; deleting and renaming, no. Sending, publishing, and deleting are external actions: each requires an explicit instruction.
The fact that a button exists does not mean you have permission. Say where it should stop and wait for you.
Stopping point
Deliver the draft and stop before sending.
3. Minimum permission
Reading files is low risk; writing, medium; running commands, high. Start with the most restricted setting that can handle the task.
Written rules provide guidance; the program's permissions are what actually enforce them. In Codex, /permissions shows and changes what it can do.
Don't
Remove all protections to get around an error.
4. Wrap-up
Always ask it to finish by saying what it did, how it was checked, and what is still pending.
That turns the result into something you can review, instead of something you have to trust.
Wrap-up
Done: index.html. Checked: opens in the browser. Pending: photo.
03The requests, in order
Open the agent inside the folder (claude or codex) and paste one request at a time.
Request 1 · read only
Read AGENTS.md and README.md. Explain the project's purpose and list what's missing, without editing anything. At the end, say which files you used.
Request 2 · change with a name and a stopping point
Read AGENTS.md. Create only index.html with a simple page about me, using what's there. Don't change or delete any other files. At the end, say: what you did, how you checked it, and what is still pending.
cmd · check the change
dir /b start index.html
Request 3 · the correction
Change the title to "<your title>" and add a contact section. In index.html only.
Request 4 · the agent reads your files
Read the .txt files in the entradas folder and write saidas/resumo.md with 5 decisions and 5 pending items, citing which file each one came from.
cmd · a restore point before Git (lesson 6)
cd %USERPROFILE%\projetos xcopy /e /i meu-primeiro-agente meu-primeiro-agente-antes rem after the change, compare: fc /n meu-primeiro-agente-antes\*.md meu-primeiro-agente\*.md
Simulation: illustrative example
Request 1: "The goal is a page about Ana. Missing: the index.html, the format, and how to check it. Files read: AGENTS.md and README.md. I also checked the file listing. Nothing was edited."
It explained, listed what was missing, said what it read and what it didn’t read. No files changed.
- The files it says it read are listed in
dir /b. - After request 2, only index.html appeared.
- The page opens in the browser, and you asked for a correction.
- In resumo.md, you found at least two of the quoted phrases in the original.
- "Improve the page": it makes a change you don’t know how to check. Ask for a result you can see.
- Approving without reading: the agent asks before editing so you can see which file will change.
- A quote that isn’t in the original: add the missing rule to AGENTS.md ("only quote phrases that exist in the file").
04Practice
With the agent open inside meu-primeiro-agente.
E8 · The agent reads your files
20 minPut three of your texts in entradas (notes, meeting minutes, a long email) and make request 4. Check two quotes against the original file.
Done when: you found at least two of the quoted phrases in the original. If any are missing, add the missing rule to AGENTS.md.
05Test what you learned
The explanation appears after your answer.
Question 1 of 3
What’s the best first request in a new folder?competency
Correct
Start with an inspection: read without editing and say what you used. That gives you a reference before anything changes.Not this one
Start with an inspection: read without editing and say what you used. That gives you a reference before anything changes.Review: Inspection before renovationQuestion 2 of 3
The authorization said only "organize the evidence folder," and the agent deleted three files that looked like copies. What was missing?
Correct
Without saying what it can and can’t do (read and create, yes; delete, no), deleting was left implicit.Not this one
Without saying what it can and can’t do (read and create, yes; delete, no), deleting was left implicit.Review: Autonomy means authorization with a clear scopeQuestion 3 of 3
AGENTS.md says "don’t send anything." Does that technically prevent sending?
Correct
A written rule guides behavior; permissions limit what’s possible. The two work together.Not this one
A written rule guides behavior; permissions limit what’s possible. The two work together.Review: Autonomy means authorization with a clear scopeTest complete
You got {a} out of {n} right. Get them all right to mark the lesson complete.Choose an option. The explanation appears after your attempt.