Daytona provides the cloud sandbox in which PullPlane agents inspect, test, and change a connected repository away from a teammate's laptop and production environment.
A sandbox for each run
PullPlane provisions a dedicated sandbox for an agent run, clones the selected repository into it, and starts the configured Claude, Codex, Research, Reviewer, QA, or Security work there. Run sandboxes are not shared as a common working directory between agents.
Visible, isolated execution
Isolation does not make the work opaque. PullPlane streams run status and terminal events, exposes touched files and the git diff, and can hand off a running preview when the project starts successfully in the sandbox.
- Repository work stays inside the run environment until branch delivery
- Model credentials and configured repository secrets are injected for the run that needs them
- The run lifecycle reclaims finished sandbox compute after output and preview handoff
Managed and workspace-key setup
On managed sandbox plans, PullPlane supplies the Daytona connection. On workspace-key plans, an owner adds a Daytona API key during setup. Availability, concurrency, and runtime remain subject to the workspace's configured limits.