How to connect Daytona to OpenClaw
Connect Daytona to OpenClaw with ClawLink in one click — 114 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
DaytonaOAUTH2MCPManage development environments and workspaces. Once connected, OpenClaw can read and act on Daytona from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Daytona access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Daytona setup: install one ClawHub skill, connect Daytona in the browser, and OpenClaw can call real Daytona actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Daytona skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Daytona" (hith3sh/daytona-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/daytona-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Daytona.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Daytona
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Daytona?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Daytona in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Daytona to download file deprecated and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Daytona is connected in the dashboard, that agent calls the same 114 Daytona tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Daytona MCP for OpenClaw
Looking for a Daytona MCP server for OpenClaw? ClawLink connects Daytona to OpenClaw and exposes 114 Daytona tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Daytona integration works the same way.
What the OpenClaw Daytona integration can do
114 Daytona tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 114.
30 of 114 Daytona tools for OpenClaw
| Tool | What it does |
|---|---|
Download file deprecated daytona_download_file_deprecated | [DEPRECATED] Downloads a file from a sandbox's toolbox filesystem |
Download files daytona_download_files | Downloads multiple files from a sandbox as a multipart/form-data bundle |
Find in files deprecated daytona_find_in_files_deprecated | [DEPRECATED] Searches for text or patterns in files within a sandbox |
Get API key daytona_get_api_key | Retrieves an API key by its name |
Get available account providers daytona_get_available_account_providers | Retrieves all available account providers that can be used to authenticate and link accounts |
Get build logs URL daytona_get_build_logs_url | Retrieves the build logs URL for a specific sandbox by its ID or name |
Get commit history daytona_get_commit_history | Gets commit history from a repository in a sandbox toolbox |
Get computer use status daytona_get_computer_use_status | Retrieves the status of all VNC desktop processes in a sandbox |
Get config daytona_get_config | Retrieves the Daytona platform configuration including URLs, OIDC settings, analytics, rate |
Get display info daytona_get_display_info | Retrieves information about displays connected to a sandbox |
Get entrypoint logs daytona_get_entrypoint_logs | Retrieves entrypoint logs for a sandbox session |
Get file info daytona_get_file_info | [DEPRECATED] Gets file info inside a sandbox toolbox |
Get git history deprecated daytona_get_git_history_deprecated | [DEPRECATED] Get commit history from a git repository in a sandbox toolbox |
Get has sandbox access daytona_get_has_sandbox_access | Checks if the authenticated user has access to a specific sandbox |
Get health daytona_get_health | Retrieves the current health status of the Daytona service |
Get organization daytona_get_organization | Retrieves detailed information about an organization by its unique identifier |
Get organization audit logs daytona_get_organization_audit_logs | Retrieves audit logs for an organization |
Get organization invitations count user daytona_get_organization_invitations_count_user | Retrieves the count of organization invitations for the authenticated user |
Get organization usage overview daytona_get_organization_usage_overview | Retrieves the current usage overview for an organization, including CPU, memory, disk |
Get process status daytona_get_process_status | Retrieves the status of a specific VNC process in a sandbox |
Get project dir deprecated daytona_get_project_dir_deprecated | [DEPRECATED] Gets the project directory path within a sandbox toolbox |
Get pty session daytona_get_pty_session | Retrieves information about a PTY (pseudo-terminal) session in a sandbox |
Get push access daytona_get_push_access | Retrieves temporary storage access credentials for pushing objects to object storage |
Get registry daytona_get_registry | Retrieves details of a specific Docker registry by its unique identifier |
Get sandbox daytona_get_sandbox | Retrieves details of a specific sandbox by its ID or name |
Get session command logs daytona_get_session_command_logs | Retrieves logs for a specific command executed within a session |
Get session deprecated daytona_get_session_deprecated | [DEPRECATED] Retrieves details of a specific session in a sandbox toolbox |
Get snapshot daytona_get_snapshot | Retrieves details of a specific snapshot by its ID or name |
Get snapshot build logs daytona_get_snapshot_build_logs | Retrieves build logs for a specific snapshot |
Get toolbox proxy URL daytona_get_toolbox_proxy_url | Retrieves the toolbox proxy URL for a sandbox by its ID or name |
Try it: find the Daytona tool you need
Browse the 30 Daytona tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Daytona to download file deprecated and walk me through the result in plain English.
Use Daytona to download files and walk me through the result in plain English.
Use Daytona to find in files deprecated and walk me through the result in plain English.
Pull the relevant data from Daytona, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Daytona working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Daytona app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Daytona through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Daytona. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Daytona actions to the runtime in a format your agent can reliably use. | 114 tools for Daytona are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Daytona to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Daytona in the browser, and the 114 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Daytona skill but can't call the tools
The ClawHub skill teaches OpenClaw about Daytona, but the calls run through the ClawLink plugin and your connected account. Make sure Daytona is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Daytona from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Daytona tools
Daytona tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Daytona call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Daytona returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Daytona and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Daytona integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Daytona: link your Daytona account once in the browser and OpenClaw can call the Daytona API through 114 ready-made tools — no custom code or token handling.
How do I add Daytona to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Daytona skill from ClawHub, then you click Connect in the dashboard to authorize Daytona. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Daytona to OpenClaw?
About two minutes. Sign in, click Connect next to Daytona in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Daytona up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Daytona working from chat.
OpenClaw installed the Daytona skill but can't call the tools
The ClawHub skill teaches OpenClaw about Daytona, but the calls run through the ClawLink plugin and your connected account. Make sure Daytona is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Connect GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.