At Dreamforce, Tableau introduced Tableau Studio, the next evolution of Tableau Desktop. The way we build in Tableau is about to change a lot. And for a small studio like ours that builds products on top of Tableau, it raises a lot of questions.
Here’s what we know so far, and what we think about it.
What is Tableau Studio?
Tableau Studio is Tableau Desktop with an AI agent built in.
On the right side of the screen, there’s a new Tableau Agent panel. You describe what you want in plain English, and the agent builds it: worksheets, calculations, formatting, dashboards. You can switch back to good old drag-and-drop at any moment, on the same workbook.
After using it for a while, it feels much better than the Tableau Agent experience available in Tableau Cloud. And there are a few things that make it better than using an external AI chatbot for Tableau.
It knows your context: the open workbook, your data sources, the existing sheets.
It knows Tableau’s semantic layer, so “revenue” means your company’s revenue, not a guess.
Skills and memory: best practices are built in, and you can share a project folder with your team’s own skills and conventions.
What about Extensions
This is what made me stop for a minute.
I opened Studio and asked the agent for a network chart linking Categories and Manufacturers in Superstore. A few minutes later, I had a force-directed graph built as a Viz Extension:
Yeah, sure, it’s far from perfect… but it was built with a simple prompt: “make a network chart”.
“Vibe-coded extensions”. You’ll hear that a lot from Tableau in the coming months. And let’s be honest: a simple chart type is no longer a product on its own. If anyone can generate a Sankey or a network graph in a few minutes, that’s not where the value is.
So should we continue building stuff?
A vibe-coded extension is also code that nobody maintains, nobody reviewed, and nobody owns. And in a company, that quickly becomes a problem:
Unchecked code on your servers: every generated extension runs on your Tableau Cloud or Server, often with libraries pulled from who knows where. Nobody checked them for vulnerabilities, licenses, or what data they send outside.
No consistency: ten people, ten prompts, ten network charts. Each one with its own settings, its own look and feel, and its own way of being used.
No owner: the person who wrote the prompt changes teams or leaves the company. Who fixes the extension when it breaks?
No updates: Tableau releases a new version, the Extensions API changes, a library becomes outdated… and the extension silently stops working in a dashboard your CEO opens every Monday.
No accessibility, no performance testing: a generated chart can look great on Superstore and freeze with a million rows, or be unusable with a keyboard or a screen reader.
Building a chart has never been easier. Building something a company can trust, support, and roll out to thousands of users hasn’t changed that much.
We think the future of Viz Extensions is less about “new chart types” and more about polished, reviewed, maintained tools.
So yeah, we think we should continue!
Workspace Extensions: a new playground
Studio also comes with something new for developers: Workspace Extensions.
Dashboard and Viz Extensions live inside a dashboard or a worksheet, for the people consuming it. Workspace Extensions extend the authoring experience itself, for the people building it.
For us, that’s probably the most exciting part of the announcement. A lot of what we build is already for authors: the Figma to Tableau plugin, the Custom Theme Generator, the Filter Manager… Imagine those living directly inside Studio, next to the agent, instead of in a separate tool.
Things are moving fast. We are like you, figuring things out as they come, and we’ll keep sharing what we learn along the way.
Meanwhile, if you want some food for thought, Tim and Kirk recorded a great conversation on Tableau, AI, and Claude Dashboards.
And with that, speak to you next week (probably!).
