Daytona
Cloud development workspaces with environments, snapshots, and remote execution.
Spins up a workspace, runs a command inside it, and tears the environment down when the task is finished.
Use Daytona with Snow
Snow is a personal AI assistant that builds real apps for you, and they can put Daytona to work.
What Snow can do with Daytona
These are the Daytona operations Snow and the apps you build with it can run. Sign in to choose which ones Snow may run without asking.
Reads46
Look at your data without changing it.
- Check Sandbox Access
Checks if the authenticated user has access to a specific sandbox. Use this action when you need to verify whether the current user has permission to access a particular sandbox before performing further operations on it. This is a read-only operation that does not modify any sandbox data.
- Download Multiple Files
Downloads multiple files from a sandbox as a multipart/form-data bundle. Use this action when you need to retrieve multiple files from a sandbox in a single operation. The files are returned as a streamed multipart response where each file is a separate part. This is a read-only operation that does not modify any resources.
- Get API Key
Retrieves an API key by its name. Use when you need to retrieve details about a specific API key, including its creation date, expiration, permissions, and usage statistics. This is a read-only operation that does not modify any resources.
- Get Authenticated User
Retrieves the profile of the authenticated user. Use when you need to fetch details about the currently logged-in user, including their ID, email, name, creation date, and associated public keys. This action requires authentication and uses the bearer token provided in the request headers to identify the user. This is a read-only operation that does not modify any resources.
- Get Available Account Providers
Retrieves all available account providers that can be used to authenticate and link accounts. Use when you need to discover which account providers (such as GitHub, GitLab, Google) are available for linking to the user's account. This is a read-only operation that does not modify any resources. Note: The list includes both the provider name (machine-readable) and displayName (human-readable) for each provider.
- Get Build Logs URL
Retrieves the build logs URL for a specific sandbox by its ID or name. Use this action when you need to access build logs for a sandbox, such as during troubleshooting build failures, monitoring build progress, or retrieving historical build information. This is a read-only operation that does not modify any resources.
- Get Commit History
Gets commit history from a repository in a sandbox toolbox. Use this action when you need to retrieve the commit history including: - Commit hash - Author name and email - Commit message - Timestamp This is a read-only operation that does not modify any resources.
- Get Computer Use Status
Retrieves the status of all VNC desktop processes in a sandbox. Use this action when you need to check the current state of all VNC desktop processes running within a sandbox. The status can indicate whether services are fully operational (active), partially running (partial), not running (inactive), or experiencing errors (error). This is useful for monitoring the health of computer use services and troubleshooting connectivity issues. This is a read-only operation that does not modify any resources. Note: This endpoint is deprecated. Consider using alternative methods for checking computer use status in new implementations.
- Get Daytona Config
Retrieves the Daytona platform configuration including URLs, OIDC settings, analytics, rate limits, and other platform-level settings. Use this action when you need to fetch the current Daytona configuration settings, such as the dashboard URL, proxy settings, SSH gateway configuration, analytics endpoints, or to check if maintenance mode is enabled. This is a read-only operation that returns the platform configuration.
- Get Daytona Health Status
Retrieves the current health status of the Daytona service. Use when you need to verify that the Daytona API is running and accessible. This action is read-only and does not modify any data. This action is useful for monitoring, debugging connection issues, or confirming API availability before performing other operations.
Creates15
Add something new to your account.
- Clone Repository
Clones a Git repository into a sandbox toolbox. Use this action when you need to clone a public or private Git repository into a specific directory within a sandbox. Supports optional branch selection and commit checkout. This is commonly used to set up a development environment or fetch source code for further operations. Note: Credentials (username/password) should only be provided when the target repository requires authentication. The sandbox must be running to perform this operation.
- Create API Key
Creates a new API key for the organization. Use when you need to generate a new API key that can be used to authenticate API requests. The created API key value is only returned once in the response and cannot be retrieved again, so it must be stored securely. This action requires appropriate organization permissions.
- Create Docker Registry
Creates a new Docker registry for the organization. Use when you need to register a new container registry (such as Docker Hub, GCR, ECR, or other Docker registries) so that Daytona can pull images from it. The registry credentials are stored securely and used for pulling images when creating sandboxes. Ensure the provided credentials have appropriate permissions (typically read access to the registry).
- Create Folder in Sandbox
Creates a new folder inside a sandbox's filesystem. Use this action when you need to create a directory within a running sandbox's filesystem. This is useful for organizing files, preparing directory structures, or setting up paths for subsequent file operations. Note: This endpoint is deprecated. Consider using alternative methods for folder creation if available.
- Create Organization
Creates a new organization in Daytona. Use this action when you need to set up a new organization with a specific name and default region configuration. This action creates a top-level organization entity that can manage sandboxes, users, and resources within the specified region.
- Create Organization Invitation
Creates an invitation to join an organization with specified roles and permissions. The invitation will be sent to the provided email address. Use this action when you need to invite a new member to an organization with specific role assignments. The invitation email will include a link to accept the invitation.
- Create Organization Role
Creates a new organization role with specified permissions. Use this action when you need to define custom roles for organization members, allowing fine-grained control over what resources they can access and what operations they can perform. Common use cases include creating roles like "Developer" (with sandbox write access), "Viewer" (read-only access), or "Admin" (full access to all resources).
- Create Process Session
Creates a new session in the sandbox for process management. Use this action when you need to establish a new process session within a running sandbox environment. This enables managing process execution and state within the Daytona platform. The session can be used to track and manage process-related operations. Note: This endpoint is deprecated. Consider using alternative methods for process session management if available. The sandbox must be in a running state for this operation to succeed.
- Create PTY Session
Creates a new PTY (pseudo-terminal) session in a sandbox. Use this action when you need to establish an interactive terminal session within a running sandbox environment. This enables real-time command execution and terminal interaction through the Daytona platform. The session can be configured with specific terminal dimensions (cols/rows), working directory, and environment variables. Note: This endpoint is deprecated. The sandbox must be in a running state for this operation to succeed. Consider alternative methods for terminal sessions if available.
- Create Sandbox
Creates a new sandbox environment for development or testing purposes. Use this action when you need to provision a new isolated environment with configurable compute resources (CPU, memory, GPU), networking options, and storage volumes. The sandbox can be customized with environment variables, labels, and automatic lifecycle management settings. Note: This action creates a new resource. Ensure you have the appropriate permissions in your organization before creating sandboxes.
Updates23
Change something that is already there.
- Archive Sandbox
Archives a sandbox in the Daytona platform. Use this action when you need to archive a sandbox that is no longer needed but should be preserved for future reference. The sandbox will be marked as archived and its state will change to reflect the archival status. Note: Archiving a sandbox does not delete it immediately. The sandbox can potentially be restored or recovered from an archived state depending on the platform configuration.
- Checkout Git Branch
No description available.
- Deactivate Snapshot
Deactivates a snapshot in the Daytona platform. Use this action when you need to deactivate a snapshot that is currently active. This will stop the snapshot from being used for new sandbox creations. Note: Deactivating a snapshot does not delete it. The snapshot data remains accessible but the snapshot is marked as inactive.
- Execute Command
Executes a shell command within a running sandbox via the toolbox proxy. Use this action when you need to run shell commands, scripts, or any executable commands inside a sandbox environment. This is useful for automation tasks, running build commands, executing scripts, or performing system operations within the sandbox. The sandbox must be in a running state for this action to succeed. Command execution is synchronous and will wait for completion up to the specified timeout (default 10 seconds).
- Focus Accessibility Node
Focuses an accessibility node in a sandbox's computer use system. Use this action when you need to programmatically set focus to a specific accessibility node within a sandbox's desktop environment. This is particularly useful for UI automation workflows where you need to ensure a specific element has focus before performing keyboard or mouse actions on it. Note: The sandbox must have computer use enabled for this action to work. This action is idempotent — focusing the same node multiple times will have the same effect.
- Replace In Files
Replaces text or patterns in multiple files within a sandbox. Use this action when you need to perform find-and-replace operations across multiple files in a sandbox. For each file specified, the action searches for the given pattern and replaces it with the new value. This action modifies files within the sandbox, so use with caution as changes may be difficult to revert. Consider backing up files before performing bulk replacements.
- Replace Sandbox Labels
Replaces all labels on a sandbox with a new set of key-value pairs. Use this action when you need to update or redefine the labels associated with an existing sandbox. This operation completely replaces any existing labels — the previous labels will be removed. Note: This action modifies the sandbox's labels in bulk. If you need to add or remove individual labels while preserving others, consider fetching the current labels first and constructing the complete new set.
- Resize PTY Session
Resizes an active PTY session with new terminal dimensions. Use this action when you need to change the column and row dimensions of an existing pseudo-terminal (PTY) session within a running sandbox. This is commonly used to adjust the terminal display size to match the current viewport or user preference. The session must be active for this operation to succeed. This action is idempotent - resizing to the same dimensions is safe and will not cause errors. Note: Ensure the PTY session is active before attempting to resize it. Resizing an inactive session may result in errors.
- Set Auto Delete Interval
Sets the auto-delete interval for a sandbox. Use this action when you need to configure automatic deletion of a sandbox after it is stopped. The interval specifies how many minutes after stopping the sandbox before it gets deleted. Use a negative value to disable auto-delete, or 0 to delete immediately upon stopping. This action modifies the sandbox lifecycle configuration and affects when the sandbox will be permanently removed after being stopped.
- Set Autostop Interval
Sets the auto-stop interval for a sandbox in the Daytona platform. Use this action when you need to configure how long a sandbox should run idle before automatically stopping. This helps manage resources and reduce costs by automatically stopping unused sandboxes. The interval is specified in minutes. Setting the interval to 0 disables auto-stop, allowing the sandbox to run indefinitely until manually stopped. The API returns the updated sandbox object with the new auto_stop_interval value.
Deletes18
Remove something. This often cannot be undone.
- Cancel Organization Invitation
Cancels a pending organization invitation. Use when you need to revoke an invitation that has been sent but not yet accepted by the recipient. This action is irreversible — once an invitation is cancelled, it cannot be reactivated and the recipient will no longer be able to accept it. The cancelled invitation would need to be re-sent as a new invitation if access is still desired.
- Delete API Key
Deletes an API key by its name. Use when you need to revoke access for an API key that is no longer needed or has been compromised. This action is irreversible — once an API key is deleted, it cannot be recovered and any systems using that key will immediately lose access.
- Delete API Key for User
Deletes an API key for a specific user. Use when you need to remove an existing API key associated with a user account, such as when cleaning up unused credentials or revoking access. This action is irreversible — once the API key is deleted, it cannot be recovered and any systems relying on that key will lose access.
- Delete Docker Registry
Deletes a Docker registry from the Daytona platform. Use when you need to remove an existing Docker registry configuration. This is an irreversible operation — once a registry is deleted, it cannot be recovered and any references to it in workspaces may fail until reconfigured.
- Delete Git Branch
Deletes a branch from a git repository inside a sandbox by its name. Use when you need to permanently remove a git branch that is no longer needed. This action is irreversible — once a branch is deleted, it cannot be recovered unless it has been pushed to a remote. Ensure the branch has been properly merged or is no longer needed before proceeding. Note: This action uses a deprecated API endpoint. The API documentation marks this endpoint as
- Delete Organization
Deletes an organization. Use when you need to permanently remove an organization from the system, including all associated data, members, and resources. This action is irreversible — once an organization is deleted, it cannot be recovered. All organization data, including workspaces, sandboxes, and member information, will be permanently lost. Ensure you have appropriate backups or have migrated necessary data before proceeding.
- Delete Organization OTEL Config
Deletes the OpenTelemetry (OTEL) configuration for an organization. Use this action when you need to remove the OpenTelemetry settings that were previously configured for an organization's observability and tracing capabilities. This action is irreversible — once the OpenTelemetry configuration is deleted, the organization will no longer have OTEL tracing enabled and any previously collected telemetry data will no longer be accessible through the configured OTEL endpoint. A new configuration would need to be created to re-enable OpenTelemetry observability.
- Delete Organization Role
Deletes an organization role. Use when you need to permanently remove a role from an organization, such as cleaning up unused custom roles or removing roles that are no longer needed. This action is irreversible — once a role is deleted, it cannot be recovered. Users who were assigned this role will lose the associated permissions and access. Ensure no active users or resources depend on this role before proceeding.
- Delete Recording
Deletes a recording from the Daytona platform by its ID. Use when you need to permanently remove a recording that is no longer needed. This action is irreversible — once a recording is deleted, it cannot be recovered. Any data associated with the recording will be permanently lost.
- Delete Sandbox
Deletes a sandbox from the Daytona platform by its ID or name. Use when you need to permanently remove a sandbox that is no longer needed. This action is irreversible — once a sandbox is deleted, it cannot be recovered. Any data, processes, or configurations within the sandbox will be permanently lost. Ensure all important work has been saved or backed up before proceeding.
Related integrations
Ready to put Daytona to work?
Sign up free, build an app by chatting, and connect Daytona in minutes. No credit card required.