Daytona integration

Developer Tools & Infrastructure · 12 actions · API key auth

Run AI-generated code in secure, isolated cloud sandboxes. Create and manage sandboxes, execute shell commands, run Python, JavaScript, or TypeScript code, transfer files, and clone Git repositories.

Put Daytona to work View Daytona integration docs

Overview

The ModuleX Daytona integration lets a ModuleX agent operate Daytona on your behalf — running create, remove and list actions across sandboxes, codes and commands — directly from a plain-English request, using your organization's own Daytona credentials. No pre-built workflow is required: the agent picks the right Daytona action for the task.

Daytona is a developer tools & infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Daytona action — or, when you want a repeatable process, the composer assembles a Daytona workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Daytona in plain English

Type what you want. A ModuleX agent picks the right Daytona action — or chains several — and runs it. No workflow to build.

Create a new Daytona sandbox for running AI-generated code in isolation
resolves tocreate_sandbox
Find the sandbox I describe and remove it
resolves tolist_sandboxesdelete_sandbox
Show me the files that match what I describe
resolves tolist_files

Use cases

What you can automate with Daytona

Find the right sandbox and remove it in one promptlist_sandboxesdelete_sandbox
Run a code from a plain-English requestrun_code
Run a command from a plain-English requestexecute_command
Upload a file from a requestupload_file

At a glance

Daytona integration at a glance

VendorDaytona

CategoryDeveloper Tools & Infrastructure

Actions available12

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 12 Daytona actions

Sandboxes6

create_sandbox

Create a new Daytona sandbox for running AI-generated code in isolation.

list_sandboxes

List Daytona sandboxes in the organization.

get_sandbox

Get details of a Daytona sandbox.

start_sandbox

Start a stopped Daytona sandbox.

stop_sandbox

Stop a running Daytona sandbox.

delete_sandbox

Delete a Daytona sandbox.

Codes1

run_code

Run Python, JavaScript, or TypeScript code inside a Daytona sandbox.

Commands1

execute_command

Execute a shell command inside a Daytona sandbox.

Files3

upload_file

Upload a file to a Daytona sandbox.

download_file

Download a file from a Daytona sandbox (returned base64-encoded inline).

list_files

List files in a directory of a Daytona sandbox.

Git Clones1

git_clone

Clone a Git repository into a Daytona sandbox.

See full parameters and response schemas in the Daytona integration docs

Two ways

Two ways to use Daytona in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Daytona action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Daytona into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Daytona

API keyDaytona uses API-key authentication. You provide your own Daytona secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Daytona without re-authenticating.

Step-by-step setup in the Daytona docs

Pairs well with Daytona

Agents often chain Daytona with these — connect them once and the agent can use all of them in a single task.

Microsoft Entra ID12 actions

FAQ

Daytona + ModuleX FAQ

A ModuleX agent can run any of Daytona's 12 actions — across sandboxes, codes, commands and files — from a plain-English request, using your organization's own Daytona credentials.

No. The agent selects the right Daytona action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Daytona API key, stored encrypted and scoped to your organization.

12, spanning sandboxes, codes, commands and files.

Daytona runs on your own credentials, so any Daytona usage is billed by Daytona directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Daytona to work in ModuleX.

Connect Daytona once with your own credentials and let your agent run all 12 actions on demand.

Put Daytona to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →