GS Gábor Szárnyas On The New Stack Podcast

“The agents I tend to think of as like a bat flying in with bad vision and then doing echolocation, just doing maybe hundreds more queries and then trying to make sense of the data. And every now and then, some of these queries tend to be quite expensive. So if you run it in a cloud database, your bill may be a fair bit higher at the end of the month than you would expect.”

The New Stack Podcast · Hands-On Engineering Podcasts · November 2026

“The agents I tend to think of as like a bat flying in with bad vision and then doing echolocation, just doing maybe hundreds more queries and then trying to make sense of the data. And every now and then, some of these queries tend to be quite expensive. So if you run it in a cloud database, your bill may be a fair bit higher at the end of the month than you would expect.” — Gábor Szárnyas, The New Stack Podcast

Context

The host asked what makes DuckDB useful for AI agents. Szárnyas compares how agents explore data with how people do. He ties it to cost, since running locally keeps the bill predictable.

Transcript

The New Stack Podcast Around 23:57 into the episode
Gábor Szárnyas

…slash library, we do list a lot of projects that are done in an academic or research setup. And it's papers that ship a DuckDB implementation. And we found that most often than not, academics are really happy to implement their ideas in DuckDB and then ship it as a DuckDB community extension.

Jennifer Riggins

…new CEO, Andy Jassy, who was talking. And he talked about DuckDB and how it could help AI agents query data. So what makes DuckDB unique in this time of great change that is useful for agents? And then if it's useful for agents, typically it's useful for developers too. So what is that benefit?

Gábor Szárnyas

…of a few things. One is this simple install and easy setup that's beneficial for agents because they can run it very quickly. The other is this predictable cost approach. If you query something that is a database operated by someone else who charges some price for you for your queries, that can be a problem because the way these agents work is ultimately a bit different from how humans work. The agents I tend to think of as like a bat flying in with bad vision and then doing echolocation, just doing maybe hundreds more queries and then trying to make sense of the data. And every now and then, some of these queries tend to be quite expensive. So if you run it in a cloud database, your bill may be a fair bit higher at the end of the month than you would expect. With DuckDB, this will run maybe on your laptop or your local instance. So the cost remains predictable. And finally, I think the third thing for this is that it used to be a problem that the agent prototyped something for you and then you needed to move it to another maybe proprietary database system that is in the cloud. And people try to work around this with all sorts of clever approaches…

Jennifer Riggins

Okay, fair enough. And now that you've come back, listeners, from Googling Bat versus Duck, which I will do later to watch those videos, it's very interesting. Let's talk about the DuckDB CLI command line interface agentic mode. How does that work with data for coding agents? How do you?

Gábor Szárnyas

I think the CLI is turning this on, as we previously discussed, by default, whenever it detects that it's running within a harness of a coding agent. And it also, with this front-loaded information package that you see, helps quicker iteration. And ultimately, we have to acknowledge that software…

Jennifer Riggins

Okay. So as we referenced when I called Andy Jassy, your new CEO, he is. But Duck Labs joined Amazon last quarter. So I think those that are users and invest in the open source community, including your academic partners and friends, they kind of want to know what does that mean for the open source…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from The New Stack Podcast