Sandbox Lifecycle

Sandboxes are the ephemeral, secure environments where AI agents execute tasks. Understanding their lifecycle is key to using OutcomeDev effectively.

The "Fresh Clone" Rule

Every task runs in a brand new, isolated sandbox. This is our foundational principle for security and reproducibility.

1. Provisioning: When you start a task, we provision a new cloud environment.
2. Cloning: We perform a git clone of your connected repository into the sandbox.
3. Execution: The agent runs your task, installing dependencies, writing code, and running commands as needed.
4. Termination: Once the task is complete (or hits a timeout), the entire sandbox is destroyed.

This means no state is ever carried over between tasks.

Timeouts

To prevent runaway processes, sandboxes have a default timeout of 15 minutes. This is configurable in your Settings. If a task exceeds this limit, it will be stopped and the sandbox terminated.

Reusing Tasks

Because every run is a fresh clone, you can rerun any task and expect the same result, provided the underlying code in your repository hasn't changed. This is the core of reproducibility.

If you want to build on a previous task, you must ensure the changes from that task were committed back to your repository. The agent will then clone the updated repository and continue from there.