DuckDB 2.0 LTS: Client-Server Mode, Agent Mode, One-Way Files

DuckDB 2.0 is out, and the embedded database now has a server. The DuckDB team announced version 2.0.0 LTS, "Cinnamon Teal," on October 21: a client-server protocol called Quack, an agent mode for AI tools that drive the CLI, triggers, and a new SQL parser. It is a long-term support release. It also writes database files that DuckDB 1.x cannot open. If DuckDB sits anywhere in your reporting stack, the upgrade order matters more than the feature list.

What actually happened

Per the official announcement, built from close to 20,000 commits since 1.5:

• Quack client-server protocol. Any DuckDB process can now serve its databases. The quack extension adds quack_serve(token = ...), clients attach with ATTACH 'quack:...', and the CLI gets -serve and -connect flags. It listens on localhost by default. For remote access, DuckDB says to put a TLS-terminating reverse proxy in front.
• CONNECT for other databases. The same CONNECT statement works against PostgreSQL and MySQL, with a remote pushdown optimizer.
• Agent mode. The CLI detects when an AI agent runs it. It then prints compact Markdown tables, says when results are truncated, stops runaway queries early, returns errors as JSON, and reports the expected cost of long queries before running them. In DuckDB's TPC-H tests it cut the output the model had to read by 59%. Toggle it with -agent or -no-agent.
• Async I/O and VARIANT. Parquet, CSV and native reads run in the background with multiple requests in flight, which helps s3:// workloads. A new VARIANT type stores JSON-like data in columnar form.
• Triggers. CREATE TRIGGER with BEFORE and AFTER timing and row or statement granularity, with some combinations not yet supported.
• Support window. 2.0 is supported until at least October 2027. 1.4 support ends November 17, 2026. 1.5 is extended to March 2027.

Why it matters for your business

DuckDB is the quiet engine behind a lot of small-business analytics: a Parquet export from Shopify, a nightly sales rollup, a notebook someone on the team owns. 2.0 changes three things for that setup.

The file format is one-way. DuckDB 2.0 reads and writes your existing files, and those stay readable by older versions. But a database file created by 2.0 cannot be opened by anything before 2.0. If one laptop upgrades and writes a new shared file, every 1.x script that reads it breaks. Upgrade readers first, writers last. DuckDB's own advice is to test on a shadow system.

Agent mode is the right default. A model reading padded ASCII boxes wastes tokens, and a model that fires an unbounded query on a large table wastes money. Cost estimates before a long query and early stops are the controls we want on any agent that touches data.

Quack is not a public endpoint. Localhost and a token by default is correct. Keep it that way, or put it behind a proxy you control.

Sources: DuckDB.