Glossary Sandbox environment
Sandbox environment
A controlled task world with a starting state, a defined set of permitted actions and rules that decide whether the agent succeeded.
Answer in brief
A sandbox environment is a controlled task world in which an agent can act: a starting state, the actions it may take, and the rules that decide whether the final state is a success. It makes a run repeatable, scorable and comparable with another run.
The environment and the verifier are separate pieces of work. Building a world is design work; deciding success is a specification problem, and it is usually cheaper to settle the objective before the world exists.
Definition
A sandbox environment is a controlled task world defined by a starting state, a set of permitted actions and success rules. The starting state has to be reproducible: the same records, permissions and tool responses, unless handling a changing state is the point of the task.
Two environments that look alike can differ in what they permit, and therefore in what a passing run proves. The sandboxes and verifiers guide sets out the components; the tool-use trajectory entry covers what the environment records while the agent works.
What the environment defines
- The starting state: data, files, accounts and permissions.
- The actions and tools the agent may call, and those it may not.
- The reset procedure that returns the world to the same starting state.
- What the agent cannot see: grader state, expected answers and other runs.
- The rules that decide success, written before the first run.
A reset that does not return to the same state makes two runs incomparable.
The verifier decides success
The verifier is the check that decides whether the final state meets the objective: a test script, a state comparison, or a rubric applied by a person. An objective no check can decide is not yet an objective.
Test the verifier before trusting it. Run it against attempts you know to be good and attempts you know to be bad and confirm it separates them; a verifier that accepts almost everything produces a number that looks like an evaluation while measuring nothing.
Proxy reward and permissions
A proxy reward is a measurable stand-in for the outcome you want, such as a form being filled or a status field being changed. If the proxy can be satisfied without doing the task, a capable agent will find that route. Name the shortcut and add a check that closes it.
Permissions belong in the same conversation: which credentials the sandbox holds, which endpoints it can reach, whether it can write outside its workspace, and how it is isolated from production.
Acceptance question
Ask for the environment definition and the verifier source, then run one known good and one known bad attempt in front of you. Accept when the reset works, the verifier separates the two, and the permissions match what you would allow in a rehearsal. The buying guide places this check in the purchase sequence.
Questions & answers
Does a sandbox need to replicate production exactly?
Can the environment and the verifier come from different suppliers?
Sources for this entry
- Editorial checklists on this site — Original guidance written for this reference; the environment checklist is editorial, not a published standard.
- WebArena: a realistic web environment for autonomous agents — Public paper describing realistic web environments and reproducible evaluation of autonomous agents; cited for the category, not as a ranked result.
Editorial checklists on this site are original guidance. Links to official product documentation help readers understand the category; they do not establish comparative performance and are not endorsements of any supplier.
Cite this entry
Best AI Agent Training Data. “Sandbox environment.” Content reviewed .
https://bestaiagenttrainingdata.com/