Daisuke Matsushima

🦆 Announcing DuckDB 2.0.0 LTS “Cinnamon Teal” We are proud to release DuckDB 2.0.0, named after the cinnamon teal (Spatula cyanoptera), a striking reddish-brown duck found in the western Americas. 🌎 DuckDB 2.0.0 is the biggest DuckDB feature release so far. It ships a polished version of the Quack protocol, which turns DuckDB into a full-fledged server. It improves performance and lowers costs through supporting asynchronous I/O, a first-class VARIANT type, and a dedicated “agent mode”. It also empowers extension developers with a new SQL parser that allows adding new statements, clauses, and keywords, a new API to build on, and a new mechanism to distribute extensions more easily. In our announcement blog post, we summarize the highlights and then walk through the key changes and give guidance on how to migrate to 2.0. For the complete release notes, see the release page on GitHub⁠. duckdb.org/2026/10/21/announ… #DuckDB

DuckDB 2.0 is coming tomorrow!

Agent Mode in the DuckDB CLI 🤖 🦆 The #DuckDB v2.0 CLI has an agent mode that gets AI coding agents to a correct result faster and with fewer tokens. When the CLI detects an agent, it prints compact Markdown tables instead of padded boxes, says clearly when a result was cut, stops runaway queries early, and reports errors as JSON. Long queries announce their expected cost before they start, so the agent can decide whether to wait. Learn more in today’s blog post: duckdb.org/2026/10/09/agent-…

🐣 DuckDB v2.0 is around the corner! We started publishing alpha releases and encourage our community to give them a go. If you encounter any issues, we're more than happy to fix them before the release in October. Link in the thread.

🦆🤓 When Denis Hirn implemented DuckDB’s first recursive CTE operator in 2020, correctness determined the design: evaluate the non-recursive term once, then evaluate the recursive term until the next working table is empty. That established the right semantic contract, but reusable runtime state was scoped too narrowly. In the upcoming DuckDB v2.0 release, we assign those scopes explicitly. #DuckDB’s recursive CTE engine now treats recursion as one long-lived computation: it retains eligible epoch-invariant state, chooses execution modes from exact frontier cardinalities and physical work, probes keyed state directly and gives `USING KEY ... UNION` changed-key semantics. Read more in this preview of the forthcoming v2.0 release: duckdb.org/2026/08/25/how-du…

Today, @ducklabs_com is joining @awscloud. The move is expected to be completed by early September. Joining AWS gives DuckLabs the resources and reach to bring DuckDB, DuckLake, and the Quack protocol to many more developers and organizations – and to pursue ideas at a scale that would have been difficult for us to reach alone. The DuckLabs team will remain together in Amsterdam and will continue working for the Duck Stack community as an AWS subsidiary. Most importantly, #DuckDB and the other open source components of the Duck Stack will remain free and open source under the MIT license, with the non-profit DuckDB Foundation continuing its stewardship of the projects. This is a significant moment for DuckLabs and the Duck Stack community. It marks the end of one chapter that we are immensely proud of, and the beginning of another that we believe will take DuckDB much further. Read the full announcement here: ducklabs.com/ducklabs-is-joi… #AWS