ClaudeMulti-file workflowsLevel 3: Workflows

How Do You Approve Claude's File List Before Edits?

Use plan mode, and require the plan to be a table of every file Claude will create, change or delete. Trim it with Ctrl+G, then approve. In the Claude app, ask for the same list and tell Claude to wait. You can then check the result against the list when it's done.

Prompt to copy
/plan [goal].

The plan must be an edit manifest: a table of every file you'll create, change or delete, with one line on what changes and why. Leave out files you only need to read. Order it so the code builds and tests pass after each group. Mark anything you're unsure of with a question.

Once I approve, treat the list as the scope. If you find you need a file that isn't on it, stop and tell me why before you touch it.
  1. 1Claude lists each file and what changes
  2. 2You trim it with Ctrl+G
  3. 3Approve, then compare with git diff --statafter the work
In Claude Code, plan mode blocks edits until you approve, so the list really does come first.

Try it now

  1. 1Send the prompt in Claude Code. The status bar shows ⏸ plan mode on while it works.
  2. 2Press Ctrl+G to open the plan in your editor, and delete rows you don't want. To send it back with comments, choose No, keep planning.
  3. 3Choose Yes, manually approve edits to watch each edit, or Yes, and use auto mode if you've read the plan and trust it.
  4. 4When it's done, run git diff --stat. It worked if the files match the list, or each difference has a reason Claude told you about.

Use it when

A feature that crosses layers, a cross-cutting rename, or wiring a new dependency through a project. Use it the moment you can't hold the whole change in your head.

Skip it when

A single-file change or a typo, where writing the list takes longer than the edit. For one mechanical change across a great many files, use /batch instead, which researches the code and shows its own plan of 5 to 30 units for you to approve.

Why it works

Scope is the costly failure in multi-file work: eight files edited when three were needed, or two missed. Anthropic's help center recommends switching to plan mode or just asking for a plan on anything touching more than two or three files, since a plan costs far less than a large diff you revert and redo. Plan mode makes this a real gate, because edits stay blocked until you approve. A file list makes the plan checkable, since after the work git diff --stat either matches or it doesn't. Anthropic's large-codebase guide adds another benefit: Claude Code re-injects the plan file after each compaction, so on a long change the list survives where conversation history may not.

Example

You ask for rate limiting on the API. The manifest lists a new src/middleware/rateLimiter.ts, a change to src/middleware/index.ts, a new RATE_LIMIT_PER_MINUTE in config/default.ts, a new test file, and an edit to src/auth/session.ts marked with a question. You don't think auth is involved, so you delete that row and the question gets answered before any code moves.

Going further

For repetitive work, the manifest can drive a script. Anthropic's docs show a loop over files.txt that runs claude --bare -p for each file with --allowedTools, --permission-mode dontAsk and --max-turns 20, replying OK or FAIL. Try it on three files first, fix the prompt, then run the rest. Know what --bare skips: hooks, skills, plugins, MCP servers and CLAUDE.md files. It also never touches your claude.ai login, so authentication comes from ANTHROPIC_API_KEY or your cloud provider, which means API billing rather than your plan.

Common mistakes

  • Approving a list you didn't read. The review is the only thing this adds, so if you skip it you've just spent tokens on a table.
  • Accepting entries like "update related files". Every row should name a real file and a real change.
  • Ignoring a new file that turns up mid-work. Add it to the plan or reject it, rather than letting the change spread quietly.
  • Leaving claude -p --worktree runs around. They exit without asking about cleanup, so remove them with git worktree remove.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course