The external world an agent acts on — files, databases, APIs, browsers — accessed via tool results.
The environment is the external world an AI agent perceives and acts upon through tool calls and tool results. It encompasses everything outside the agent's own runtime harness — the files it reads and writes, the databases it queries, the APIs it calls, the browser sessions it controls. The harness is the wrapper that runs the agent; the environment is the workspace the agent operates in.
Agents perceive the environment exclusively through tool results — structured outputs returned by the harness after executing a tool call. An agent reading a file sees the content through a Read tool result; it changes the environment through a Write or Edit tool call. The environment holds state that persists across tool calls within a session: a file written in one turn remains written for subsequent turns.
The central tradeoff is scope control. Expanding the environment to include more systems — staging databases, cloud APIs, production dashboards — gives the agent more to work with but increases the risk surface. Restricting the environment to a narrow sandbox limits damage from errors or misaligned tool use but may prevent the agent from completing its task.
Open questions include how to give agents situational awareness of which environment they are operating in, and how to handle conflicts when multiple agents share access to the same environment simultaneously. No standard mechanism currently exists for environment-level access control across agent sessions.