Daytona Integration

Everruns integrates with Daytona to provide cloud-based sandbox environments for secure, isolated code execution. Agents can create, manage, and interact with multiple sandboxes per session — each a fully isolated Linux environment with network access.

What You Get

Isolated Sandboxes: Each sandbox is a secure, isolated Linux environment
Multi-Sandbox Sessions: Create and manage multiple sandboxes within a single session
File Operations: Read, write, and download files from sandbox filesystems
Git Integration: Clone repositories with automatic GitHub credential forwarding
Shell Execution: Run arbitrary commands with configurable timeouts

Quick Start

1. Get Your API Key

Go to the Daytona Dashboard
Navigate to API Keys in your account settings
Click Create New API Key
Copy the key

2. Connect in Everruns

Go to Settings > Connections
Find Daytona in the available providers
Click Connect and paste your API key

Once connected, the Daytona capability is automatically available in agent sessions.

3. Use in Sessions

Agents with the Daytona capability can use these tools:

Tool	Description
`daytona_create_sandbox`	Create and start a new sandbox
`daytona_exec`	Execute shell commands
`daytona_read_file`	Read files from sandbox
`daytona_write_file`	Write files to sandbox
`daytona_download_workspace`	Download workspace to session storage
`daytona_list_sandboxes`	List active sandboxes
`daytona_manage_sandbox`	Stop or delete sandboxes
`daytona_git_clone`	Clone repositories (auto-authenticates with GitHub)
`daytona_git_credentials`	Configure git push/pull credentials

Git Integration

Daytona sandboxes integrate with your connected GitHub account:

Clone private repos: daytona_git_clone automatically uses your GitHub credentials
Push/pull/fetch: Call daytona_git_credentials once after creating a sandbox, then use daytona_exec for any git command
Shorthand syntax: Use user/repo format instead of full URLs

Sandbox Lifecycle

Sandboxes auto-stop after 5 minutes of inactivity as a safety net. Best practice is to explicitly delete sandboxes when done — stopping only pauses them (they remain visible on your Daytona dashboard).

Security

API keys are encrypted at rest (AES-256-GCM envelope encryption)
Each sandbox is fully isolated from other sandboxes and the host
Git credentials are short-lived and scoped to the sandbox
Sandbox state is stored in encrypted session secrets