Xenition is an AI workspace with 23 real editing surfaces — document, spreadsheet, slides, code, diagram, video studio, 3D and more — that all share one memory. A single chat can write a document, design a deck, build and deploy a full-stack app, render a video or reconcile a pile of invoices, and hand the result to a surface you can edit.

Yes. The free plan includes 25,000 credits a month and needs no credit card. Paid plans start at about $16.67 per month billed yearly, with usage-based credits shared across every surface.

What if the tool I need is not in Xenition?

Ask for it in the product chat. The team reviews every request and most ship within 3 to 7 days.

How is Xenition different from a chatbot with plugins?

A chatbot returns text. Xenition returns work on a surface you can keep editing, and remembers it. It also does things a single-surface tool structurally cannot: learning paths with decaying mastery that can refuse to teach a topic whose foundation has lapsed, invoice reconciliation where confidence comes from arithmetic rather than a model's self-assessment, explainer videos where narration is measured before any frame is cut, and meeting notes that expand your own typed notes and drop any action item that cannot quote its source line.

Can Xenition build and deploy a real application?

Yes. Describe an app and Xenition generates a working product with a real Postgres database, authentication, storage, an API, a web front end and a native mobile app, then deploys it. There are also 153 full-stack templates, each with a live demo.

Which apps does Xenition connect to?

121 apps including Slack, Gmail, Google Calendar, Google Drive, Notion, GitHub, Linear, Jira, HubSpot, Salesforce, Stripe, QuickBooks and Airtable. Agents can act in them, with an approval gate on anything destructive.

Is Xenition available outside the browser?

Yes — a desktop app for macOS, Windows and Linux with a global hotkey and silent auto-updates, plus native mobile apps for iOS and Android. The interface is available in 36 languages.

All connectors

Daytona integration

Daytona is a development environment management platform that provides cloud-based development workspaces with API access for automation

Connect Daytona to Xenition and work with it from chat, from an agent, or on a schedule — alongside every other app you have connected, in one workspace.

What you can do with Daytona

Ask in plain language and Xenition calls the right one:

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 dep
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.
Checkout Git Branch — [DEPRECATED] Checkout a branch or commit in a git repository within a sandbox. Use this action when you need to switch branches or checkout a specific commit in a git repository that exists within a sandbox toolbox. This operation modifies the working tree of the repository. Note: This endpoint is deprecated. Consider using alternative approaches for git operations if available. The sandbox must b
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 targ
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 Sandbox Backup — Initiates a backup operation for an existing sandbox environment. Use this action when you need to create a point-in-time snapshot of a sandbox that can be used for restoration or cloning purposes. The backup operation is asynchronous and the status can be tracked via the backupState field in the response (Pending -> InProgress -> Completed or Error). Note: This action creates a backup resource. E
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 ses
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
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 regi
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 yo
Create Snapshot — Creates a new snapshot resource that can be used as a base image for sandboxes. Use this action when you need to create a new snapshot with specific compute resources (CPU, memory, GPU, disk) and a container image. Snapshots define the base configuration that sandboxes will inherit when created from them. The snapshot can be built from a Dockerfile using the buildInfo parameter, or use an existing
Create SSH Access — Creates SSH access credentials for a sandbox environment. Use this action when you need to establish an SSH connection to a sandbox for administrative tasks, file transfers, or development operations. The returned credentials include a token and SSH command that can be used to connect to the sandbox securely. Note: SSH access tokens have a limited validity period. By default, they expire after 60
Create Volume — Creates a new volume for storing data that can be attached to sandboxes. Use this action when you need to provision persistent storage for your sandbox environments. Volumes persist data across sandbox restarts and can be mounted to sandboxes to provide additional storage capacity. Note: This action creates a new storage resource. Ensure you have the appropriate permissions in your organization be
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.
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 Sandbox File — Deletes a file inside a sandbox by its path. Use when you need to permanently remove a file from a sandbox that is no longer needed. This action is irreversible — once a file is deleted, it cannot be recovered. Ensure the file is not needed before proceeding with deletion. Note: This action uses a deprecated API endpoint. Consider migrating to an alternative method for file management when availab
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.
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 n
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 telem
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
Delete PTY Session — Deletes a PTY session and terminates the associated process. Use this action when you need to clean up an active PTY session that is no longer needed. This will terminate any process running in that session and release the associated resources. Note: This endpoint is deprecated. Consider using alternative methods for managing PTY sessions in new implementations. This action is irreversible — once
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 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 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.
Delete Session — Deletes a session from the Daytona platform by its ID. Use when you need to permanently remove a session that is no longer needed. This action is irreversible — once a session is deleted, it cannot be recovered. Any ongoing processes or data associated with the session will be permanently lost.

…and 20 more Daytona actions available in the workspace.

Give an agent access to Daytona

An agent you create can use Daytona on your behalf and keep working while you do something else. Every action an agent takes goes through an approval gate first, so nothing touches your Daytona account without you agreeing to it.

Other connectors

Frequently asked questions

How do I connect Daytona to Xenition?

Open the connectors directory in Xenition, find Daytona, and sign in when the authorisation window opens. The connection is managed for you — there is no API key to create, paste or rotate.

What can Xenition do with Daytona?

Xenition can run 50 different Daytona actions, including Archive Sandbox, Cancel Organization Invitation, Checkout Git Branch. You ask in plain language and the right one is called for you.

Can an agent use Daytona on my behalf?

Yes. Agents can use Daytona while you do something else, and every action passes through an approval gate before it runs.

Is there a free plan?

Yes. Xenition starts free with 25,000 credits a month and no credit card, and all connectors are available on every plan.