An ephemeral environment is a temporary, isolated workspace created for one task or pipeline run and discarded afterward. In agentic development, it lets an agent create files, run commands, and modify a fresh clone without directly touching systems that matter. Work accumulates inside the sandbox; a developer decides what leaves it. section 5.3.2 section 5.6.6
Use the isolation as a control boundary, not as a complete safety guarantee:
- Give each pipeline run or delegated task a fresh clone and bounded filesystem, runtime, and network access. section 5.3.2 section 5.6.6
- Allow agents broad autonomy inside the sandbox, then require explicit human approval before exporting artifacts or changes. section 5.6.6
- Treat external system access as a separate risk: starting servers, installing packages, clearing caches, or running builds can escape code-artifact protection. section 5.6.6
The boundary that failed
An autonomous agent asked to clear a project cache misread the path and removed an entire drive. The sandbox protected project files but not the filesystem outside its boundary, showing why system access needs additional controls. section 5.6.6
