CLAUDE CODE AGENTS: FUNDAMENTALS - Chapter 1, Exercise 2
Why Denying Write Access Is a Guarantee, Not a Limitation
====================================================================================

QUESTION:
A search-only agent is deliberately denied the ability to edit or write
files. Explain why this restriction is described in this chapter as a
guarantee rather than a limitation.

SOLUTION / EXPLANATION:

Calling this restriction a "limitation" would imply the agent is being held
back from something it should ideally be able to do, with the restriction
as an unfortunate compromise. That framing doesn't match the actual reason
for it.

A search-only agent's entire job is to look through a codebase and report
back what it finds - there is no legitimate reason such an agent would ever
need to modify a file. Given that, denying it write access doesn't cost
anything real, because the agent was never meant to write anything in the
first place. What it does provide is a genuine guarantee: no matter how
that agent behaves internally, no matter what instructions it's given or
how it interprets a task, it is structurally incapable of altering a single
file, because the capability to do so simply doesn't exist for it. This
isn't a matter of trusting the agent to behave well and hoping it doesn't
accidentally edit something - the tool to do so isn't available to it at
all.

This is exactly the meaning of "isolation" as this chapter defines it: the
tighter an agent's allowed toolset matches only what its actual job
requires, the more that agent's possible behavior is constrained by
construction, rather than by good intentions or careful prompting. A
guarantee holds regardless of how the agent behaves; a limitation implies
something desirable was given up. Since nothing desirable is given up here
- a search agent never needed write access to do its job well - "guarantee"
is the accurate word, not "limitation."

--------------------------------------------------------------------------
WHY THIS WORKS AS AN ANSWER:
It explains precisely why the restriction costs nothing (the agent never
needed the capability), and contrasts "restriction as guaranteed inability"
against "restriction as unfortunate tradeoff" to justify why the chapter's
own word choice ("guarantee") is the accurate one.