DuckDB 2.0 Gives Developers More Ways to Connect, Query and Build

We are proud to release DuckDB 2.0.0, codenamed “Cinnamon Teal” after the Spatula cyanoptera⁠, a strikingly reddish-brown duck found in the western Americas.What’s New in the Docs for 2.0
This page tracks the documentation for the features introduced in DuckDB 2.0, organized around the themes of the DuckDB 2.0.0 release announcement. Each section links to the relevant documentation.

CLI Agent Mode recognizes supported AI coding-agent environments, including Claude Code and OpenAI Codex, and adapts DuckDB’s command-line output accordingly. It presents compact results, flags truncated output and reports machine-readable errors. In one published test, it reduced query-output tokens by 59%, although overall agent cost and runtime did not decrease materially.

An extensible SQL parser lets extensions introduce new SQL syntax. An updated database-file format and improvements to compression and query execution further expand the release’s capabilities.

Built in the open
DuckDB 2.0 builds on work dating back to early 2026 and, for some components, considerably longer. Quack appeared as a preview release in May, and the team invited community testing of 2.0 development builds in September.

DuckDB 2.0 is designated a long-term support (LTS) release, with support through at least October 2027. DuckDB 1.5 support has been extended to March 2027 to give users additional time to test and migrate.

The release introduces a new default database-file format and a small number of breaking changes. Users upgrading existing deployments, particularly those involving multiple DuckDB processes or third-party extensions, should review the migration guidance before updating.

DuckDB 2.0 is available at duckdb.org/install. For a detailed technical overview of the new features and improvements, see the DuckDB team’s launch blog, Announcing DuckDB 2.0.0 LTS “Cinnamon Teal” Release notes, documentation and migration guidance are also available at duckdb.org/news.