AMA about Tableau Studio with Matthew Miller, Will Martin and Lee Graber
1h 23m 16,204 words transcribed
Summary
Team DataFam TUG meeting #96 is an ask-me-anything about Tableau Studio. Matthew Miller had planned to present as a Salesforce employee but has since joined CodeMetal, so speaks as a community member who knows a great deal about how Studio was built. Will Martin, an architect on the Studio team, and Lee Graber, who worked on Tableau's extensibility, join from Tableau. Matthew explains that Studio is Tableau Desktop, forked, rebuilt to be agent-aware and then merged back, with no feature left behind; that a data app is a Tableau dashboard whose custom extension code is now packaged inside the workbook and served by Studio, Server and Cloud; and that workspace extensions are plugins that live in the editor rather than the workbook. Live demos cover an annotation workspace extension, a Tableau Public Explorer, the new Tableau agent and its viz templating engine, skills (including a Power BI converter skill the agent built), and Puppet mode, where Claude drives Studio through a local MCP and CLI. Questions from Kirk Munroe, Andy Holt, Fi Crocker and the chat range over data apps versus the agent, which licences are needed, bring-your-own-model plans, Tableau Knowledge, pricing in a headless BI world and whether dashboards have a future. The speakers note that branding, licensing and timelines were still being decided at the time, and Chris McClellan hosts.
Listen to this TUG
Prefer to listen? This meeting is also an episode of the Tableau TUG recordings podcast.
Key points
- Tableau Studio is Tableau Desktop rebranded and relaunched, not a new product: the code base was forked, made agent-aware, then merged back.
- One principle was no feature left behind, so even obscure Desktop features carry over.
- A data app is a Tableau dashboard, usually one full-screen dashboard extension, whose custom code is now packaged inside the workbook.
- Packaged extensions are served locally by Studio and by Server and Cloud, so there is no separate web server, certificate or domain to set up.
- Workspace extensions are plugins for the editor itself: they persist across sheets, the data source pane and the start page, and the new Tableau agent is one of them.
- Parts of Studio, including the agent, can be updated independently of the platform, so the agent could ship as often as needed.
- A GUI combined with a text interface suits creative work better than chat alone; a click can be worth a thousand words.
- The agent's templating engine matches field types to saved viz templates, and users can create their own templates.
- Skills are markdown files that teach the agent a workflow, and the agent can write new skills itself.
- Puppet mode lets a third-party agent such as Claude work in Studio alongside you through a local MCP and CLI, regardless of licence.
- The built-in agent is also an MCP client, so it can be connected to tools like Jira or Snowflake.
- Matthew's view on dashboards: they aren't dead, and most customers want a bar chart they can believe in more than they want vibe coding.
Jump to a chapter (33)
- 0:00 Welcome to meeting #96
- 0:58 Matthew Miller, now a community member
- 3:03 What is Tableau Studio? It is Tableau Desktop
- 6:14 Will Martin, Studio architect, joins in
- 7:49 Why build Tableau Studio?
- 9:37 What is a data app?
- 15:31 Data apps and the VizQL Data Service
- 16:31 Why use Studio if Claude can build workbooks?
- 19:22 Which model, and is it metered?
- 22:43 A quick tour: parts that update independently
- 25:11 Workspace extensions
- 28:31 Demo: an annotation workspace extension
- 30:12 Demo: Tableau Public Explorer
- 31:32 Lee Graber on workspace extensions for Server
- 34:36 The Tableau agent: put Claude in it
- 37:08 A templating engine for vizzes
- 40:49 Can agents create graphics on dashboards?
- 41:25 Tableau MCP and the public APIs
- 44:36 Puppet mode: Tableau and Claude side by side
- 50:35 Skills
- 51:36 Building a Power BI converter skill
- 53:18 Rewind, fork and plan mode
- 54:10 Data apps versus the Tableau agent
- 58:45 What licensing is needed?
- 1:01:45 Serving data apps from Server and Cloud
- 1:02:51 Kirk Munroe clarifies the licensing question
- 1:05:32 An MCP client, and Tableau Knowledge
- 1:08:27 Pricing in a headless BI world
- 1:11:34 Which model, and the cost of curiosity
- 1:12:50 Will people pay for viewers?
- 1:17:28 Cheaper licensing when anyone can vibe code
- 1:19:43 The future of dashboards
- 1:21:56 Wrap-up and what's next
Transcript
0:00 Chris McClellan: So welcome to Team DataFam Tableau User Group meeting number 96. This TUG aims to capture all the in-person and unrecorded presentations and give them a wider audience. So I don't care if you've presented at a conference before or not at a conference, or if you've just got something that you've built up on your own, everyone's welcome here. We'll find a time slot for you.
0:21 Get in touch. My email is team.DataFam@Gmail.com.
0:26 But today we have an AMA with Tableau Studio with this guy called Matthew Miller, who's currently the SVP Head of Product at CodeMetal.
0:35 But he's got some friends with him from Tableau and Salesforce, they'll pop in at some stage, uh, and we're doing an AMA about Tableau Studio.
0:44 So Matthew, I'm gonna hand it over to you.
0:47 Do you want some of these slides to look at as well? Or you just came to… Have you got your own slides? Do you agree to-
0:53 Matthew Miller: Oh, you've got slides
0:53 Chris McClellan: … we go straight to questions?
0:54 Matthew Miller: Those are great. Let's leave your slides up for a second.
0:57 Chris McClellan: Sure.
0:58 Matthew Miller: So, well, hello everyone. It's great to see you, uh, virtually, and hopefully in person again someday soon.
1:06 Uh, if this is a little weird for you, it's a little weird for me because, uh, as of really recently, I was planning to do this AMA in my capacity as a Salesforce employee, but I am no longer a Salesforce employee. However, I am still absolutely Team DataFam. Um, and honestly, there's a bunch of us here who predate the term DataFam. I consider myself Tableau community for life.
1:33 I quipped to someone that I'm just simply returning to the audience so that I can heckle during Devs on Stage.
1:40 So, uh, I no longer, you know, I would, I would've said at the beginning anyway that my thoughts here don't officially represent my employer, but they definitely don't because I don't work there anymore. Um, I'm now part of a company called CodeMetal, and, uh, so I'm here in the capacity as a community member and friend who just happens to know a heck of a lot about the development of this thing we call Tableau Studio.
2:02 What I thought I would do is, uh, give a little bit of the framing for why we did this, explain some of the… Like, answer, let's say, the frequently asked questions that I expect we'll have. Uh, I've got a fantastic set of questions that Jonathan collected very kindly in the link that he put in the chat here, so I can pull from those to answer questions.
2:22 I've got Studio itself and a bunch of demos ready to explain things. But really what I would love for us to accomplish in this hour-ish together is to make sure that you come away going, "Oh, wow, okay, I totally get it." Like, all your questions are answered. "I totally understand what Studio is, what it can do for me, for my team, for my company, um, today and in the future." So with that, this is an AMA, so, uh, feel free to throw…
2:48 In fact, please throw questions in the Q&A panel. I'll start with just a tad bit of framing, and then, uh, we'll go from there.
2:56 Uh, and if you have questions that you see in the stuff that Jonathan pulled together in that link that you wanna ask, feel free to ask those as well. So what is Tableau Studio? Tableau Studio is Tableau Desktop. In fact, I started making a slide somewhere of the top 10 things it is not. You know, Tableau Studio is not a panacea for the world's ills, et cetera.
3:15 It, it, it is not an additional product. It's not a new thing. It's not written from scratch. Here's what we did, and by we, I mean they. I'm gonna keep saying we, I think, for a really long time.
3:27 Uh, what we did is this.
3:29 So somewhere around, well, depends on how you think about it, but a number of months ago, you got the, the big code base of Tableau. It's enormous, 280,005- 280,000 files. And we forked that, so now we got two of them, and they're running in parallel, and we called this one Tableau Studio. And we tried to see what we could achieve with, like, a, an elite team of folks, uh, some of whom are on this call, and I'll introduce in a second.
3:56 Just went as fast as we possibly could and did a whole lot of things that we'd always wanted to do with Tableau. Why do we take that pattern of running them in parallel? Well, what if it failed and we kind of mucked everything up? So the normal Tableau Desktop development continued at pace, fixing bugs and adding features and stuff. And so along the way, we would occasionally, like, bring in the stuff that they were doing, so we kept up to date.
4:17 And there was a point, I mean, Will, you might have a different view on this. I think five or six weeks into that project, we were like, "I think we're onto something here." And so at some point, Studio just became Desktop. They all became one. So Studio is a rebrand and relaunch of the venerable Tableau Desktop, but it is fully 100% Tableau Desktop.
4:35 And one of our key principles was no feature left behind. Those weird, weird, weird ones. And I love asking people what their favorite weird, esoteric, no one knows about it feature of Tableau is. So if you'd like to have a little fun, throw your favorite, "I bet nobody knows Tableau can do this feature," in the chat. But I promise you, we kept it, 'cause that's the thing about Tableau Desktop, it's, what, 3,700-page PDF manual that you can do everything with it.
5:01 So what if, though, we thought, we could take that and we could make it completely agent aware? So that means, like, a, a kickass, world-class agent in Tableau Desktop with full access to the workbook and full access to the command surface of Tableau. The, the roughly, well, it's 200- 2,500 APIs, internal APIs, of which about 810 are, like, human accessible.
5:25 Like, you click on this button and it does that thing. Give, give agents the ability to do things like put pill on shelf and swap axes, but also let it just bulk edit the TWB to do things like spellcheck, Matt Francis, if you're listening, or whatever else you want. Bulk styling.
5:42 We also made it possible to plug in to Tableau from the side with a local, what we call an MCP tool, so that third party agents could have that same interactive canvas. We did a bunch of other really cool things too that I'll get to in a bit. But the key thing to know is Tableau Studio is Tableau Desktop. Just like we went from Tableau Online to Tableau Cloud, we rebranded Tableau Desktop to Tableau Studio, and that is- That's what this is.
6:07 So now why did we do this? Well, we'll come back to that in a second, but I thought I would, since he's on, I don't know if Lee is on yet. I was kinda stalling. Will?
6:15 Will Martin: He, he's not. So I, I
6:17 Matthew Miller: There we go
6:17 Will Martin: … Will, um-
6:18 Matthew Miller: I wanna choose Will.
6:20 Will Martin: Yeah. Uh, so Will Martin, I ac- I actually do still work for Tableau, uh, unlike our other venerable presenter here. Um, but I'm an architect on the, the Studio team. Uh, this, Matthew doesn't know, but it is looking like for the very first release of Studio, it might not fully have the branding, the rebranding of all of Desktop as Studio. As everything that he has said fits, but there are, say the naming and the marketing are kind of out of the hands of product and engineering degree, and there's some, there's some, uh, negotiations happening there.
6:57 Matthew Miller: Uh, I mean, are you telling me that the URL for Tableau Cloud might still say online.Tableau.com for a while?
7:02 Will Martin: It, it might say that, yes.
7:04 Matthew Miller: Well, I, it, the, it doesn't surprise me. It, it's hard to make a lot of changes. So that's, that's news to me here, uh, that we're, we're gonna maybe at, at release it'll still possibly say Desktop, but anyhow, Tableau Studio, uh, the soon to be completely thoroughly rebranded. I mean, there's so many places where it, it does say Desktop, it'll probably take a while.
7:23 So w- um, and thank you, Will, for jumping in. Will is the architect behind a lot of this, has done a lot of the hacking and spelunking to prototype a lot of these ideas that then the team has gone and built out. So I'm really glad he's here to answer your questions. He's also a fellow TWB nerd. That's kinda how we, like, hit it off. Um, like, I bet I can't out-TWB nerd you.
7:45 Oh, yeah? How do you define a group filter and where is it used?
7:48 I digress.
7:50 So why Tableau Studio?
7:53 Well, the premise was this, started actually a couple years ago, with a conversation around what do people really use Tableau Desktop for? Like, the original thought and intent was that Tableau Desktop was gonna be a tool for everyone in the entire world. Like, if you were a truck driver, you'd just fire up Desktop and see and understand your truck driving data.
8:14 If you're a CEO, you'd just open up Desktop and see and understand your CEO data. No matter what your role is, a dentist, who knows, you would use Tableau Desktop. And I think it's fair to say that, like, that's not what's happened. It's found an enormous market, and a lot of folks have used it. Tableau Desktop is absolutely transformative for me.
8:34 This isn't about my Tableau journey, but it started a wicked long time ago when I was like, "Holy crap, this is amazing. I never want any other tool to explore data." But what, what we realized was the predominant usage of Tableau Desktop was to create things for others.
8:48 That is, it was effectively a, an, a no-code or very low-code analytical development environment, an IDE.
8:57 Oh, well, what if we really lean into that and go after the work that people are doing to try to build stuff for others? Build data sources, build dashboards, build vizzes, and how can we really accelerate high-value offerings? So that was the original, um, like thesis behind this.
9:14 I don't know what your other slides say, so if you wanna go ahead, Chris, to the next one, I can tackle those questions one at a time. But hopefully that answers questions about, like, what is Studio, it is Desktop, um, and why did we build it?
9:26 Chris McClellan: That's okay. We're not really onto the questions yet, but I thought you might want to open with that.
9:29 Matthew Miller: There you go.
9:30 Chris McClellan: And the next one was about data, um, Tableau Studio as well, just in case, and data apps.
9:37 Data apps.
9:37 Matthew Miller: Right.
9:38 What is a data app or a data app, depending on, um, where you live?
9:44 So the, um, data apps are a marketing buzzword.
9:48 Why don't we step back though to what an app is from the perspective of, let's say, normal people who aren't living in the data and analytics industry.
9:57 Uh, when I open this, uh, weather thing on my phone, that's an app. If you ask any normal person who isn't, like, in the bubble of tech, they'll say, "That's an app." Where'd you get it? I got it on the App Store. And like, they don't really care that, like, the weather app doesn't have write back, it doesn't have workflow integrations, it can't update a Salesforce record.
10:18 They don't care if it was vibe coded. They don't care if it was human coded, whether it's an electron app or it's web-based, or they don't care about that. It's an app. And so to me, the term data app is purely just an experience that any normal non-tech bubble user would say, "Yep, that's an app. It's got data in it." Which could be just a, a report, a vaguely interactive report like the weather app for monitoring something.
10:45 It could also be something with greater interactivity, like a, like a, what we would think of as probably a typical dashboard, all the way to a full-fledged, like, application, like Salesforce CRM, where you can write things back and forth. So th- that's how I think about an app. The term data apps though means things that are built in Tableau that are all or mostly created with custom code that's authored by an agent and embedded, actually properly embedded as part of the workbook.
11:17 That was something that was completely net new in Studio. So if you look at that slide that Chris has got shown here, like those are not what we call like a native viz. And by a native viz, I mean something where you drag and drop stuff onto columns and rows and use the built-in bar charts and line charts and pie charts. This is something where we've created a viz extension and/or a dashboard extension on the fly.
11:39 Now, data apps are dashboards.
11:42 They are often just a dashboard shell, just one big zone that has one big, uh, full-screen, um, dashboard extension in it, and that dashboard extension is the custom code. So what's net new? Like, haven't you always been able to do that? Like, you could totally make a dashboard five years ago that was just one huge dashboard extension that you custom coded.
12:04 People have been doing that for ages. Look at, like, um, some of Tristan's stuff or Merlin's things or, um, Marcelo's awesome dashboard editor. But The difference is that those can now be embedded in the workbook, like actually in the workbook. So here, you know, I gotta not assume too much Tableau nerdery. Uh, when you save a Tableau workbook as a packaged workbook, we're saving both the workbook itself, which is like the metadata, along with the related assets, like hyper files or Excel files that you need, uh, and maybe some images.
12:33 And in this case, we are now also packaging that custom extension itself. Crucially, and interestingly enough, a data app, as we're calling them, doesn't actually have to be vibe coded. That is, it doesn't need to be agentically coded. You can do traditional software development. Tableau doesn't actually care or know the provenance of the code and the percentage of it that you hand wrote or agentically coded.
12:57 What it just knows is I've now got an extension that, or extensions, that are part of this workbook. What's cool about that is I can create a completely custom analytical experience and send it to Andy Cotgreave, for example, who's about to drop from the chat to probably go play board games, I'm guessing.
13:15 And, and then Andy can open it, and it works just as well. That is, like Tableau Studio is now serving that extension to you locally, safely, securely, and directly. There's no need to stand up another web server, and go out to Heroku, and set up a certificate and a do- domain all to host this. So I can tell a coding agent, "Make me a custom viz," and it just does it, and it puts it directly into my workbook and it just works.
13:40 What's even more cool is that now you'll be able to publish those to… Yeah, Jacob, you've been pushing the envelope. I, I, I know I've said this publicly and privately, but you're, you're kicking ass and taking names. Some really, really cool stuff you built. I love that globe. Um, so you should, you should like blog more and do more videos, 'cause you, you're doing really, really cool stuff.
13:56 It shows off, um, and, and I'll just shout out Jacob for a second. Like I, I actually don't think that the long arc of travel is everything's totally custom code. I don't think people want to administrate that or update it, but there's a lot of power in a metadata-driven experience.
14:14 For example, if I open a Word doc from 2007, I'm opening metadata, not code, whereas the code of Microsoft Word, hopefully, thankfully, has been upgraded over the years, and new features and bug stuffs have been fixed. So I open up that piece of metadata Word doc from 2007, and it just works, and that's kind of the thing that Tableau's always been able to do.
14:33 You can open a version 1.0 workbook, and unless it has a, a TDE file, um, otherwise it'll work just perfectly fine right out of the box. We've always been big on backwards compatibility.
14:46 So, uh, what we're, what we're doing here is enabling you to completely customize. That's what a data app is.
14:54 Um, and, uh, did I mention? Yes. There, and they're also, um, will be served from server and cloud. So if you vibe code something, or custom code, and embed that, and package that in your workbook and publish it, server can serve it to you directly, which is amazing. I think one of the rate limiters for extensions has been, well, I gotta again, find a server to put it on internally, and put a certificate on it, and get my administrator to allow it.
15:17 Um, and because we used extensions, we already got all the existing governance. When I say we, I mean they, got the governance just out of the box.
15:25 Okay.
15:26 That's data apps. Um, any questions as we go? Just throw them in the chat.
15:31 Will Martin: Just gonna, just gonna… A quick comment, too, is one difference as well between this and, uh, viz, the, uh, existing viz extensions is the use of, like HBI, so sorry, VizQL data service, and the VizQL data service endpoint as the thing that backs it. So if you look at, like the view that's currently… Oh, that's a Tab Next data app, but, uh, a Tab Core data app as well, uh, you can issue arbitrary queries to populate it.
15:56 Um, so viz extensions we're still using encodings and everything. Um, so you can put things on color or whatever else, uh, but that defines your data table, and there's a little bit more flexibility now 'cause now even within a viz extension or data app, you'll be able to use, um, that VizQL data syntax as well to issue arbitrary queries. So you can pick and choose, you know, do custom summations, whatever, um, and not need to kind of have like a helper, um, encoding or something to power that.
16:27 Matthew Miller: Yep.
16:28 Right on.
16:28 Um, I see some questions in the chat. Let's tackle them while we're at it. Uh, Kirk says, "Given that I can create workbooks from Claude with the Claude MCP 26.3.1 and ask it to build old school multiple extensions or a single extension, why would we need Studio to build them?" Well, that's a great question. So I, I don't think creative professionals prefer what are called TUIs.
16:51 I think they prefer GUIs, and Tableau is weird in the sense that it's a, it uses… Like people who do data work in general are weird because we require orthogonal skills. Like it's a little bit nerdy and technical, but it's also a bit creative, and if I'm working on something creative, I actually wanna see it live in front of me.
17:08 And with Studio you've got this great, you know, IDE for seeing and exploring, and again, you can use the mix of the native tooling that you've already got and we're familiar with, along with just describing it in a text UI, and see the asset happen in front of you, and text UIs alone don't do that.
17:24 Um, even things like MCP apps don't do that, 'cause the experience is sort of scrolling off the screen ahead of you.
17:30 So, uh, and I don't, I don't think… I've not met anybody yet who uses Photoshop who's like, "I just want to spend all my time in Claude telling it to move a thing 10 pixels to the left." Uh, and in fact, um, it's funny, I would've said one of our competitors, but now I can say, um, that my good friend Charles Schaefer at Hex, they've got… They're doing this really, really well with those generative chart controls.
17:50 K- I was kind of envious of what they de- they did, because they, uh, when I talked to Charles about this, he was like, "We realized people were vibe coding things by describing them in a text interface, and but the last mile was really frustrating," 'cause they're like, "Dang it. I just want to move that thing 10 pixels over. No, not quite that blue.
18:07 This blue." And that last, you know, five yards or last mile or whatever, was taking a ton of back and forth with the text UI, where a graphic UI you just go click, drag, snap, done.
18:19 And that, that was a bit of an aha for me. So what you can do, and I don't know how well this has been, you know, really highlighted yet or real- how far we've really pushed this, Will might know more with the skills, but, um, you actually can do that in Studio. You can say like, "This is what I want on the marks card," because you can customize the, the marks card.
18:37 So you can create like a, um, a generative custom, almost ephemeral UI for authoring.
18:44 That's a long way of saying I think there's a lot of power, like a click is worth a thousand words.
18:48 So, you know, yeah, you can totally just describe the thing you want and then bam, you know, stone tablets, there it is. But I think a GUI combined with a TUI is a really powerful experience for creative work.
19:03 All right, um.
19:04 Will Martin: Awesome.
19:05 Matthew Miller: Questions. I got demos galore.
19:07 Will Martin: Questions.
19:08 Matthew Miller: Uh, all right. What LLM-
19:09 Will Martin: Well, do you want to, do you want to cut to some demos to begin with?
19:12 Matthew Miller: Uh, we can do. I just see a question come on.
19:13 Will Martin: Yeah.
19:13 Matthew Miller: I can hit that. Um, I also realize I neglected to grab one thing off GitHub that I need. Um, we'll come back to that.
19:22 All right, uh, let me tackle the first question. What LLM or AI model will Studio use and how will the token usage work for it? Is it unlimited or hitting a balance somewhere?
19:31 Uh, unless something has changed, the plan with Studio is that it will be unmetered. That is we're putting the risk there, putting the risk onto Tableau, uh, of managing that cost. And, and so, uh, and then in terms of which specific model, out of the box, this will use the, uh, INS, uh, Agentforce trust layer. I believe it is a Claude model. It was Sonnet last I was involved.
19:56 Uh, however, in certain cases you'll be able to bring your own model, and that'll flow through, I believe it's Server, Will.
20:03 Will Martin: Yeah.
20:03 Matthew Miller: Um, will support bring your own model first and then cloud later.
20:06 Will Martin: Yep. Yeah, so at the moment, um, and I think it has been officially decided, uh, I hope I'm not… They're like, there's still some discussions about the licensing model that it's under.
20:18 Um, yeah, so Jonathan has a little bit of an alpha build here. Um, but it's, uh, the plan is, yep, we will, um, eat the cost on the cloud side.
20:30 Um, and then on the server side, it basically proxies through and just like you can set up today some of the AI settings, the LLM settings, uh, you'll be able to just hook that up and we'll proxy through your server, and then it'll go to the, uh, uh, to, uh, it'll go to whatever backend you have.
20:50 Matthew Miller: There you go. So yeah, let's talk about the agent. Uh, it, you know, again, I, I know some of you are here because I said it was kind of gloves off, et cetera. You know, I have enormous love and respect for my friends and colleagues at Tableau and the challenges of making difficult decisions. Um, and of course I will continue to respect my NDA. However, uh, it is my personal opinion that what, what has driven the phenomenal hockey stick adoption of conversational AI agents has been that there's a free version that's actually pretty darn capable.
21:22 Um, and so the, the, the strategy that I would love to see is where, uh, everyone, even in Tableau Studio for public and Tableau Studio free, et cetera, gets some amount, a reasonable amount of AI capability that's full feature. Where you can go, "Wow, that's awesome," but then after, you know, X number of tokens or a number of minutes or whatever, it goes, "Sorry, you got to wait and it reset in five hours or seven days.
21:46 You know, call your salesperson." I think that's fair. I think people understand that.
21:50 Um, so that's my personal belief, is that the agent itself. But I'll show you some things, um, that, that I think will show you, look, there's other possibilities as well, even in addition to this agent. Put another way, a thing to take away here is Tableau Studio is not just the new Tableau Agent. There's a bunch of really cool new stuff that's useful even if you're bringing your own LLM or bringing your own agent.
22:14 Uh, Tim Cady is asking a ballpark idea on timing for bring your own LLM for cloud. That's a question for someone who currently has a Salesforce paycheck. Will, you want to-
22:23 Will Martin: It is. Yeah, I mean, they are actively working on it, I would say. I don't know their exact timeline, uh, because I'm not the PM of that project. I'm not gonna like say a definite timeline, but they are certainly looking at it, like actively right now.
22:43 Matthew Miller: All right. So, um, for those who haven't like played with this or tried this yet, let me give you kind of a quick whistle stop tour, and then I'll, I'll go back to the AMA.
22:53 So you'll notice this looks refreshingly like Tableau Desktop, 'cause it is. But one of the really cool things that the team has done is ripped out some of the pieces of Tableau that were written in very hard to change, uh, C++ and replaced them with like, uh, independently updatable capabilities. What's that mean practically, Matthew? Use simpler words.
23:14 Well, you ever been stuck on like 2023.2, but like Tim Cady won't upgrade the stupid server? You've been waiting a year, you know, 'cause of whatever. I don't know what Tim's reason is. Um, good to see you, Tim. And so you're stuck on 2023.2.
23:28 And, and so what we're doing now is like you can be on a certain version of Tableau Studio, but we can independently update, uh, when I say we I mean they, certain parts of the product, and one of those is the new Tableau Agent. So this is independently deployable. And our mental model here is VS Code. Yeah, come on, Tim, upgrade the server. Uh, our mental model here is like virtual, um, Visual Studio Code, which many of you have probably used, where like core parts of it can just be independently updated while the sort of platform stays the same, and I love that.
23:59 So, um, the cadence for release for Tableau Studio anyway, like the whole platform is going, uh, I believe, and I don't want to speak out of turn, but, uh, is going from, uh, three or four times a year to much more frequent. Will b- will be able to comment on the timeline for when that'll start. But, um, the agent itself can be shipped like three times a day if need be, which is awesome, or more.
24:21 There are other parts of the product that also are, uh, beginning to behave that way. Uh, this new sheet pane, did you notice that little loading indicator?
24:29 The new sheet pane, this was always just a static image. This actually has some new capability built in. It will only fire currently in a few unique cases, like you have to be signed into Tableau Cloud and have certain things, but there's some cool stuff that this does. So this whole pane here is like a, a whole new independently deployable thing.
24:48 And also the start page, uh, if you saw the demo at Dreamforce of the agent mode, like this venerable start page, which, you know, is usually just a quick stop on my way to doing other interesting things in Tableau, will be completely replaced with a whole new agent experience. You'll still have all that capability, but nicely redesigned, but now it'll be something that can be easily updated, which just gives the team the ability to iterate really, really fast.
25:12 A foundational capability that makes that possible is what are called workspace extensions. This is a nice segue to that before we come back to the agent. And again, I'm keeping an eye on the chat in case you have questions. So what is a workspace extension? We know what viz extensions are. They're custom viz types, and we know what dashboard extensions…
25:29 Um, yep, Will Perkins made this shirt. I was hoping you'd turn up. Good to see you.
25:33 Uh, and dashboard extensions are custom extensions you can put on dashboards. Well, a workspace extension does not live in the workbook. It's like a Photoshop plugin or a Pro Tools plugin. It's a thing that's there in the editor, but it's not actually in the content itself. So those show up under this new menu up here. I'll see if my screen zoom. That's a lame screen zoom.
25:53 That's a little better. So now I have this, and I've added a couple of my own. You can now manage your workspace extensions, and I've added a couple of additional ones. So the Tableau Agent that you see here over on the right is a first party workspace extension. It's one that Tableau built, and when I say we, I mean they.
26:10 Uh, and there will be a bunch of those, places in the product where that's like a first party plugin that the team maintains. It can easily update as quickly as they want and move really fast.
26:18 But you can add your own. So you can imagine, uh, let's just say, oh, I'm just making something up. You work at like a big bank, and you, um, you know, your server admin hasn't upgraded the server in three years, but, you know, you, you've gone and built your own workspace extension, and you can, like have your own custom experience that interacts with Tableau like a plugin.
26:37 Like it can read and write the TWB in real time. It can do things like put things on shelves and swap stuff around. Basically anything that you can do with a, with a, you know, mouse or track pad in Tableau, it can do at least in theory. I'm sure Will's eyebrows are going up, but in theory they can.
26:52 They, they have technically the ability to do anything in the product. I think there will be some limitations at GA.
27:00 So that concept of like a plugin is what made it possible for the team to build this new Tableau Agent that I'll come to in a sec. I'll pause for a second to see if there's any… Poor Tim.
27:11 Um, we, uh, any- let's see if there any other questions here.
27:15 Should I be looking at the Q&A pane or the chat pane, Chris?
27:19 Chris McClellan: That's okay. There's no one's, no one's typing in Q&A yet. They're all just in chat.
27:22 Matthew Miller: All right.
27:22 Chris McClellan: That's fine.
27:24 Matthew Miller: So what's new about this workspace extensions thing? You might go, "Well, didn't we have something like that before with like Show Me or the Data Guide?" Uh, there was never a place in the product before where you could have some durable, persist experience that followed you around as you went from part of the product to part of the product, and sort of retained state.
27:42 But now, and I'll just show you as an example, I'll pop this thing out. This Tableau Agent, uh, is the same. So I'm just gonna type some stuff in here like, "Why hasn't Tim upgraded my server?" And, and then you'll notice as I go from tab to tab, and even all the way over to the data source pane, and even the start page, it sticks with me, and that has never been possible before.
28:05 Will did a lot of the really hard yards to… So shout out Will Martin for doing the hard yards to get this to work, and that means it's possible now to build add-ons that truly are like aware of the total context of what you're trying to do. Whereas like a dashboard extension would go out of scope the second you went to a different dashboard, workspace extensions can be docked on the sidebar or floating as you saw, and you can also have multiple of them open at a time.
28:29 Some of you have seen this demo, but some of you haven't. This is one, uh, that I made just to kind of show off what is possible with workspace extensions. I took an OG feature that many of you know and love. Let me go find, uh, this looks like a good viz for it. Actually, this one looks better.
28:45 And the annotation feature, so many of you know there's the annotation feature where you can annotate a mark or a point or an area.
28:53 So I thought, "Gosh, is there, is there a way I could make a plugin that can, uh, read the data out of the viz in real time just to show you what's possible?" So this thing, as I go from tab to tab and sheet to sheet, notice it reanalyzes the contents of the sheet. So as I go here, it's like, hey, I can see, I'm gonna clear all the annotations. It suggested that these might be interesting annotations, and so I'll say, "Yeah, this one's kind of cool.
29:18 Um, whoa, Tim, check this out," and I'll click apply. And it's gonna…
29:26 Aw, womp, womp. It's gonna fail 'cause of some probably little bug. Come on. Give it… There we go. All right. Well, um, I'm not gonna blame the studio team. I'm gonna blame my vibe coded workspace extension most likely for that one, 'cause you can see it worked fine here. So notice it found interesting values in the data, and threw little annotations in.
29:45 That's kinda cool. Now, not the most like high value thing, but what I wanted you to see is, like, I built that in seconds. So the idea with workspace extensions is now for those things where you're like, "Man, why doesn't Tableau have X, Y, Z feature?" It can, and rather than clutter the product, which already has, let's face it, 3,700 page manual with tons and tons of buttons, drop-downs, and stuff, if you want your own feature, build it.
30:09 Workspace extensions are the way to go.
30:12 I have one other. This is supposed to be a pièce de résistance. We're gonna have fingers crossed that this works.
30:17 Um, they call this the Tableau Public Explorer.
30:20 So this lets you browse various Viz of the Day, um, search by whatever. Uh, let's try… Oh, look at that.I could literally, I could not have made… I did not make this up. I didn't pick this. It just did this on its own. So I thought, wouldn't it be cool if you could add that inspiration? Normally, if somebody has given you permission, like has made it possible to download a Tableau Public viz, you got to go download the workbook and open another version, and, and then right click on the tab and hit copy, and go over here and hit paste.
30:48 And who wants to do that? You're just going to click inject.
30:50 This is… Will Martin, I'm very excited if this works.
30:53 It didn't work. Oh, so close. Um, injection failed, unknown error. Uh, maybe it's because, um…
31:02 So, well, in theory, what should have been possible is that this can read from public and then grab that and inject that directly into my workbook. It is, uh, theoretically possible, um, it to do this. So if you can do it with by hand, you can do that with a workspace extension. So now we get to the fun part, which is the agent, the actual first party agent.
31:25 Let me see if there's any questions though, because this is, in theory, an AMA and not just Matthew rambles through the product.
31:31 Um-
31:32 Chris McClellan: The other Will Martin had his hand up.
31:34 Matthew Miller: Oh, Will, you got your hand up. What's up?
31:36 Will Martin: Uh, I think, I think the Lee Will had it up. Lee, go ahead.
31:40 Lee Graber: I, I was just, you know, since you were just talking about everything, I, I wanted you to mention that while the initial focus is, well, for me, oddly, uh, on desktop or studio, whatever, for workspace extensions, a lot of the original, sorry, Will, original, original thought around this was for server, with the original destination location being the viewing toolbar, where many people have wanted to be able to plug things in, but are forced to put them into dashboards and workbooks themselves.
32:19 But now you can imagine all the things that we currently have there, like data guide or commenting or anything, those could have all been workspace extensions.
32:29 And you can actually make your own.
32:32 Uh, we're not actually enabling it quite yet, but conceptually you could ship these and deploy them to your server in a standalone package. So you deploy the code itself too, if it can run as a standalone extension, and it'll just show up there, and you'll be- have access to the side pane, uh, and information about the viz being viewed next to you.
32:58 And, you know, you can't do authoring things from there, but you'll have access to all of the APIs.
33:07 Matthew Miller: Uh-
33:07 Lee Graber: So-
33:07 Matthew Miller: I apparently sent my actual presenter login to Lee and Will when I was like, "Hey, you're going to join." And so that's why there are three people with my face in the chat, and all of us are now replying as Will Martin. But the person you just heard speak is Lee Graber, who's a dear friend. And, uh, Will, you're also a dear friend. I just want to say that no doesn't mean false.
33:29 And, and Lee's a great guy, and Lee's the one who has just relentlessly, uh, pushed for this vision of extensibility in Tableau. He worked on a lot of the e- extensibility stuff like dashboard extensions.
33:40 And so he, he… The vision for workspace extensions goes well beyond just Studio. I pulled up the, um, infamous pine tree viz. You can see I need to go water it.
33:50 And, uh, and so what, what Will's talking about is adding new things here. So the… There's actually this capability, some of it's already built, to like target different places in the product. So targeting a button that goes on the toolbar that might open the sidebar here, or, uh, uh, adding something maybe to the, to the tool tip bar. Um, so you've seen a few examples already.
34:12 One is this sidebar target, one is the new sheet target, another is the start page, but there's a whole bunch of other places where, uh, the team is looking at extensibility. And a lot of it's driven by Lee's vision for what are called packages more broadly. So you heard that here first. Workspace extensions are like ship point one, you could say, of packages.
34:32 All right, so now you get the idea of workspace extensions and plugins. Let's talk about the actual Tableau Agent. And, um, I'll go look to see if there's, uh, anybody else or any other questions. All right. So the actual agent itself. The agent itself, uh, you may have used the former Tableau Agent inspired a bit by the Slackbot team. There was a thing called Slackbot, whose sole purpose was to occasionally be like, "Do you want to leave these channels you don't use?" Now, Slackbot got this massive glow up, and they did that by ripping out the old one and replacing it with one that was built with a modern agent harness and leading edge foundation models.
35:07 So that's what we did. And like put sort of bluntly or tongue in cheek, you know, the mantra was like, "Put Claude in it. Let Claude control it." Though it doesn't have to be Claude, but it was kind of the thought process. So modern agent SDK, modern foundation models, and a, a set of, uh, system prompt, a set of expertise and resources and skills.
35:27 So this thing has access to, as I mentioned, reading and writing the workbook.
35:31 Uh, I guess I should share a little nerdery I learned in this process that may be helpful to those who are thinking of doing this kind of extensibility.
35:38 I had thought that like when you hit the save button in Tableau Desktop, there was some code that like assembled all the different things you've worked on and saved them somewhere. Apparently not. Uh, the, the TWB, if you've ever looked at one, is basically the way Tableau thinks about everything. And so if you edit that in memory, Desktop just snaps to it.
35:55 So you have the ability as an extensions, a workspace extensions author, and the agent has the ability to just make bulk changes to that. So, um, I don't know. We're going to shoot from the hip here. Um, could you, uh, translate all phrases in this workbook into… This is going to be a really bad… This is going to be a great demo. Shooting from the hip.
36:15 I don't know what's going to happen.
36:17 But, uh, I'm just going to ask it to translate phrases into Japanese. So it's going to dig through all the text. If you know your TWB, you probably know there's some things that actually don't actually get stored in the TWB that are text. So if there's some things left over that are English, there can be some good reasons for that. But we'll see what happens.
36:33 And, uh, oh, it wants to ask me which we could start with one. That sounds like nice and safe. So this sounds often like, like a modern- Coding agent, except it's like wire right in here.
36:43 It has access to a local MCP and CLI that can read the data sources, write the data sources, make new sheets. There are also some things it has that we've never had before. One of those is a viz templating engine.
36:56 Um, cool. There we go. So it localized all my, uh, dashboard, and, um, I, I don't speak Japanese. Where's KT?
37:05 Um, but this looks pretty good.
37:08 Further, it has a templating engine. So this is something we never had before.
37:13 Uh, let's see. Just for a little audience interaction, what's a good question to ask about the world indicators data source? Anybody got one?
37:21 Oh, yes. Tableau Agent got a massive upgrade fee. It's just completely, uh, rebuilt from the ground up. Anybody got a good w- uh, world indicators question?
37:31 Don't all jump in at once.
37:34 Okay.
37:36 Let's take the data from internet and mobile phone usage, but, um, show me, actually make me three other interesting vizzes that, uh, show off this data.
37:54 Uh, not the best question, but that's okay. It's the power of LLMs. They'll figure it out. So what this is gonna do is look at the set of templates. The templates that ship with Studio use the venerable bookmark format, which is a way of saving a worksheet standalone. There you go. So it has, if we look here at what it's actually doing, it's looked at the list of available templates that it has, and it's found those templates by saying, "All right.
38:19 I've got fields of this type." So it's like an abstract. It looks for like an abstract. I've got geographic fields, I've got date fields, I've got number fields, and it, and then the MCP that ships with Studio provides a, this bank of templates, and it can find like slots where those match up, if that makes sense. So it doesn't have to match like sales to sales, it can just find a floating point and a floating point, or a geographic thing and a geographic thing.
38:44 And those templates can be edited by you, the, uh, the user, and, um, and they can be extended as well. So how do you do that? Let me show you. Actually, um, y- you may, um… I don't know if this has changed, Will. I- are the templates still, um, reading the bookmarks folder?
39:03 Will Martin: Yeah. That hasn't changed.
39:04 Matthew Miller: Okay, great. I just wanted to make sure I wasn't giving misinformation. And, uh, documents.
39:11 I gotta find this on my other monitor.
39:14 Come on. You can do it.
39:15 All right. So there's a bookmark folder that if you've never looked in it, this is a place where you can put, uh, bookmarks. If you don't know what a bookmark is, you can grab any sheet. So let's say that I want to turn this, um…
39:27 Let's grab one of these worksheets. I want to turn this worksheet or, or this worksheet into a bookmark. I c- I might say, "I don't really like that color. I want that to be red, and I want to save this as my template." You can go up here to, um, authenticate with 1Password, and go to, um, a window and bookmark. Click Create Bookmark, and you can save that.
39:48 Uh, and that bookmark becomes a template that Studio picks up automatically.
39:53 And by the same, uh, token, if you want to read in any of the templates that come with it, you can just open them right in Desktop, modify them, save them back, share them with your friends. So that templating is one of these undersung capabilities I had wanted for a really long time, and I'm super pumped, uh, that they m- made it in there. It turned out to be kind of a hard problem, actually, to try to find that mapping, but agents are pretty good if they can go, uh…
40:14 You know what it's like? It's like a Mad Lib. You know? It's like three adverbs, a noun, and a verb. It's like, all right, do you have a template that's got three, you know, three measures, a dimension that's geographic and a measure that's a date? And it's like, yep, these 10 templates. And then the agent's pretty good about going, um, "Okay, cool.
40:30 I think that's the one I want," and providing the fields, and then it's actually the agent that injects that and does the data mapping.
40:38 Does that make sense? I think it's super-duper cool.
40:43 Will Martin: Um, there's a couple questions on the side that I think, um-
40:49 Matthew Miller: All right. Can agents create graphics on the dashboard? Uh, yes, absolutely. Um, let's, um… We can do that. I can show you. But th- uh, this agent does have the ability not only to, uh, create images as part of those embedded assets, the viz or dashboard extensions, but it also can read images and documents that you share with it. So you can say like, "Hey, I just sketched out a dashboard.
41:13 It looks like X. You know, can you make something that looks similar to this?
41:16 Um, or make me a custom viz that looks like this." And it can read that, process it with like, you know, vision AI, and then implement. Good question.
41:25 Will Martin: Yeah, and then I, and then I'll take, Kirk, your question about if you're using Claude Code it's on 5.5 against the latest Claude MCP.
41:33 Um, so if people are looking at the, um, Tableau MCP, we actually just merged in all the changes that are powering the kind of like workbook authoring. Um, all those just got merged into the public Tableau GitHub, so you can go look at those. Um, so if you're issuing directly against Cloud, you're going to not necessarily have all those tools because they work locally, and they're also helper tools that are not necessarily in Cloud.
42:03 Um, but there's a lot of overlap there. Um, one thing we've not talked about here generally though is that this is all built on top of a, like, public REST API that Desktop can now expose to other, uh, things on your machine. Uh, so we like to call it puppet mode. But for even those who don't have, uh, Tableau Plus, there was a question about that earlier, um, you can hook up, uh, with the same Tableau MCP that is public.
42:36 You can just run that locally, um, and you can just communicate with Desktop locally. So I think Matthew is about to do a live demo of this, so basically he has Quad set up to kind of puppet- This Tableau Desktop instance or potentially multiple.
42:51 Um-
42:51 Matthew Miller: Yes. Fantastic.
42:53 Uh, go ahead.
42:54 Will Martin: And, and, and so I think this, this is a, one, a place where, again, some of the additions for Studio can help everyone regardless of license, which is awesome. I know on the engineering side we're excited for that, for everybody to use it. Um, one other thing in terms of just like overall effort and like what it can do, um, we have seen cases internally where the Studio agent today is geared towards trying to balance an interactive session where someone is gonna be working in the workbook.
43:31 Um, so there are a limit to the number of times we let it go do its thing. We aren't necessarily gonna just let it go for 20 minutes without any, uh, direction from the user, uh, because again, it's geared towards a little bit more conversational. Uh, we have seen people with the kind of Puppet mode do some honestly pretty incredible things. Uh, if they kind of…
43:52 And I think Matthew might be the foremost person in this, so basically let it run for hours, uh, and it can do some crazy things with just trial and error, as well as just like some of the skills we've built, of course. Um, and so there's a little bit of a different use case for, for both of them is what we're seeing internally.
44:11 Um, and I think we will continue to work to get that balance right. Um, but Kirk, as you said, of like what's the difference between the two? Um, there is a little bit of that, that we're seeing that like there's more optimizations, more skills for kind of interactive flows within Tableau Studio. But for Puppet mode, like some people, again, like earn some tokens, uh, but you can do some crazy things, uh, with Puppet mode.
44:36 Matthew Miller: Yeah. Um, so I, uh, shot from the hip a little. I did not test this thing just before this and my version of things had changed, but the good thing is it's an agent, so I told it, "Go find it in the right place." What I wanted to show you is that it- it's detected the presence of an instance of Tableau Studio. So it's found it and said, "Yep, I can see it's running." Um, it told me that I had an outdated version of a thing on my machine.
45:00 Uh, that's not Studio's fault, that's my bad.
45:02 But what it has done is it's found this instance and connected into it with what's called this external client API. So hopefully I've swapped that back out and can show you. There we go. Great. So, um, tell me what kind of things I can do to interact with Studio desktop, uh, in interactively through the, um, MCP, CLI, and external client API.
45:30 So this will go give us a list of like interesting stuff that a third party agent can do.
45:35 Now, you can use this entirely headlessly, and some of the data apps demos you've seen, somebody is in Claude, like on their phone, and they describe what they want, and it gets built using a bunch of this grounding and capability, and then pushed straight to server or cloud. You can totally do that. I think of that as kind of like Big Bang, and that's, that's great if you know exactly what you want or you can go look, make it look like this.
45:58 Uh, the, the Puppet mode like this is when you're, like it's kind of human and third party agent working together. Like I'm dragging and dropping stuff here. Let me scoot this over to this side of the screen so we can kind of see it side by side. Like we're working side by side and I'm making changes. Maybe the a- the Tableau Agent's done some things.
46:15 I've dragged and dropped some things, and I want the, my third party agent to do some stuff as well.
46:21 So here's a whole bunch of the capabilities that it's just described for me. I don't know if you can see that, but I'll zoom a little so you can. I get the list of workbook contents, and I can go to different sheets and navigate and format and edit the XML directly. That's the kind of, you know, do whatever you want. Making batch edits, getting summary data, which means that it can basically see what you see, but also see the data that you see.
46:43 So I've often asked it to go and answer a question, and it'll go and do that exactly the way I would, by building out a bunch of sheets with various combinations of things on rows and columns, not necessarily pretty, but sort of data exploration vizzes, and then read the data out of those and use that to drive exploration.
47:00 Um, pro tip, by the way, and I don't, 'cause I don't, but this is actually somewhat supported out of the box. I usually pair this with a ScreenVision MCP, um, that there's not one like built in there. You can get them. I'm not endorsing a particular one, but you can find some open source, so then it can like read my entire screen. But it, but there is the ability to get viz images from the external client API.
47:21 So a third party agent can see at least the viz that you're working with. I don't think, Will, that we got a full, like show me what all of desktop looks like right now support.
47:30 Will Martin: So, so we, we do, I believe, I think we added one. Um, one of the slight challenges there, I mean, not really a challenge, um, it does require, it like works through the accessibility framework, is how you can screenshot within Qt, the backing application. So it has to ask for some permissions. Um, but uh, I do think we added that. Um, I'll have to double check.
47:56 Matthew Miller: Cool.
47:57 All right, so Puppet mode, yeah, w- we call it Puppet mode, by the way, um, Michael, because, um, these are, you could think of the workspace extensions as plugins for Tableau. We kept the extensions naming. Lee and Will and I debated and argued and haggled, and, and Lee was right. I really think workspace extension is the right name for it.
48:16 But they are basically plugins, whereas when you connect in, into like a third party agent, they call those plugins. So you, you might go get like the Claude plugin for controlling Tableau Studio. So to keep plugin versus plugin clear, we called them, we called it Puppet mode, at least internally. So it's like interactive live. And t- this is my preferred way now, by the way, to use desktop.
48:40 Um, either the first party agent, but often mostly, uh, third party agents.
48:45 Um, this was by the way, partially inspired- Uh, I know this is going to be on YouTube forever.
48:51 Um, let's just say I, uh, accidentally oversaw, uh, uh, someone on a flight using Tableau, and they were alt tabbing between Tableau and Claude, and Tableau and Claude, and Tableau and Claude. And then, like, going back into Tableau and dragging some stuff in, like, downloading it to CSV, and putting it in Claude, and try- they were trying to solve some data problem.
49:08 And it was one of those things where I almost wanted to tap them on the shoulder and be like, "I literally know how to solve that.
49:13 Ah, we're fixing it." So partially this is inspired by that experience of, like, seeing somebody go, "I've got a coding agent over here," or, "a AI agent that I like. It's got this capability. I got Tableau, it's brilliant. I want the two, like, actually married and in real time." Will's done a bunch of… Will and the team have done a bunch of really cool things too about, like, the way it queues up the things that it's asking for so that you don't, you know, step on the toes of the agent or it step on your toes.
49:40 All right. Other questions.
49:41 Chris McClellan: I think the, I think the key thing there, right, is you've got, uh, right, ri- right up there on the bottom of the Claude window it says, "Tableau Desktop with MCP." So there's an MCP built into Tableau Desktop, so you can do that communication.
49:54 Matthew Miller: Yeah. Technically it's right alongside, but yeah. It's, um-
49:56 Chris McClellan: Mm-hmm
49:56 Matthew Miller: …
49:57 uh, it… and the, the MCP is, is, like, a companion along with the CLI. Uh, you can actually grab them. Uh, you can find them on your machine. They install in different places, whether it's Windows or Mac. Um, and you can use them. You also can call directly to this, this external client API. It'll be documented.
50:14 Uh, so if you want to build your own MCP, like some customers who are on this call have chosen to build their own MCP for Tableau, and that's fine. That's okay. It'll work just perfectly fine.
50:27 All right. Less than other questions. Let's go to some other stuff that the agent can do. So in addition to, like, conversational stuff you've seen, you have the ability to for skills, and skills are a, just a markdown file that tells the agent what to do. They also can additionally have a slash command. So these are the ones that come out of the box, and there's an awesome set.
50:49 Adam Miko is cranking those out, um, has done an amazing job. I think he had a goal of having 50 of them ready to ship by November 1st.
50:57 Will, you'll be able to tell me if he's on track. Last I saw though, it was like 40. I think he's got it.
51:02 Um, some really cool things.
51:03 Will Martin: I, I think he has more than that at this point.
51:05 Matthew Miller: I love it. That, that guy's brilliant. Um, so see, no surprise. Well, so I've got a folder here called, uh, tab agent skills, and these are mine, some that I built. So I'm gonna go into settings, and you can see the ones that are here out of the box. Uh, I'm gonna add that path. So I'm gonna grab my tab agent skills path and paste it, and it'll parse that, and it finds all these other skills that I had added.
51:30 Uh, things like understand what's going on, and replace data source connection, recommend next actions, et cetera. Um, I was at Dreamforce and showing this to someone, the, the, the big Salesforce conference, gosh, last month, and, uh, and they were like, "Do you think this could build me a Power BI or could we get a Power BI converter skill?" So I grabbed a bunch of Power BI documentation and a screenshot of a vis from, from, like, Google Images, and threw it in here, and it built a Power BI conversion skill.
51:57 I don't know how good it was. I didn't have a chance to test it, but, um, that's kind of cool. So, um, skills can be quite large. I think the context window that we have, Will, is a million tokens. Is that right? We don't… We're running at a million?
52:11 Will Martin: Um, I think so, but they just up- they've upgraded the model since you left. I can't remember what the, what the newest one is.
52:17 Matthew Miller: You know, I go away and I fi- and you finally get all the cool stuff.
52:21 Uh, so now that I've added those skills, uh, those will all be a, uh, here, uh, appear here, and the same, like, reload skill as well. So there is a skill builder skill, which is super meta, a skill creator skill that ships out of the box. So whatever it is that you want. Um, I was talking with at, at, uh, a- with Alex Mao at the, um, visionary day, and he was asking for a feature in Tableau.
52:45 He was like, "Hey, you know, there's this one thing I do often. Do you think we'd get a button?" So I was like, "I, I bet we can just have the agent build a skill for that," and it did, which is super, super cool.
52:54 So that's how you add additional skills. Um, I've already shown you attaching files, shown you how to revert a conversation in Workface. Uh, this is really, really cool. Um, props to the design team, by the way, that worked on this. Can I just shout out, just 'cause it's not business value, and yet it's so Tableau, these little icons that the design team put in here for different things, and the little, the little loading indicator.
53:15 I just think they're really, uh, just very Tableau. So you can rewind to a different part in the conversation and kind of fork the conversation from there. There's a planning mode. If you've used coding agents, plan mode is like, don't do anything. Draft the plan, and let's review it before that's done, and, uh, what was in- internally referred to as YOLO mode, um, auto-run mode, just like, um, again, Claude and others have.
53:39 Uh, I think that's about it there.
53:41 And of course, your like, you know, new chat and other things.
53:44 All the chats that you do have with it, by the way, are logged locally, so it's, um, I found it useful actually to mine those and say, "Hey, what are some skills I should have had that I didn't have that would help me get to my goal faster?" And it's amazing how an agent can go through and read those and build you some skills.
54:02 All right. Uh, let's see what's next. Any other questions?
54:06 Chris McClellan: There's, there's a lot more on the deck if you want to go back to that.
54:09 Matthew Miller: Sure.
54:10 Andy Holt: I think you kind of touched on this a little bit, um, Matthew, in terms of what you were saying earlier, but just I was kind of thinking what are the different use cases for Data Apps versus Tableau Studio in terms of how you guys have built and designed it? When is each the correct decision, if there's an easy split?
54:26 Matthew Miller: Oh, yeah. So I mean, a Data App is a Tableau dashboard. So I, I, I tried to answer this earlier. I don't know if I did it well, but a, a Data App is a Tableau dashboard.
54:37 That's it. So, but I will say, when you see the demos that, like, marketing has done, it looks like it's a totally different, altogether different thing. But, um, so if you see like, oh, I was in Claude, and I described a thing, and now I have a totally custom vibe coded experience that's running in Tableau Cloud or Server.
54:55 And that's a data app.
54:57 All it has done, I mean, all, it's pretty awesome, is it's gone and created a workbook like a shell, created a dashboard or two or three as a shell, and just populated them with, with a dashboard extension that's entirely custom, but that runs over the same data model. Go over a traditional Tableau data model, like that's what Will was saying, with VizQL data s- uh, service.
55:16 So when you then see that on server or cloud, it's a workbook. You can… Or you will be able to open it in Studio. I don't know if, Will, if that-
55:24 Lee Graber: So-
55:24 Matthew Miller: There was one… If that gap has been closed. Um, any you create though in Studio that has custom content embedded, you can see it in cloud and open it in cloud.
55:35 Lee Graber: So to, to Kirk's comment, 'cause Kirk's comment is, is correct. First off, it… Whether or not it's a dashboard extension or a viz extension is somewhat, somewhat irrelevant, but realistically, Kirk, it is more like a sheet extension.
55:49 Because it is likely not, you know, viz extensions are reusable things that care about pills and shells, and a pure data app does not have to care at all about pills and shells. Similarly, a dashboard extension is often some… Is often either tuned to whatever your data source is in that specific dashboard or something, whereas this, I've seen people build data apps that are, like, single page apps with multiple tabs and all s- like 15 different vizzes on them.
56:24 So it is, it is far closer to a sheet extension. It may in the future become a sheet extension, just because that makes it a little bit clearer for us that it's not a viz extension, and it's not a dashboard extension. Like, we don't want to show it in the dashboard objects pane to let you drag this thing out into a random other dashboard. So mentally, that's how I think of it.
56:52 Uh, technically, that's how it might become.
56:56 I don't know if that was helpful for you, Kirk.
57:00 Chris McClellan: I think any-
57:00 Matthew Miller: So-
57:00 Chris McClellan: … information like that's helpful. 'Cause it's easy.
57:04 Matthew Miller: Yeah. Data apps are not a different thing than Studio. Studio is an IDE for creating any Tableau asset, including what you could call data apps.
57:12 You can also create what we are calling data apps entirely outside of Studio with a, a text user interface or any other agent.
57:26 Good question.
57:26 Lee Graber: Thank you.
57:27 Matthew Miller: Uh, a- Andy, did that, did that cover that though? Is that clear?
57:30 That we-
57:30 Andy Holt: Yeah.
57:30 Matthew Miller: I know we, we-
57:31 Andy Holt: Yeah. I, I think the actual, when I kind of told Chris, it's obviously kind of lost a little. The, the question was versus Tableau Agent in Studio. So just for, um, the kind of clarity. But yeah, I think you, you guys-
57:41 Matthew Miller: Oh
57:42 Andy Holt: … definitely kind of-
57:42 Matthew Miller: Okay. Yeah
57:43 Andy Holt: … covered it. Yeah.
57:45 Matthew Miller: Great. Um, I, I know that some of this is, uh, just a ton of new concepts, and some of this also marketing, you know, talking about a new category of thing, a data app, when in fact we've been building data apps for years. What they're really saying is now it can be entirely, you know, custom-
58:01 Lee Graber: Yeah
58:01 Matthew Miller: … and part of the workbook.
58:03 All right.
58:03 Lee Graber: Well, part of the problem-
58:04 Matthew Miller: Next question.
58:05 Lee Graber: Yeah. Part of the problem is we've done probably five different not insignificant things between packaging content, like static content in the workbook, between workspace extensions, between data apps, which are ex- essentially sheet extensions, and Studio itself with the new agent that we're sh- Like, we've done a lot of things. We talk about them all together.
58:31 Uh, and they all have value kind of on their own, and they build off of each other, but in talking about them all together, which, I mean, it's a big release, it does get a little confusing.
58:43 Matthew Miller: You wanna go to the next one, Chris?
58:45 Chris McClellan: Could do.
58:48 So e- even an easy question. Maybe what licensing is needed. So we do…
58:53 And, uh, this sort of came from something the other day with, um, uh, Tableau.
58:59 I forget what the other one, new one, new one was. But it was just like, "Oh, it's on cloud." And it's like, no, it was Cloud Plus, but not Cloud.
59:05 Um, so where can we get this from?
59:08 Matthew Miller: So Studio itself is just like an adjust desktop, but, like, massive, like, overhaul, right? So, uh, where will people get Studio? If you use Desktop today, it's gonna be rebranded Studio, and it'll be, um… Well, there was talk about actually being able to finally not even have a separate Studio public or Desktop public, uh, 'cause the delta between that and Desktop Free is very minimal.
59:32 So, but you'd have your Studio Free, Studio Standard, Studio Enterprise, Studio Plus.
59:38 Uh, and that's based on whether you have, like, which edition of Server or Cloud.
59:43 Uh, the… U- usually though when people say, "Where do I get this? Do I get it in Cloud, Server, or Plus?" Et cetera, they're referring to the new Tableau Agent. And last I was involved in this, the Agent was going to be in Server Plus and Cloud Plus.
59:57 The workspace extensions capability is available to everyone. The Puppet mode, um, external client API, all that is possible for any edition, but the specifically the new Tableau Agent because it's, you know, a ton of work, and, and then Tableau is, uh, covering the cost of the tokens.
1:00:16 Chris McClellan: Mm-hmm.
1:00:18 Matthew Miller: Uh, Studio can publish to anything.
1:00:20 But the new– To use the new Agent to author things, you'd need Cloud Plus or Server Plus.
1:00:27 Um, the… So I s- Kirk, your question is, "So Studio needs a Creator Plus to publish a cloud?" No. Studio is Desktop, it can publish anywhere it can publish today as long as you've got a, you know, a Creator license.
1:00:38 Um, you asked, "If I use the MCP through any client, do I need to use OAuth or a PAT via Creator Plus?" Um, if you're using the local MCP to talk to Studio, uh, there's no license necessary to do that. That's just a, a token that you, you read out of the user's, like, secure, uh, local storage.
1:01:01 So the authentication is not a PAT, the, 'cause it's a lo- it's all local. Like, the… When you're using a… I'm, I'm talking here about a local agent that's in Puppet Mode working with Studio.
1:01:10 That's just local.
1:01:13 There's no, um, like, sign-in or PAT necessary. Oh, as for publish, um, at… Well, so publishing from Studio is just publishing from desktop. The exact same product, same code. So if you could publish before to Studio, to Server or Cloud, you can publish from Studio. Same code, same capability, same authentication, all the same stuff.
1:01:34 Nothing new.
1:01:36 Will Martin: Um, there's a question on…
1:01:40 Oh, yeah, why don't we finish off the talk about publishing, and then we can talk about Tableau Knowledge after?
1:01:44 Matthew Miller: Uh, now, there, there is the question of which of those places can serve those embedded extensions, meaning can they serve data apps?
1:01:53 Uh, all of the platform supports extensions.
1:01:57 Um, however, I believe that Server's the first place that's gonna support embedded extensions, and then Cloud very shortly thereafter. And public, I'm not sure. Will, do you know the latest on that?
1:02:08 Will Martin: Yeah. Lee, I was g- actually gonna ask. I know that there's been kinda goings back and forth. Um, there's actually, I think for some of the early beta sites on 10.8x that might have been enabled already for data apps. Um, but I don't…
1:02:25 You're closer to that space in terms of exactly where and how that's gonna be.
1:02:30 Lee Graber: When, when it'll be available for, like, online sites?
1:02:34 Will Martin: When, but also the… Yeah, they're in 10.8x, but then also the, do you remember where the licensing, uh, discussion for data app hosting went?
1:02:43 Lee Graber: Data app hosting is not behind any license.
1:02:47 Will Martin: Okay.
1:02:48 Matthew Miller: Right.
1:02:49 Um, and public, I'm not sure.
1:02:51 Kirk Munroe: Can I, can I clarify my question then?
1:02:53 Matthew Miller: Sure.
1:02:54 Kirk Munroe: So if I use Studio the day it comes out and I wanna use the agent inside it, I need to be a creator and I need a Plus license to get access to the agent. I need a Tableau Plus-
1:03:05 Matthew Miller: Correct. You've always needed a creator. Yeah, you've always needed a creator to use it.
1:03:07 Kirk Munroe: Yeah, I've just needed a creator. That's new.
1:03:08 Matthew Miller: Now you need a creator.
1:03:09 Kirk Munroe: But the agent, or I need to be… But I guess maybe Lee answered. I don't know, maybe it's hasn't been figured out yet that ways. But imagine I go into Cloud instead and say-… I'm gonna skip, I'm not gonna use Puppet Mode. I'm gonna code directly against the MCP, which I can do like I did today on 10.8x.
1:03:27 I asked it to build it three different ways. It did it three different ways.
1:03:31 And I can publish then, 'cause I can get the MCP to publish for me. What does it check aga- And I'm all opt-in, so I didn't-
1:03:39 Matthew Miller: Same. I don't-
1:03:40 Kirk Munroe: It wasn't asking to code.
1:03:41 Matthew Miller: Yeah. As of right now, no additional-
1:03:42 Kirk Munroe: It doesn't appear… I definitely don't need Plus to do- I definitely don't need a Tableau Plus license to do it.
1:03:46 Matthew Miller: Correct, because you're, you're bringing the brain, you're bringing the tokens, right? And in fact, from Tableau Server or Cloud's perspective, they don't know how you authored the content, right? They don't know. You, you could have hand-edited the TWB in Notepad if you liked, right? They don't… The, the, the thing that I love about the approach that the team has taken here is all the cool agent stuff is upstream, right?
1:04:09 So the Server and Cloud don't actually really know and, and don't care.
1:04:12 Kirk Munroe: Well, I don't know if you saw, but Benioff announced a couple of days ago that anyone who authors via an agent to the Salesforce platform is gonna get charged for doing it that way.
1:04:20 Matthew Miller: Well, I can't, I can't speak to Salesforce's licensing.
1:04:24 Kirk Munroe: Yeah.
1:04:24 Matthew Miller: But I can tell you my opinion of it.
1:04:27 Will Martin: Well, maybe it doesn't hit-
1:04:28 Kirk Munroe: I'm saying Tableau does.
1:04:29 Will Martin: It is.
1:04:29 Kirk Munroe: Anyway, we can move on. But it affects this question. That's the only reason I asked.
1:04:33 Will Martin: S- so, so far, yeah, there's no… It's, what's gated behind Plus really is, like, the actual end product agent. Right now there's no, like, gating of the Puppet Modes. So you said use an external MCP to publish, like, great, continue doing that. But you can also use desktop and Studio and iterate on building and publish from Studio or use an MCP to publish, and that won't be gated by any means.
1:05:01 Um-
1:05:03 Lee Graber: Dan.
1:05:03 Matthew Miller: Yeah.
1:05:03 Will Martin: Go ahead, Lee.
1:05:04 Lee Graber: There are some features that we are working on that will be a, a post GA release for data apps that will likely be behind Plus.
1:05:15 But the basic stuff that we've been talking about up till now, uh, is not. Uh, again, you can, you could have hand-coded the thing. We have no idea if you actually used an agent.
1:05:27 Matthew Miller: Yep.
1:05:28 Um-
1:05:28 Will Martin: Um.
1:05:29 Matthew Miller: Let's, uh, shall we move on to the next question? We got a few minutes.
1:05:32 Will Martin: Yeah. Fiona had a question about Tableau Knowledge. Um-
1:05:34 Matthew Miller: Oh, yes. Fi. Oh, ooh, ooh, ooh, this is one of my favorite things.
1:05:39 Will Martin: Matt, go ahead.
1:05:40 Matthew Miller: So, uh, one of the things that this does i- that we haven't really trumpeted, and when I say we, I mean they, is that this is an MCP client as well.
1:05:50 So you can configure this agent to call other MCPs. Like, have it pull from your JIRA. So you literally could be in Tableau Studio and be like, "Ugh, what is the next ticket from the business?" You know, "What else do they need now? Okay, add this field." Like, you know, the real work of analysis that often has to happen. It's not fun or sexy, but just knocking out the tickets.
1:06:13 Uh, you could integrate JIRA and it'd be like, "Update JIRA. It's done." Same thing, like you could hook into Snowflake and be like, "What tables could possibly answer this question?" So it's actually a full MCP client. So I actually had Dreamforce had it set up to where it was talking to Tableau Knowledge through MCP. Now, the Tableau Knowledge is available, I believe, already in the Tableau, like, MCP server.
1:06:35 Um, so if it's on the same site that you're signed into, I think you just get that for free, right, Will?
1:06:41 Will Martin: Yeah. So I-
1:06:42 Lee Graber: Yeah
1:06:42 Will Martin: … I would say, like we're, we're pretty early in the integration stages here. Um, so today if you're to use the MCP, there's some combination of, um, the underlying metadata API as well as TK to try to kind of, like, figure out the right thing and make sure you have all the context. But as TK is getting off the ground and we're getting more and more in there, um, I think we'll probably expand that.
1:07:05 Um, like Matthew said, like- It's an MCP tool because we built this on the MCP.
1:07:10 Uh, we kind of get it for mostly free, but there's like… I would say there's get it for free and then deeply integrate, and we're still working, I think, through that, like, deep integration as people start onboarding onto TK more and we start to see, um, kind of just how deep and how much benefit we can get there.
1:07:28 Matthew Miller: There's a time-honored tradition of Tableau employees, you know, sharing a little more documentation about the inner workings than they probably should. Um, and I don't even work there anymore, so I can, but it's not too hard to figure out how to configure it for MCPs. If you just look at the standard MCP, um, JSON configuration file that Claude uses, and you have to put it in a folder.
1:07:50 So like the s- where I added my skills folder, um, the base one doesn't do it, but you ca- create your own skills folder and put an MCP JSON in there. And actually, to its credit, it says that in the screen. If you go to the Tableau Agent and hit settings, you'll see it. So you can register any MCP server, um-
1:08:05 Will Martin: This, this is, this is one of those things may have changed or may change from the, uh people still working, uh, at Tableau on this, but I know Matthew's had fun pushing this.
1:08:15 Matthew Miller: Don't break it. It's awesome. Um, I always wanted the ability to be like, "Can you just go update and, like, send an email to the person?" And be like, "I'm done." It would've made my consulting so much easier, except I was billing by the hour. All right, next question.
1:08:27 Chris McClellan: Uh, next question I think is Kirk anyway.
1:08:31 Matthew Miller: In a data apps or headless BI world, how do you see Tableau being able to price going forward?
1:08:37 Uh, well, I will, I will actually…
1:08:40 I can speak totally freely, can't I?
1:08:43 Um, I, I, I feel like anytime someone, when I was a Tableau executive, and a customer would be like, "Tableau's too expensive," I would say, "Is it now?" And I would draw the same little diagram, which is, like, a simple scatter plot, and I'd put price, value on the two axes, and I'd draw a 45-degree angle, an arrow going up.
1:09:05 It goes like this. Like, um, the, the cost and the, like, the value you accrue to run the product should pretty much scale linearly.
1:09:15 That's how we think about it. So at least I think that's how one should think about it. And I said to this customer, "You would pay $10,000 a user a month for Tableau." And their eyes got really big, like, "Don't tell me that's what you're gonna do." I said, "If, if it made you $50,000 per user per month in value." So, uh, I, I think that's the right way to do it.
1:09:37 It is… I, I got grumpy anytime somebody was like, "Well, we need to sell more of," insert thing. I'm like, "Well, we do, probably. But what do customers actually need, and what's valuable to them?" And I would note, I'll just say as well, like, the, the model, uh, the model's well been broken because we're in this world where agents can do a lot of things, and how do you price per agent?
1:09:57 And Salesforce is trying to figure this out, and everybody's trying to figure this out, and I need to figure this out in my new job. But, um, you know, f- for what it's worth, the, the, coming back to the value of Tableau Studio, it is the world's most widely adopted and capable analytical IDE. So as long as you're getting a ton of value out of the assets that it creates for others, uh, I would tend to think that the, the price of Studio should come down, and then I would monetize the value you capture.
1:10:25 This is purely my opinion. I would monetize the value you capture later. 'Cause the value isn't, I don't think it's in the offering. It's in the consumption and the actions that come with it. But, you know, there's other companies that see it the other way, and they, they charge a ton more than Tableau did for the offering, and then everything else is free.
1:10:42 Kirk Munroe: To clarify that, since I asked the question, I didn't mean how much money could Tableau charge. I meant the pricing model Tableau could use, and you just used the word consumption. So imagine pushing data apps headless, so not Studio for a second.
1:10:57 I publish workbooks, but I still have all the governance and everything from Tableau Cloud or Server. I'm not debating that. It just, it feels like a very consumption conversation, not a per user conversation. Is all I mean.
1:11:11 Matthew Miller: Yeah.
1:11:11 Kirk Munroe: So I don't mean a dollar fi- I don't mean a dollar figure. I mean a pricing model question.
1:11:16 Matthew Miller: I know that there are some really, really smart people who I love and respect who have this challenge in figuring out how to do it in a complex world where things are changing.
1:11:24 Uh, and so I, I wish them great luck in figuring that out, and I'm sure we'll all give them feedback if we don't.
1:11:31 All right, next question.
1:11:34 Chris McClellan: Easy. Next question is, uh, what LLM model does it use? I think we've sort of covered it.
1:11:38 Matthew Miller: We did that. Currently, I mean, out of the box, it's Claude Sonnet 5.5 for now.
1:11:42 Chris McClellan: Mm-hmm.
1:11:43 Matthew Miller: And by LLM engine, like, you gotta separate the model from the harness, right? Um, hey, while I'm leaking things that cause my colleagues to cringe, it is possible, technically unsupported currently, at least in the alpha or beta, to use this with local models.
1:11:59 Um, and I've done it. It's super cool.
1:12:01 My Mac Studio arrives, like, in four days. I can't wait to try this. I'm sure it'll, you know, run dog slow, but still, it's kinda cool you can do that.
1:12:11 Um, Fi said, "Consumption kills creativity." I couldn't agree more. Andy Cotgreave has dropped off to probably go play board games, but, uh, I love that he said, like, the cost of curiosity should come down.
1:12:23 And so I love that we s- that we, and by we, I mean they, have settled on an unmetered approach with Studio, where you can just explore as fast as you want and at the same cost. At least for human licensing, that makes a ton of sense to me.
1:12:36 I didn't, I never felt comfortable with consumption for offering, because offering is about exploration.
1:12:43 Uh um, just wait until my NDA expires, Michael.
1:12:48 Okay, next.
1:12:50 Chris McClellan: Okay, next question is, uh, another Kirk question. Do you think people will pay for viewers of these HTML dashboards?
1:12:57 Matthew Miller: Sure. I don't think end users care what things are built in. They don't care what things are built in on their… Today, they don't even know. End users have no idea. That's why I don't like, and I found it confusing, the marketing term data apps. Like, I like the term, but I don't like the way it was like, "Data apps are only the vibe coded things.
1:13:12 Those mean custom HTML-" I've not met a single actual user of Tableau who actually understood the difference or cared.
1:13:20 Like, it's just about the value they accrue from being able to see, understand, and act on the right things, the right place at the right time.
1:13:26 So, um, I, I, I think people will just, you know, if they, if they fi- if they're comfortable saying, "I pay f- per f- per viewer 'cause that's how I accrue value from my usage of Tableau," I don't think they care where it's offered in. What I love now is, like, this is true self-service, you know? Um, like, you can, you can do really horrifically bad data viz things now.
1:13:48 But then again, we've always let you do some really weird data viz things if you really were committed. So people have unlimited flexibility now. I think that's fantastic.
1:13:57 Kind of the, it's the, maybe the rise of the, um, the, like, self-service business user. Ooh, while I'm sharing things that we're not supposed to know, um, it is largely technically possible for a workspace extension to run in viewer mode. And, and apparently, from my investigation of it, maybe the architects will correct me, theoretically possible that that workspace extension could mutate the dashboard, like, just for the sake of that session.
1:14:24 So imagine the person viewing a dashboard goes, "This is great, but I don't wanna see a bar chart, I wanna see a line chart." People have asked for that forever. That's theoretically possible. So, uh, there's some really cool things that we could do to make the viewing experience way more capable, not just dashboard Q&A, but, like, like, manipulate this thing for me.
1:14:44 Um, and I believe, Will, I thought that was possible in, in web, even when not in web offering. But-
1:14:49 Will Martin: I-
1:14:52 It's a, it's a slippery slope. Uh, it, it should be… so, right, like, so, so there's…
1:14:58 Hey, we're the engineers in the room, so, like, we're not gonna answer the, the pricing/packaging ones thankfully. But the, uh, for these sorts of things, um, there's the, like, should they be able, how, like, what degree should, uh, viewers generally have?
1:15:15 Uh, I think you would agree that, like, if someone has really old school embedded username and password in the XML, they should not be able to, like, see and edit that, right? So there are, like, permission level things of, like, if you don't have filter permissions, you probably shouldn't be able to see and edit filters.
1:15:30 Uh, changing, like, the, the chart type, you know, like, obviously that's not going to necessarily change that. Um, so I think there, technically it's, it's possible. Uh, but there are constraints from permissions, and I'm sure there are business constraints that, um, I don't think about that often. Uh, but I'd say permissions are the big one.
1:15:52 Matthew Miller: Yeah. Well, I'm just completely, you know, in YOLO mode here myself. Um, I have lobbied for killing off the viewer license and just giving everyone explorers. If the user already had viewer, like, you, you kind of lock their permissions by default to viewer, but they could, the admin could upgrade them to full explorer. 'Cause I think the expectation now from users is these dashboard apps are, like, not static.
1:16:15 Hyper-personalization's a thing. And so, you know, uh, I hate to say I told you so, but I think web offering, I never liked web offering because it was intended to be a lighter weight offering for people who were less technical and weren't building big data sources, but it just sort of brought the, let's say, baggage of the full offering experience without bringing the brilliance.
1:16:36 And so I would love to see web offering dec- usage decline more than it has. And the, the agent in viewer mode is where a user who goes, "Ugh, I just need to see an extra 12 months of data," or, "I just need to, like, flip the bar chart to the line chart or make it a different color of blue for this client," um, that they don't have to go put in a JIRA ticket and run it to somebody who's got Studio.
1:16:59 Um, all right, uh, we should move on. Kirk, you asked, "I didn't expect you to care now that you're gone." Oh, come on.
1:17:05 I don't know if Tim Cady's still here, but I'm still tattooed. Let's go. Next question.
1:17:11 Chris McClellan: Uh, next question is, is it, is it-
1:17:12 Kirk Munroe: I said Domo, I said Domo had the feature and they're gone.
1:17:15 Matthew Miller: What's that now?
1:17:16 Kirk Munroe: The product. No. Whatever. In Domo, viewer, the equivalent of viewers used to be able to change their chart type, but that was so successful that the company doesn't exist anymore. I'm being sarcastic.
1:17:28 Matthew Miller: Outstanding. Uh, Fi said, "Can someone lobby, lobby for cheaper licensing now that everyone can vibe code anywhere?" Um, I will say this is a little on the less, you know, positive and peppy mode. At one point, I said the following in a meeting, which is maybe why I wasn't always popular. Like, listen, there are cases where you get, like, 10 to 100 times more capability for 10 to 100 times less cost in some of these c- certain types of things that people wanna do.
1:17:54 Now Tableau, again, 3,700-page manual. There's no broader, more capable analytical IDE. I love the product. I've used it forever, and it's great. But for certain use cases that are pretty common, you know, the agents made stuff just super cheap, and it's awfully hard to justify a more expensive license.
1:18:11 You know, it's, uh, one of my favorite customer interactions in my pre-Tableau days when I was in the Microsoft world, was a, uh, like, Air Force or Army guy saying, uh, "It's like y'all trying to sell me," this is to Microsoft, "It's like y'all trying to sell me the whole train when all, all I need is one damn car." Um, it's like we, we gotta make sure we're aligning again, like, cost and value.
1:18:31 So, yes, I'm with you. There are places where, you know, you could imagine, uh, different types of licenses. Maybe, you know, I think, I think Mark Benioff, as usual, is probably onto something with, like, headless-only licensing might be a thing.
1:18:44 Um, I don't know. We'll see. That world's changing fast. "Do you think Tableau will adopt the extra agent interface consumption pricing?" Oh, hey, that's exactly what we were talking about.
1:18:53 Chris McClellan: Yeah.
1:18:53 Matthew Miller: Um, I can't speak to what Tableau's gonna do pricing-wise. Uh, I, I think that, um, I've never liked charging for APIs that a person could use through a UI. Like, who cares whether they're getting… It's kind of like, do I care if you get value out of Tableau from a subscription or from Pulse? Or from drag and drop. Like, no, you're still getting value out of the product.
1:19:18 You're still the same person. If we're doing user licensing, that's just one user.
1:19:22 I wouldn't wanna charge you extra 'cause you're bringing your own agent and UI. Um, but, like, dedicated agent-only pricing could make a lot of sense if it were, like, at a lower price because the cost to serve is lower. It's about the kinda cost and value for, for the business as well. But that's my opinion.
1:19:41 All right, we probably get one more question in.
1:19:42 Chris McClellan: Also-
1:19:42 Matthew Miller: What do you think, Chris?
1:19:43 Chris McClellan: Yeah, there's, there's just a few more. So what is the general outlook for dashboards in the future, i.e. a big shift of vibe coding or still manually building things?
1:19:52 Matthew Miller: Uh, neither. I think that the data apps aren't going anywhere. You know, dashboards are dead has been said by so many companies that have come and gone because apps aren't dead. Because at least now, it's humans interacting with stuff.
1:20:08 So a- dashboards and apps aren't going anywhere 'cause humans still need to look at things, and because, like, the science behind Tableau still, still true, still real. Like, seeing and understanding things is way more powerful. I get so, like, tired reading text UIs and trying to parse things.
1:20:24 Chris McClellan: Mm-hmm.
1:20:25 Matthew Miller: Um, so I don't think that's going away. Um, I th- and vibe coding, neither vibe coding nor, like, click, click, click, click, click, click, click. Click, click, click, click, click, click, click. Neither of those are the answer. I think that what people want is freedom, flexibility, and choice.
1:20:40 Shout out Francois who, who hammered that into me. Like, freedom, flexibility, and choice. I don't think they want vibe coding. I don't think they want manual clicking. What they want is to be able to see and understand the world around them, and then share that with others, and make sure they can trust it.
1:20:55 Uh, like, uh, maybe I can close with this. I was on a panel, uh, years ago, and I was asked about, like, Tableau customers and adoption of AI, and it was just asked in a, like, stuffy way, and I was sitting with a bunch of stuffy executives on stage. And I just couldn't, I couldn't, like, do the, you know, the thing. And I said, "Look, maybe it's just me or maybe it's just the clients I talk to or customers I talk to, but I think most Tableau customers just want a bar chart they can believe in." So I think trust and trusted data is far more important.
1:21:22 I don't think people love the clicking.
1:21:24 I don't think they love vibe coding. I think they wanna be able to see, understand, and act on data.
1:21:29 So, uh, the paradigm in the future will probably shift, you know, to something that is metadata-driven, 'cause that's way better than just bundles of custom code floating around on tons of servers everywhere.
1:21:40 Uh, but it will have the flexibility level that people love of vibe coding.
1:21:45 Chris McClellan: Yep.
1:21:47 And I think we're really close to the end.
1:21:51 Matthew Miller: Go ahead. I'm, I'm good.
1:21:52 Chris McClellan: It was the end. There you go. I thought that was fine.
1:21:54 Matthew Miller: All right. Wonderful. Couldn't have been better timed.
1:21:56 Chris McClellan: Okay.
1:21:57 So just to wrap up on my side, there might be some other questions in the chat as well. So there's Matthew's contact details if you don't know how to contact him. LinkedIn, X, or Tableau Public.
1:22:08 Um, but, uh, on the 17th of November, so in two weeks' time from now we have David returning. We might actually squeeze in another TUG between now and then. I'm not sure. But this is the actual next official one.
1:22:23 A two-week break. That's pretty crazy. Um, so David's coming back for the second in his series of AI, MCP, all that sort of stuff. Um, again, different time slot. It's one meeting. Just, just depends on where you are in the world. But register for that one as well.
1:22:39 And this recording, we might have to edit a few things out.
1:22:43 Every other thing that, that we do and a whole heap of other TUGs are on YouTube at Team DataFam, or listen to the MP3 podcast on Spotify or Apple, or email me if you've got any questions, if you want to present, et cetera.
1:22:57 And, um, thank you Matthew and friends for that. The recording will be online as soon as possible. And, um, thanks for your time today, guys, and all that awesome information that we've got.
1:23:08 Matthew Miller: So great to see you all and spend some time together.
1:23:11 Don't be a stranger.
Shorts for this TUG
- Tableau Studio is Tableau Desktop, rebranded 3:03
- No feature left behind in Tableau Studio 4:35
- Why Tableau Studio is built for people who build 8:01
- What is a data app, really? 9:48
- Custom viz extensions with no web server needed 13:03
- Why metadata beats custom code in Tableau 14:02
- A click is worth a thousand words 16:47
- The new Tableau agent can ship three times a day 23:14
- Workspace extensions are plugins for Tableau 25:22
- Missing a Tableau feature? Build it yourself 29:46
- The mantra behind the new Tableau agent 34:46
- How Tableau Studio picks viz templates like Mad Libs 40:02
- Why Tableau and Claude should work side by side 48:49
- Building a Power BI converter skill in Tableau 51:36
- Tableau Studio's agent is an MCP client too 1:05:41
- Is Tableau too expensive? Is it now? 1:08:48
- Why Tableau Studio's AI is unmetered 1:12:15
- Selling the whole train when you need one car 1:17:44
- Dashboards aren't dead, and here's why 1:19:57
- Most customers want a bar chart they can believe in 1:20:57