# How to connect Daytona to Hermes Agent (no API keys) > Connect Daytona to Hermes with ClawLink in one click — 114 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/daytona Most guides for giving Hermes Agent Daytona access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Daytona setup: pair once in the browser and your always-on Hermes agent can act on Daytona for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to Daytona. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Daytona** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect daytona # connect Daytona (browser OAuth) npx -y @useclawlink/cli actions daytona # list available actions npx -y @useclawlink/cli run daytona --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Daytona in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Daytona to download file deprecated and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Daytona MCP for Hermes Looking for a Daytona MCP server for Hermes Agent? ClawLink connects Daytona to Hermes Agent and exposes 114 Daytona tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Daytona integration](https://claw-link.dev/openclaw/daytona) works the same way. ## What the Hermes Agent Daytona integration can do 114 Daytona tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Download File Deprecated** > Use Daytona to download file deprecated and walk me through the result in plain English. **Download Files** > Use Daytona to download files and walk me through the result in plain English. **Find In Files Deprecated** > Use Daytona to find in files deprecated and walk me through the result in plain English. **Get Api Key** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Daytona Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Daytona integration? Yes. ClawLink is the fastest way to connect Hermes to Daytona: link your Daytona account once in the browser and Hermes Agent can call the Daytona API through 114 ready-made tools — no custom code or token handling. ### How do I connect Daytona to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Daytona in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Daytona to Hermes Agent? About two minutes. Sign in, click Connect next to Daytona in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Daytona working from chat. ### Hermes paired but still can't use Daytona Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/safetyculture) — 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.