Daytona SDK and CLI 2.0.0 become the default on November 20, 2026
In short: if you install the Daytona SDK without a version pin (CI jobs, Docker builds, fresh installs without a lockfile), pick one of these before November 20, 2026.
Option 1, upgrade to 2.0.0: a small code change that our upgrade tool makes for you.
Option 2, stay on 0.x: pin with daytona<1 (Python) or npm i @daytona/sdk@0 (TypeScript). No code changes.
Installing from a committed lockfile? Nothing changes until you upgrade. Using the CLI? See the CLI section below.
What is happening
On November 20, 2026, version 2.0.0 of the Daytona SDKs and CLI becomes the default on PyPI, npm and Homebrew. There is no 1.x.
2.0.0 is a breaking release. It keeps the interface you use today under a v0 namespace and adds a new v2 one, so code written for 0.x fails until its client calls and most imports go through v0. Without a version pin, your next install or upgrade moves you to 2.0.0.
Option 1: Upgrade to 2.0.0 and keep your current interface
2.0.0 includes the interface you use today under the v0 namespace. It works with your existing API keys and organizations. In most code, two things change (old line marked -, new line marked +):
Python
- daytona.create()
+ daytona.v0.create()
- from daytona import Sandbox
+ from daytona.v0 import Sandbox
TypeScript
- daytona.create()
+ daytona.v0.create()
- import { Sandbox } from '@daytona/sdk'
+ import { Sandbox } from '@daytona/sdk/v0'
The Daytona client import itself stays the same. On Python, the v0 namespace needs the v0-sdk extra: daytona[v0-sdk].
Our upgrade tool makes these changes for you. The steps and install commands are in the upgrade guide.
You can then adopt the v2 interface gradually from the same package.
Option 2: Stay on 0.x (no code changes)
Pin your SDK as shown below. The 0.x SDKs and CLI keep working as they do today, and we'll announce any end-of-support date months in advance.
Python
requirements.txt or pyproject.toml:
daytona<1
pip:
pip install "daytona<1"
uv:
uv add "daytona<1"
Poetry: a ^0.x constraint already stays on 0.x.
Open-ended constraints such as daytona>=0.200 will move to 2.0.0. Add <1.
TypeScript
npm i @daytona/sdk@0
Avoid "*", "latest" and open-ended ranges such as ">=0.200.0" in package.json.
Old package names
daytona_sdk (PyPI) and @daytonaio/sdk (npm) stay on 0.x, so this change does not affect them.
Third-party packages
A package that uses the Daytona SDK the old way will break on 2.0.0, and you can't change its code yourself. Check whether it pins the SDK to 0.x. If it doesn't, pin it in your own project.
Python
Add this to your requirements.txt or pyproject.toml:
daytona<1
TypeScript
Add this to package.json (use resolutions for Yarn, pnpm.overrides for pnpm):
"overrides": { "@daytona/sdk": "<1" }
With npm, if your project also depends on @daytona/sdk directly, use this instead:
"overrides": { "@daytona/sdk": "$@daytona/sdk" }
CLI
The CLI has no v0 namespace. From November 20, 2026, daytona is the 2.x CLI and the 0.x CLI is installed separately as daytona-v0. To keep using the 0.x CLI, install it and update your scripts to call daytona-v0:
Homebrew
brew install daytonaio/cli/daytona-v0
macOS and Linux without Homebrew
curl -fsSL https://raw.githubusercontent.com | sh
Windows
powershell -Command "irm https://get.daytona.io | iex"
Questions? Reply to this email.
The Daytona team
Daytona is a cloud runtime for AI agents and developers. Built for scale and security, Daytona provides isolated sandboxes to run code, automate workflows, and power agentic applications.
©2026 Daytona Platforms, Inc. | Unsubscribe