Safety and permissions
Run agents in a sandbox with the fewest rights they need, keep production out of reach, and treat everything they read as possibly hostile.
- Required 7
- Recommended 1
Required
Run agents in a sandbox
RequiredRun coding agents in an isolated environment, such as a container, a virtual machine or the agent's own sandbox mode.
Keep production credentials away from agents
RequiredNever give a coding agent production keys, database passwords or customer data.
Give agents the fewest rights they need
RequiredGive each agent token only the rights its task needs, and make it short-lived and easy to revoke.
Approve destructive commands
RequiredRequire a person's approval before an agent deletes data, rewrites history, changes infrastructure or spends money.
Treat what the agent reads as untrusted
RequiredAssume any web page, issue, file, dependency or tool result an agent reads may contain instructions meant to hijack it.
Review agent settings like code
RequiredTreat instruction files, agent settings, hooks and rule folders as code that can run. Review every change to them and scan them for hidden text.
Open unknown repositories in a sandbox
RequiredOpen a repository you did not write in a container or virtual machine first. Trust it in your editor or agent only after reading its config.
Recommended
Know what the agent tool does with your code
RecommendedBefore an agent reads your code, check whether its provider stores it, for how long, and whether it trains models on it.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers ai development playbook: https://agentwranglers.se/playbook/ai-assisted-development/safety-and-permissions.