> ## Documentation Index
> Fetch the complete documentation index at: https://felan.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Daytona

> Connect a customer-owned Daytona Cloud account for bounded control-plane management.

Felan's Daytona integration connects one customer-owned Daytona Cloud account
per team. It is separate from the Daytona account Felan uses for its own agent
runtime.

## Set up Daytona

1. In the Daytona Cloud dashboard, create an API key in the customer
   organization used by Felan.
2. Grant the key only the control-plane permissions needed for the team's
   work. Do not reuse Felan's platform runtime key.
3. In Felan, open **Integrations → Catalog → Daytona** and choose **Configure**.
4. Enter the customer API key and, when needed, the Daytona target or region.
   Felan validates the key before saving it. A failed replacement leaves the
   existing working connection unchanged.

The API key is encrypted at rest and is never shown after saving. Felan
projects it into the isolated workspace only as `CUSTOMER_DAYTONA_API_KEY` and
the optional `CUSTOMER_DAYTONA_TARGET`. Felan's reserved `DAYTONA_API_KEY`,
`DAYTONA_API_URL`, and `DAYTONA_TARGET` values are not used for this
integration.

## Supported operations

The Daytona skill and bundled CLI support these control-plane operations:

* Sandboxes: list, get, create, start, stop, and delete.
* Snapshots: list, get, create, and delete.
* Volumes: list, get, create, and delete.

The integration does not provide workload shell, filesystem, Git, port,
session, resize, lifecycle-setting, secret, registry, runner, region-management,
or arbitrary API passthrough access.

## Confirmation and safety

The skill asks for clear user confirmation immediately before every create,
start, stop, or delete operation. Cancelling or declining confirmation invokes
no Daytona mutation. Reads do not require confirmation. Provider permission
errors are reported as operation-specific sanitized blockers, and CLI output
is bounded and excludes credentials.

Daytona API-key permissions remain the provider-enforced boundary. Use a
least-privilege key, rotate it through Daytona Cloud, and disconnect the
integration when the team no longer needs the customer account.