851: The Future of VS Code and Copilot

Wes and Scott talk with Cassidy Williams and Harald Kirschner about exciting new features in VS Code and GitHub Copilot, including custom instructions, UI/UX improvements, and the future of AI and Copilot within different editors. Show Notes 00:00 Welcome to Syntax! 00:32 Cassidy’s keynote at GitHub Universe 03:23 New Copilot features 04:55 Use cases for prompt engineering 09:20 UI and UX enhancements 19:18 Copilot Extensions 20:38 Brought to you by Sentry.io 21:26 Multi-line suggestions? 27:00 How do you develop new ideas in this space? GitHub Next 35:42 Copilot in Xcode GitHub Copilot code completion in Xcode is now available in public preview 39:16 VS Code experimental features @code Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Wes Bos?

  Welcome to Syntax. Here we are live today at, not live, this is not live. We're recording at GitHub Universe and we have two amazing guests on today. We just did an episode on some of the new site and stuff to VS Code. And we've got Cassidy Williams and Harold Kirchner on today to answer some of our questions and talk about it. So, welcome. Thanks so much for coming on.

• 0:23Speaker 01

  Thanks for having us live. We're live in person.

• 0:26Wes Bos?

  Live in person. This is really cool.

• 0:28Scott Tolinski?

  Live to tape, yeah.

• 0:29Wes Bos?

  I've never really done this before, which is pretty nifty. You did the keynote, which was wild. I saw you go up there and I was like, oh, man.

• 0:37Speaker 01

  I know her.

• 0:38Wes Bos?

  Yeah, I know her. And like, were you been nervous? Like, I was nervous.

• 0:42Speaker 01

  I was, I was hiding my panic.

• 0:44Wes Bos?

  Oh, my.

• 0:46Speaker 01

  I was so worried the demo wouldn't work.

• 0:48Wes Bos?

  Yeah.

• 0:48Speaker 01

  Uh, just, because it was all, it was all a real live demo and stuff. Where like, I had a backup video just in case things didn't work and I was just gonna say, we're moving to it. And the fact that it all worked, I was so happy. It was because AI is non-deterministic.

• 1:02Wes Bos?

  Yeah, yeah.

• 1:03Speaker 01

  And as I did so many rehearsals and run-throughs, the results were different every single time. And, and so, I, like, I put in as many fail safes as I could and the team was like, well, what if you rearrange this? Change the prompt this way and stuff? And like, it came together at the end and I'm so happy that it went smoothly. Yeah.

• 1:22Wes Bos?

  And Harold told me that there was somebody backstage doing the same thing in case they needed to cut over to it?

• 1:27Speaker 01

  Yeah, they were like mimicking me on their laptop, so if we had to switch to a different laptop, they could, yeah.

• 1:33Scott Tolinski?

  That's so smart, like a triple backup system.

• 1:35Speaker 01

  Yeah, so we had the video, we had the second laptop, we had me, and then a hope and a prayer. And it worked out.

• 1:42Scott Tolinski?

  Was that the, the most, like, intensity you felt before going on stage before? Because you've done a lot of stuff, yeah.

• 1:49Speaker 01

  Yeah, I honestly, there wasn't a lot of intensity before. It was right when I got out and I was like, hmm, there are a lot of people watching.

• 1:55Wes Bos?

  Yeah.

• 1:56Speaker 01

  I really hope the demo does what I planned for it to do. Because like, it's not like the Copilot chat or anything ever failed. It would just not always return the exact same thing.

• 2:05Wes Bos?

  Yeah.

• 2:06Speaker 01

  And when I wanted to explain like really specific concepts, I was like, I really hope. It lets me explain these very specific concepts and it worked out. I was very happy.

• 2:14Speaker 03

  But you had really good recovery in the rehearsal before, right?

• 2:17Speaker 01

  Thank you.

• 2:18Scott Tolinski?

  Okay.

• 2:18Speaker 03

  But if you don't need that, even better.

• 2:20Speaker 01

  Even better, yeah.

• 2:22Scott Tolinski?

  I think that lends a lot to the authenticity of the demo. So if like people don't know, like while they're watching if they're pre-canned or whatever, I know because even like Google gets sometimes criticized for that.

• 2:32Wes Bos?

  Oh, cool AI demo. You scripted that, you know, but you were actually doing it, right?

• 2:37Speaker 01

  Yeah, no, the only thing that I had like macros for was just I had a really long prompt at one point and I used it to type a little faster.

• 2:44Scott Tolinski?

  I want to hit that on stage.

• 2:45Speaker 01

  Yeah, it was it was long. But besides that, yeah, no, it was all real.

• 2:49Speaker 03

  Yeah, I had people who do AI demos next to me asking like, is that is that real? Is that recorded? Because like, that's that's a big demo. It's like, yeah, I I saw it. Yes, it was. It's real. But so but even people like who do AI demos, like that's that's that's the next level of like, that's that we ship these products in a way that that this came together on stage. It wasn't like, it just made a graph, right? It wrote new code, it created new files and it just it all worked. So it was magical.

• 3:18Speaker 01

  It was a lot of features to compress in one demo for sure.

• 3:22Wes Bos?

  Yeah, no kidding. So there was like, let's rattle through those features real quickly. Like, what were what were the ones that we announced today?

• 3:30Speaker 01

  The one that I think is like the biggest coolest one is probably multi-file editing.

• 3:34Wes Bos?

  Yeah.

• 3:34Speaker 01

  And so the fact that, yeah, it can it can work through multiple files at once is really awesome, creating new ones and editing existing ones. And the one that I think is the coolest is the Copilot custom instructions.

• 3:46Scott Tolinski?

  Yes.

• 3:46Speaker 01

  Being able to like say exactly what you want your code to do and then being able to pick your model for that.

• 3:52Wes Bos?

  Yeah.

• 3:52Speaker 01

  Is really nice.

• 3:54Wes Bos?

  So that's in the, what was that file called? We have it here.

• 3:57Speaker 01

  The Copilot Instructions.

• 3:59Scott Tolinski?

  It's just a straight up text file, right?

• 4:01Speaker 01

  Yeah, it's a markdown file. Yeah, so you can you can even like format it at headings for like importance and stuff.

• 4:06Speaker 03

  Yeah, and we thought about it, we thought like it should be YAML and we have there's some more things coming like there's like it doesn't doesn't work nice in large monorepos, right? You want to have a front and back and there's there's more stuff, but this is like the easiest solution to just. Unlock people and it works across all different kind of repos and it's very free form.

• 4:25Speaker 01

  Yeah, and as I've like learned more about the prompt engineering side of things, you could say like under this heading, general guidelines and like saying like things you definitely need to know, like you can be really specific with it and get really good results.

• 4:37Wes Bos?

  You know, the one I want to do is when you write the word color in a comment, use the correct spelling, which is a color with a U. You know, and or write the my comments as if it were a Canadian.

• 4:51Speaker 01

  It'll just say A at the end and be like, you're like a moose.

• 4:53Wes Bos?

  But like, what, what are some other use cases that people use that sort of prompting for?

• 5:00Speaker 01

  Yeah, so, so the case that I talked about in the keynote was basically adding a feature flag with launch darkly at the beginning of every component. And that was just, that was a way to show like, we have the co-pilot extensions available, but then it's also a thing that can be added to every component. I think probably the broadest use case I've seen is like specific code styles. Or if you want like the autocomplete to follow a certain linting rule or something that that isn't automatic. And then like adding doc strings and stuff.

• 5:28Wes Bos?

  Oh, yeah.

• 5:29Speaker 01

  I feel like that's a really big one.

• 5:30Speaker 03

  Yeah, I think the big one. So we did talk to a ton of customers. It comes up left and right, like, oh, GitHub doesn't understand my code base, where it's really around like, if you look at this code that you give it, you wouldn't know that like that you use the other dependency, right? If you want by the graph, like how to should now use the three versus some other library that you might already use. And we could get all these libraries from your package or JSON, but, but that's like a giant just kitchen sink of here's everything that's already included. So it really giving to the developer to like, just if the AI makes a mistake, makes a wrong assumption. Like, that's basically the basic workflow of a custom instruction. Don't just fill it up with everything, but just as you use it, as it makes mistakes,

• 6:12Speaker 03

  just kind of spell it out like, oh, it doesn't do tailwind. Like, because if you cut in your file, it doesn't use tailwind, just tell it, use tailwind. I want to have my thing sorted. I want to have dark and light theme covered. And that's kind of the way. I mean, it's often dependencies that you wanted to use. It's code conventions you wanted to use. It's mistakes it's make. That's, that's kind of where you corrected.

• 6:31Scott Tolinski?

  What about like, um, you know, I think a lot about. So many libraries move fast, right? Can you reference docs, like specifically use this version's docs? Use whatever, spell V5 docs? Because the model might not have an understanding of that code style, right?

• 6:48Speaker 01

  There is a code referencing feature that I didn't demo that allows you to do some element of that. But I don't think the custom instructions can like pull from things that the model doesn't know about.

• 6:58Wes Bos?

  Oh, yeah.

• 6:58Scott Tolinski?

  Cool.

• 6:59Wes Bos?

  Yeah, that would be a pretty... Let's turn this into a feature request, you know?

• 7:03Speaker 01

  Oh, believe me.

• 7:07Wes Bos?

  I'm sure you just walked... Did you walk around today and people just come up to you and give you random suggestions?

• 7:13Speaker 03

  Actually, everybody was so happy. I got very few. Everybody asked like, so what else do you want? Everything shipped. Like, we didn't ship it. So there's like a few things here and there. But then it's like, yeah, we have that. Like, that's knowledge bases in GitHub Enterprise. Like, what you just mentioned, like, a way to reference other documentation that you already have that's knowledge bases and those features. So just like bringing these, make people aware and making sure they work easy and easily accessible as well.

• 7:42Wes Bos?

  And like when you're prompting it, you're also able to reference parts of your codebase and specific files as well, right?

• 7:49Speaker 01

  Yeah, so that is where, in the multi-file editing demo, I was able to say like, "Based on this file, I want you to pull in data from this activity service, then create a new file based on that." And it just knows and works. So you could pull in your package JSON and say like, "Hey, these are what I have installed. Make sure it's based on this." And there were some other things that I didn't get to demo pretty early based on time. Where, for example, GitHub search, you could, you can tag like the GitHub agent and say like, "Tell me about issue number eight" or something, and everything will be just right there in the chat.

• 8:22Speaker 03

  I know you didn't demo that. I took it out of my demo because of that.

• 8:27Speaker 01

  They were just like, "You're getting close on time." And I was like, "Dang it, okay, I'll cut that one out." And then there was also a code review where you can say like, "Hey, based on these files, could you give me some feedback based on things that we want in the repo and stuff?" There's a lot of cool things.

• 8:43Scott Tolinski?

  Yeah.

• 8:44Wes Bos?

  Okay, okay, that makes sense. Yeah, that's, that's really neat to be able to reference specific parts of your codebase because I know one thing we were saying is that it's not just the what model you use, right? The models are surprisingly almost table stakes now, or they're out there, but it's, it's how you give your, the data to the, the LLM.

• 9:05Speaker 01

  Right.

• 9:05Wes Bos?

  And, and how you then apply it, right? Like, what's the UI and whatever? And that's what is so exciting to me that GitHub and Microsoft are, are friends.

• 9:16Wes Bos?

  You can add the UI to the, to the editor, right? Like, like how much, maybe Harold, you can tell us this, is like, how much of the UI needs to be added to VS Code in order to make these things work, right? Like, are you?

• 9:28Speaker 03

  Yeah, I mean, most of the pixels you see on the screen are in VS Code core. So all that UI is handled. Because otherwise, the only other way to add UI would be either using VS Code components or it's using an iframe. And that's what you see everybody else doing. If you have any, like, non-VS Code looking UI, that's basically an iframe that's trying to get close enough.

• 9:48Wes Bos?

  Oh, yeah.

• 9:48Speaker 03

  So, yeah, all the UI is VS Code, like the attaching files, all those flows are in core. Uh, they're proposed APIs, but it's like the discussion hack can use around it, but they're mostly proposed because they move so fast in, in sequence and, and strong relationship with how we evolve chat.

• 10:03Wes Bos?

  Yeah.

• 10:03Speaker 03

  And you see that if you install insiders for VS Code, which if you want to get the latest and greatest, you should, you will see every day the Copilot chat extension updates as well, because there might be changes that are synchronized because of two, so they might be depending on each other. So it's a really close relationship there.

• 10:18Wes Bos?

  Just always trying new UIs. Like, one of the ones I really liked is you, you sent me a DM, you're like, you should try, or we had a call, you're like, you should try, what is it, the inline chat?

• 10:27Scott Tolinski?

  Yeah.

• 10:27Wes Bos?

  Where instead of opening the sidebar, you just write what you want.

• 10:31Speaker 01

  I love using that.

• 10:32Wes Bos?

  This feels way better to me.

• 10:33Scott Tolinski?

  Yeah.

• 10:34Wes Bos?

  Rather than going off the sidebar and working on something.

• 10:36Scott Tolinski?

  I end up not using sidebar chat at all.

• 10:38Wes Bos?

  Do it in.

• 10:39Speaker 01

  Yeah, I almost exclusively use inline. It's so nice.

• 10:42Wes Bos?

  And I didn't know about it, you know? And, and then, like, I'm surprised, like, I don't know how many other people might not know about it, but I was like, oh, this, this feels a lot better to me. And it's just all these different. Ways that you have to experiment, like are you guys always experimenting with different UIs for applying this type of stuff?

• 10:58Speaker 03

  Yeah.

• 10:59Speaker 01

  Especially for demos. Just like, okay, how can I present this information in the most efficient way possible? Where a lot of my demos started as me like writing comments and saying like Copilot will autocomplete this and being like, hmm, we shouldn't do it that way. But yeah, I think the inline chat is probably my favorite way of using it just because it's right there and I could say like, I actually don't like this and it'll redo it in some way. And that's, it's nice to be able to give that feedback.

• 11:25Speaker 03

  There's a lot of, I mean, interesting tricks that people don't know, like the inline chat, A, discovering it. So now we have more, more entry points, like we see a little sparkle if you want to open it. So we're trying to really make sure like, like if you're in the, even need of this feature right now, it is an entry point that makes it obvious. But I think like the one thing I noticed often, like you can follow up in inline chat. It's something that's people who are not used to AI prompting yet. It's like, oh yeah, give me something stupid. It's bad. Cancel. I'm gonna write that myself versus just like, oh, can you fix this? Okay, I'm done.

• 11:56Wes Bos?

  Yeah.

• 11:57Speaker 03

  So there's just these little things where making them super obvious, like changing the little field, the text in the field. There's so many UX, AI UX things that have to evolve to, to nudge people on the right path to enforce these best practices. But I think from a demo perspective, I like, I demoed writing a chess game in 3D from scratch using O1, which is a fun demo, but not real world, but it, it makes okay, cool. But I started my first part of the demo was like, I did it in chat initially when I wrote the demo. It's like, it's kind of creating a new file from chat is kind of clunky still. You can drop into a new file and then you save it. And then, so eventually I just opened inline chat and then I wrote like 500 lines of code. It looks beautiful. It's just like, I had to speed it up because like it's going on for forever.

• 12:41Wes Bos?

  Oh, yeah, yeah.

• 12:43Speaker 01

  3D chess, that's a big one.

• 12:45Speaker 03

  But it looked, it looked great because then like, oh, like now I should really enable minimap so it looks like, so you can actually see the text coming in. So there's some, yeah, depending on what you do, this, I think figuring out which UI to use, I think is one, one struggle I see.

• 12:58Speaker 01

  And it's almost which UX to use too, like how do you want to use it?

• 13:01Speaker 03

  Yeah, what's your preferred flow? Like, do you, and also there's this confidence, like, are you in an exploratory, like, more flow where you wanna, like, I have a problem, I don't know the solution, I don't even know my problem yet, or are you like, I need to edit these files, and I need to, I know how it looks like, and that's where, like, multi-file edit really shines. You're very explicit

• 13:18Wes Bos?

  Yeah.

• 13:18Speaker 03

  about which files, very explicit about, when you look at the code, yes, that's what I wanted, and you hit accept.

• 13:24Wes Bos?

  Mm-hmm.

• 13:24Speaker 03

  And that's, that's the sweet spot, versus in chat, you would ask, like, oh, like, which library could I use? Or what's, what's the best algorithm to, to sort through that? And then you can figure it out, and you slowly get it in, versus just inline chat, like, rewrite this to async, done.

• 13:38Wes Bos?

  Yeah, yeah.

• 13:39Scott Tolinski?

  I thought that workspace stuff felt like a new UI, or UX even, direction for working. Because we were saying, like, all right, are we, are we modifying the editor? Or is, like, we need to rethink, like, the paradigm of an editor, right? But like, even the brainstorming, or how it brings in a to-do list, essentially, that you can then modify, and, and man, that's all just, I think those are really awesome explorations. Uh, you had mentioned, Harold, that, like, before, well, like, even like, days or weeks before this, everything's changing so quickly, that's why you can't record the demos ahead of time.

• 14:12Wes Bos?

  Yeah. Yeah.

• 14:13Speaker 01

  Literally changed this past week.

• 14:15Speaker 03

  Fast-moving.

• 14:16Scott Tolinski?

  Is it, is it, is it a lot of features need to be?

• 14:18Speaker 03

  Casey wasn't happy.

• 14:19Speaker 01

  There's a lot of changes to my demo.

• 14:21Scott Tolinski?

  Oh, yes, okay. And then, is that like, features being pulled because they're not ready, or things being added, or just UI changes, or all the above?

• 14:29Speaker 01

  Just added and updated, where it's just like, oh, the chat is a little sleeker now. Cool, but now I gotta change some stuff.

• 14:35Speaker 03

  Like, like, like, last minute, I noticed, like, in, in my demos, I always had to make this multi-file edit, when it really big, couple edits, because the buttons were so big. So it was like, because it was accept all, save all, it's like, big buttons. So it was like, I, it doesn't work for, like, tiny screen demos, and you probably hit this as well.

• 14:52Speaker 01

  Yeah.

• 14:52Speaker 03

  So can we, can we?

• 14:53Wes Bos?

  Being in my existence.

• 14:54Speaker 03

  Can we make the button, can we make the save button, and then we decide, okay, let's move it all? So it's just like these little tweaks, but that, they affect, of course, how you talk about stuff, how you point at stuff. And they didn't really change the flow itself, but they're just like, oh, another thing.

• 15:08Wes Bos?

  Yeah.

• 15:09Speaker 01

  Yeah, and there's so many different views where, like, there's actually a really Really cool view for the multi-file editing where it's all in one place and you can just kind of scroll through leaf through. And I thought it'd be cool, but then people wouldn't see like the magic of, oh, it created this file and this file.

• 15:22Wes Bos?

  Oh, yeah, it just looks like one file.

• 15:24Speaker 01

  Right, yeah.

• 15:25Wes Bos?

  Is that actually a view where you can see it all in one go?

• 15:27Speaker 01

  Yeah.

• 15:28Scott Tolinski?

  Yeah, I like that.

• 15:29Speaker 01

  Yeah, no, it's way better than, for real-life work, I would use that view.

• 15:34Wes Bos?

  Okay.

• 15:34Speaker 01

  But for a demo, it was cooler to show like it made this and this and this.

• 15:38Speaker 03

  It's really cool, you just edit this in a recent month, it's a multi-file, multi-diff view. It looks amazing, it makes it really easy to scan.

• 15:47Speaker 01

  It's really nice.

• 15:48Wes Bos?

  That's, that's great that you're spending time on that because I find one thing when I'm looking at the stuff is if I get overwhelmed or I'm scared that it's doing too much and I can't, can't grok it quickly enough, like this is what I want.

• 16:02Speaker 01

  Right, where you're like, oh, it's getting unfamiliar.

• 16:04Wes Bos?

  You're touching multiple files, yeah, hmm, no, too much, it's doing too much, you know, click X and I'll just do it myself, so. Being able to make that like comfortable of where you can quickly grok it and understand what's changing.

• 16:15Scott Tolinski?

  Yeah, I think we both said we both kind of stay away from multi-file generation just because of that, you know?

• 16:22Speaker 01

  Right, the scariness.

• 16:23Scott Tolinski?

  Yeah, not being able to really understand what it's doing.

• 16:25Speaker 03

  And it's hard to steer too because someone you need to tell it like that edit in that file wasn't right, but don't, don't touch rest. So it gets harder to, to prompt if you, to fix it.

• 16:34Wes Bos?

  Yeah.

• 16:34Speaker 03

  And that's why we like the, in multi-file, you can like revert single changes.

• 16:38Speaker 01

  Yeah, you could say this one is good, this one's bad.

• 16:41Speaker 03

  So you stay in control around that where it gives you like, oh yeah, this wasn't right, you don't need to go in and prompt it because that, that's like mental effort as well.

• 16:48Wes Bos?

  Yeah.

• 16:49Speaker 03

  How do you describe like that change?

• 16:50Wes Bos?

  You know what that's a killer feature for is the refactoring, you know? Like, a good example would be, I have a form and I'm changing the field from name to title, you know? And there's, there's a label with a capital T title and the like, what is it, the F2 rename symbol is, is good, but there's often other parts of the, the application that are not tied to that symbol, right? There's UI and whatever, or adding another field, you know? And you have to touch your schema, you gotta touch your backend, you gotta touch the like React hook that has stayed inside of it and updater functions. That's amazing. They're like, ah, just I can so quickly.

• 17:26Speaker 01

  It just works.

• 17:27Wes Bos?

  Do it, yeah.

• 17:27Scott Tolinski?

  You just find and replace the the string of name.

• 17:32Speaker 01

  Easy peasy. You never use the word name in a codebase.

• 17:36Scott Tolinski?

  That's the one specifically.

• 17:38Wes Bos?

  I actually have a tip where I I can do a find or replace in VS Code and it will keep the case. Um, which is really good because sometimes stuff is uppercase, sometimes stuff is camel case.

• 17:48Scott Tolinski?

  Yeah, preserve case.

• 17:50Wes Bos?

  Preserve case when you find or replace was good, but obviously it's the the L L M's are are a little bit more flexible.

• 17:57Speaker 03

  I mean, for a search and place might be interesting, like what the L M does. So that's that's what we're looking like where else in these flows AI can help like we have one. So we need to talk about the experimental UIs. Like if you go into, if you now in the latest release, go into your settings and look for GitHub Copilot Chat, you'll find a whole section just experimental. And one of those is like where we go AI search. So in in the search panel, we'll actually use the semantic search it has to add additional results below. So it's not like the exact search term user, but you can do like form submissions or something and then it will go in.

• 18:29Speaker 01

  Search based on vibe.

• 18:30Speaker 03

  Yeah. So it gives you like, you don't have to think about like, oh, what's the exact wording? Is it like the right case? Is it? Yeah, you can be more open just.

• 18:39Wes Bos?

  Oh, man, it's like a fuzzy search. You know, it's I the other day, I have like hundreds of demos on my computer and I can never find the demo. I was like, I built something, but I don't know where it is. It's somewhere on my computer. And I usually just drag my entire code folder into VS Code and start doing like a fuzzy search because that's better than Mac OS's search, right? But take it one step further. I built something with a webcam that does X, Y, and Z.

• 19:04Speaker 01

  Yeah.

• 19:05Scott Tolinski?

  Oh, Wes, come on. Yeah, yeah.

• 19:08Speaker 03

  You see add work base.

• 19:10Speaker 01

  I was gonna say that that you could make a Copilot extension for that. That would be pretty good. Which I can talk about.

• 19:17Wes Bos?

  Really? Tell us about that.

• 19:19Speaker 01

  So that's something that I demoed a little bit in the keynote. But Copilot Extensions was released this past May. I think it's technically still public preview, but anybody can access it and build for it and stuff. And it's basically you can create your own agents with different commands in Copilot Chat and have it do whatever you want. And so the one that I demoed was the launch Darkly one, where you can create a feature flag, name it, toggle it, and basically control all of it within VS Code. One that I made recently was actually based on my old startups app that we shut down, but I missed it. And now it's in VS Code, where it was brainstorming buddy, where I was able to use the Copilot, you can use chat with your voice. And so you can talk instead of typing. And so I made a Copilot extension

• 20:03Speaker 01

  that let me just kind of talk out my ideas inside Copilot Chat and then use whatever results I wanted from that to write code. And it's not bad. It's basically a serverless function that you write stuff with and then you can make it go through files on your computer or whatever APIs or whatever you want. That could be cool.

• 20:23Wes Bos?

  Yeah, from my entire computer. I can never find anything.

• 20:27Scott Tolinski?

  Totally. Talk to the computer. And there's a Sentry extension, so shout out to Sentry.

• 20:31Speaker 01

  Yeah, exactly. I heard this is really good, actually.

• 20:34Scott Tolinski?

  Oh, I have no doubts about that.

• 20:38Scott Tolinski?

  And if you want to see all of the errors in your application, you'll want to check out Sentry at sentry.io/syntax. You don't want a production application out there that, well, you have no visibility into in case something is blowing up and you might not even know it. So head on over to sentry.io/syntax. Again, we've been using this tool for a long time and it totally rules. All right.

• 21:03Wes Bos?

  Can we ask you about Cursor? Is that allowed?

• 21:05Scott Tolinski?

  Is that a forbidden word?

• 21:06Speaker 01

  You know, I don't actually know, but ask me and then I can find out later.

• 21:11Wes Bos?

  So I've been tweeting about all the updates today. Everybody's stoked because they want a lot of those features, right?

• 21:17Speaker 01

  Right.

• 21:18Wes Bos?

  And quite a few of these things today announced, which is things that Cursor can do and we've all been wanting. And I've been kind of root. Looking for it. One thing, and we want to ask is if this is coming, is the multiple line suggestions? I know Copilot has multi cursor completions with ghost text, but being able to, like, as you're typing something, it will suggest, oh, edit these four lines within it. Is that something that is gonna come, or is that something you're looking at?

• 21:47Speaker 01

  You can probably speak to it a bit more, but yeah.

• 21:49Speaker 03

  Yeah, we have. So if you look at, like, the GitHub Next has been working on for a bit, the next edit suggestion.

• 21:55Wes Bos?

  Okay.

• 21:55Speaker 03

  Came out end of last year, I'm not sure exactly when, but it's been like in the works for a bit, like same similar UX of here, you made a change, this is the next change.

• 22:04Wes Bos?

  Yeah.

• 22:05Speaker 03

  So it's, yeah.

• 22:06Speaker 01

  And like suggested changes beyond what it's made so far.

• 22:09Speaker 03

  Yeah, so also going in, not just ghost text, but actually making edits. And then, yeah, so we've been, we've been taking it on, it's, it's been, yeah, out of GitHub Next, busy moving it. It's, it's the research.

• 22:19Wes Bos?

  Yeah.

• 22:19Speaker 03

  And now taking on and bringing it into the world.

• 22:22Wes Bos?

  Okay.

• 22:22Speaker 03

  It's on our list. I have it working locally, we've been self posting it.

• 22:26Wes Bos?

  Okay.

• 22:26Speaker 03

  Uh, but it wasn't just ready yet for the grand announcement. We would like to announce stuff that people can use right now.

• 22:33Wes Bos?

  Yeah.

• 22:33Speaker 03

  This is my keynote, everything is ready now for you to try. We just released it today, which is very true for today, especially.

• 22:40Speaker 01

  Yeah, we wanted everything to be out this week, and the things that couldn't, we'll do soon.

• 22:45Wes Bos?

  Yeah. Okay, yeah, so I'm looking at a demo right now, and they're editing one function, and it's trying to suggest a change to another function, because you added a parameter to this function here, oh, you probably want to start using that in another function.

• 23:00Speaker 03

  Right, like adding a component and a React thing, and then, then it just skips it again.

• 23:04Wes Bos?

  The UI for that is ghost text, which is the. It's like auto completion. Yeah, exactly.

• 23:10Speaker 03

  And the videos here, yeah, it has, has changed since. So that's a big part of how, like, where the affordances come from, how to make it easier to use, is finding right UIs. Because sometimes edits can be further down in the file, sometimes, like, how do you make it different? How do you make it easy to review is, is still like a really hard problem. Especially if it's, if it's just popping up with some confidence. Where it's not like even something you ask for, but it's like, hey, we want to apply this. Oh, I wait, I like to check out what you're telling me here. So it shouldn't slow you down, but it should be enough on the side. You can easily say like, yeah, that's what I want. And you can just tap over it.

• 23:49Wes Bos?

  Yeah, there's a fine line between it being annoying and

• 23:53Speaker 01

  Right.

• 23:53Wes Bos?

  super helpful. And I don't know where that that line is because sometimes I have to like, especially when I get into complicated reduces.

• 24:01Speaker 01

  Oh, don't get me started.

• 24:02Wes Bos?

  I'm just like, no, stop. Let me think about this for a second. That's not what I want, you know?

• 24:06Speaker 01

  Yeah. Sometimes it gets too magical with certain things. Yeah. And you want to, you want to be able to still understand your own code.

• 24:13Wes Bos?

  There's a fine line. So this will be able to both suggest additions as well as suggest like things that can take away from the code as well.

• 24:21Speaker 03

  Well.

• 24:21Wes Bos?

  The plan. And will it, will it just be ghost text? Or will it like, because cursor shows like diffs. It will show like plus in green and minus in red. Is that something that's maybe added to VS Code? Well, we have, you showed that in your

• 24:33Speaker 01

  I was gonna say, it's, it's a lot of like what you saw in the multi file edits. And I think everybody's trying to just make sure that the research shows that this is the right way to do it. Like users actually want it this way, not just thrusting our opinions on them.

• 24:47Wes Bos?

  Yeah.

• 24:47Speaker 03

  I think also the, the connecting the bits, like you have next edit suggestion, but how do you get from like, okay, this is you're doing it on my track. Do I want to keep tap, tap, tap? Or do you just want to say like, do you want to actually pull this over into a multi file edit? Because I think I know now what you want. And there's some more changes you can just do in one bit versus tapping through.

• 25:06Wes Bos?

  I find that in cursor sometimes I'm like, it does about four lines at a time. And I was converting an array of strings over to some other data type. And it was just, I had to hit is tab. You wish it was doing a little bit more. Yeah. And I was like, no, I want, you obviously know what I'm doing here. I want, I have 40 items in this array. It's, you're doing it for every line. That would be cool if it then suggested, hey.

• 25:30Speaker 03

  Yeah. So these features don't live in isolation, but they kind of know about each other. Like, or maybe if you open chat and just. Finish what I started.

• 25:37Wes Bos?

  Yeah.

• 25:37Speaker 03

  And just picks up like, because this NES already builds up this context of what you're working on. It knows your past edits. So what if you can give that to chat and just say, this is the multi added I started.

• 25:49Wes Bos?

  Yeah.

• 25:49Speaker 03

  And these are the files you should apply it to, or I just did this edit.

• 25:52Wes Bos?

  Yeah.

• 25:53Speaker 03

  Please apply it to these five other files and could run that. I think that's, that's the magic we want to unlock eventually where it's, it's not just like different feature teams work on stuff, but, but it feels like one cohesive.

• 26:03Speaker 01

  Yeah. And that's also where the repo indexing is really nice too, because it really uses your repo as a source of truth. Instead of just ideas that it has about code from the model.

• 26:13Wes Bos?

  Oh yeah. So it repo indexing will obviously just like go through your, your entire code base. And what does it do? Get ideas as to?

• 26:20Speaker 01

  The style.

• 26:21Wes Bos?

  Code format.

• 26:22Speaker 01

  Yeah, format, what functions exist and stuff. And so like, keep referring to my demo, but that's.

• 26:28Wes Bos?

  Yep.

• 26:28Speaker 01

  But what I've been doing for a while.

• 26:31Wes Bos?

  Yeah.

• 26:31Speaker 01

  But yeah, like the first thing that I asked was, are we using a line graph anywhere in the code base? And it did like intent detection saying, okay, based on what she's asking, I know to ask the workspace agent to go through the repo based on what I've indexed. And it just did all of that in the chat right there.

• 26:47Wes Bos?

  Amazing.

• 26:47Scott Tolinski?

  So, okay. So you guys, I mean, it feels like we're in a new world of interfaces and UX for these things. I mean, even anytime something new comes out, it's a slightly different, we all go, oh man, this is a little bit different, a little bit.

• 26:59Speaker 01

  Right.

• 27:00Scott Tolinski?

  Better. How do you develop new ideas here? Is it just doing a lot of coding and just what feels nice for me? What would feel nicer? Is it research? Like what is?

• 27:11Speaker 01

  I know our research teams do a whole lot of research and user testing and iterations and stuff like that.

• 27:17Scott Tolinski?

  Yeah.

• 27:18Speaker 01

  For like my own personal stuff, I'm more just like, if I keep trying this, what am I comfortable with?

• 27:23Scott Tolinski?

  And yeah.

• 27:24Speaker 01

  Like there's sometimes where I'm just like, I'm just going to turn it off. I just want to like quietly code some nice little HTML, not even think about anything and then.

• 27:32Scott Tolinski?

  Use Emmet or?

• 27:34Speaker 01

  Right, exactly. Be like, just, just simple stuff and then I'll turn it on when I want to do some, some more magical things. And so like, I, I think. Every individual developer kind of has their own iterations that they do. But at GitHub itself and Microsoft too, on the VS Code team, there's a lot of research being done, tons of user testing and talking to customers and open source projects.

• 27:56Speaker 03

  Yeah, that's something, there's so many chats. Like so for VS Code, we have a public repo where people can file issues.

• 28:02Wes Bos?

  Yeah.

• 28:02Speaker 03

  And you find me responding to issues in there as well. It's just triage by the team. That's one source. We have run surveys in the tool, like most products. But we also have this huge field team that is sales and customer success. And everybody out there talking to customers, talking to clients, talking to developers and bringing back feedback. So this is, and it's interesting because you get different kind of personas. And they're from like the enterprise decision maker who wants like, oh, we need, we needed to buy two software licenses. And we need to customize it to our ginormous monorepo. And it needs to work fast or all these other little details that you don't see in your own usage.

• 28:43Wes Bos?

  Yeah.

• 28:43Speaker 03

  I think that's interesting. But like the VS Code team also does a lot of, if a feature is self-hosted, if you use it heavily, it becomes, it becomes great. So we're also trying to like a lot of this, just by checking the AI tools, basically like, does this make us productive?

• 28:59Wes Bos?

  Yeah.

• 29:00Speaker 03

  But I also bring it out to customer development. So when we actually talk, bring it out, it's like, let somebody try it out. Talk to customers about like their experience with AI in general, but also have them try out a tool, try out different tools, try out different AI flows and try it out on a code base they know, try it out on a code base they don't know. It's vastly different.

• 29:18Wes Bos?

  Oh, yeah.

• 29:18Speaker 03

  So we see people really struggle with something that in a language they're comfortable with. And that's still a thing of AI, like some features work really well when you know what you're doing. And some features really fall apart when you're like in a completely new code base and AI just leads you astray. And you follow, follow red herring and you just lose time.

• 29:39Speaker 01

  Yeah. And I know that the GitHub Next team too, spend so much time figuring out like, okay, if we made this experiment, what would people think of it? What changes should we make?

• 29:47Wes Bos?

  Yeah.

• 29:48Speaker 01

  Is it something worth pursuing or is it something that we should just say that was a fun experiment?

• 29:52Wes Bos?

  Yeah. That's so cool.

• 29:53Speaker 03

  Love VS Code teams.

• 29:54Wes Bos?

  I think about that a lot as just like. Do I not like the way that this works? Because I just need to learn how it works? Or because I often look at features like that. I'm like, it might just be me, you know? Maybe I don't like this, but it's maybe I just need to learn a better approach to it.

• 30:12Speaker 03

  It's really easy with AI to to show that it's bad. You just do bad prompting. You give it a task it's not good at. And that's why I think why more experienced developers have an easier time figuring out how to use AI, because they quickly learn from like their own sense of skill. Like this is where it's good at and this is where it's not good at, which which can limit you as well. As it evolves, you're like, OK, I only use it for basic tasks, even though it has grown its skill over time. Like with more context window, with different models, with different contexts, it gets better. But one source of innovation is really interesting. We've been, I touched on in my talk later, is we've been hacking the past weeks on our new extension APIs in VS Code. So you can actually access a lot of co-pilot capabilities. From in the VS Code extension API.

• 30:57Speaker 03

  And you've been dabbling in that space. So you have access to the language models. You can actually run LM calls in VS Code. So you can write your own little kind of brainstorming guide just for VS Code. You have access to tooling. So you can use like the code search bits that we have within your API. So you could do that tool to like, which demo did I do? Or write me a new demo based on this demo plus this demo. And I want to see the best of.

• 31:21Wes Bos?

  OK.

• 31:22Speaker 03

  And then you have access to make a chat participant as well. So you can write your own custom commands, which is really this idea of like, what if I had an agentic flow that that can take a file and summarize it in a specific file for me? So you can you can.

• 31:36Wes Bos?

  Extension extensions.

• 31:38Speaker 03

  Yes.

• 31:38Wes Bos?

  That's cool, actually. That's that's really neat that like, if you think about all the useful extensions that VS Code has, now what does that look like when you also say, hey, you can have access to the the LLM?

• 31:51Speaker 01

  To co-pilot.

• 31:52Wes Bos?

  Yeah, right.

• 31:53Speaker 01

  Hands.

• 31:53Wes Bos?

  Yes, yeah. Pretty nifty stuff.

• 31:56Speaker 03

  And if you already have extensions, there's so many companies who build extensions internally as well. That's actually when we first shipped it out as a capability. We didn't even talk about it much. And then we broke it one day and there were like five enterprises we never heard about. Hey, can you fix it again? People are already like, oh yeah, of course we use this.

• 32:15Wes Bos?

  Oh, really?

• 32:15Speaker 03

  Yeah.

• 32:16Wes Bos?

  Are you able to tell us what kinds of stuff they were doing internally?

• 32:19Speaker 03

  Actually, we don't know yet. So we know we broke it.

• 32:24Wes Bos?

  You heard.

• 32:25Speaker 03

  Yeah.

• 32:25Speaker 01

  It's all that matters.

• 32:26Speaker 03

  Use cases like connecting it to your own issue tracking system, like anything that's in-house that the AI wouldn't usually talk to. You can easily, same with the Copilot extensions on the server side. So then it works also on the GitHub.com chat, it works in jetbrains as well in the future. So there's a lot of kind of using, building that extension once and using it in all Copilot services. Or if you just care about VS Code for your own use cases or your teams, then you can do that as well.

• 32:53Wes Bos?

  Yeah. Man, that's great. I'm just looking at my, my list of VS Code extensions and I'm trying to think of like.

• 33:00Speaker 01

  How can I be this smart?

• 33:01Wes Bos?

  All of these, you add, you add AI to any of these. You haven't really seen that yet because it's, it's either too large to run a model locally or it's too expensive to, to do that type of thing, but.

• 33:13Speaker 03

  Yeah, there's really, really cool demos from Stripe and MongoDB, for example, are in there. So they, they use it to, to write the code based on the information they have in your own setup.

• 33:24Wes Bos?

  Okay.

• 33:24Speaker 03

  Just make, make it like integrate a Stripe checkout and it integrates the Stripe checkout.

• 33:29Scott Tolinski?

  That's cool. I'm thinking Todo Tree, Todo Tree, skins, to-dos, skins.

• 33:33Wes Bos?

  Oh yeah, and then just does them.

• 33:35Scott Tolinski?

  Better comments.

• 33:35Wes Bos?

  Done, to done.

• 33:37Scott Tolinski?

  Right, yeah.

• 33:37Wes Bos?

  AI, done. Ta-da.

• 33:40Speaker 03

  Do, just, just do.

• 33:41Wes Bos?

  Do, yes.

• 33:44Wes Bos?

  That's great. Yeah, it just writes the code for you. Yeah, that's actually not a bad idea.

• 33:49Scott Tolinski?

  Yeah, not a bad idea, no.

• 33:50Wes Bos?

  Because like that's, before I learned about the inline chat, I was using just comments as a way to like make it do what I wanted. I would just write a comment.

• 33:59Scott Tolinski?

  You write the comments first.

• 34:00Wes Bos?

  And then you go on the next line and hope that it did it. And then I was like, whoa, it's much easier if you just pop the whole editor open and, and write what you want there.

• 34:09Speaker 03

  Yeah. So if you check out, there's a setting and experimental section in Copilot chat that gives you this experience. So you can basically. You write natural language, line of natural language of what you want. And then it shows you just hit Ctrl I and I'm gonna make it happen for you. So it picks up the comment, uses it as a prompt for inline chat. Picks up the comment and just.

• 34:27Wes Bos?

  You know Warp has that, so my terminal has that. Yeah. And I do it all the time, like FFmpeg convert this MP4 into an MP3. Yes.

• 34:37Speaker 01

  And then tabbing.

• 34:38Wes Bos?

  Specifically FFmpeg.

• 34:40Speaker 01

  I was gonna say FFmpeg specifically needs a lot of that.

• 34:44Speaker 03

  It's own AI.

• 34:44Wes Bos?

  Or the one I always do is I get committed a file that was very large and now I need to remove it from my Git history. I don't know what that, I always forget what it is. It's git rm cache dash dash whatever. I always forget what it is, so I just, I just type it. I accidentally committed this large file, please remove it from the Git history and.

• 35:03Speaker 03

  Yeah.

• 35:04Wes Bos?

  Does it for you.

• 35:05Speaker 03

  Right, so the Warp you say it in Warp, but in VS Code you would have those. The inline chat also is in the terminal.

• 35:10Wes Bos?

  It's in the terminal as well. I need to, maybe I need to make a, a jump over to the VS Code terminal.

• 35:16Speaker 03

  Yeah, with multi-window you could now pop it out.

• 35:19Wes Bos?

  Yeah, that was my, my hangup was always that you can't, you couldn't pop it out. But it's been, you pop it out for eight months now or something like that. I did not even know that, yeah. You gotta watch my video, Scott. I didn't watch your video.

• 35:30Speaker 01

  You do a lot of videos, man.

• 35:33Speaker 03

  Thankfully we retweeted it too.

• 35:35Wes Bos?

  Yeah, you can pop it out. Oh, that's great. Cool, um, anything else we haven't, haven't touched upon, anything else you're pretty stoked or?

• 35:42Speaker 01

  It's in Xcode now, that's pretty exciting, yeah.

• 35:46Wes Bos?

  So I downloaded, um, a, I opened up Xcode the other day and of, of course, for some reason it deleted all my simulators for some reason. Of course, to do that all the time. So I redownloaded it. And there's a little checkbox for Apple's own thing. And I was like, oh, it's interesting, Apple's getting into that game, but now you can run GoPilot on Xcode.

• 36:06Speaker 01

  Yeah, no, that was, that was an announcement that, yeah, we made today and it's really exciting. It was, it was fun actually getting to say it to the people because they're like, what? They didn't expect it and, and yeah, I think that's going to be a really big one for so many iOS developers for sure.

• 36:23Scott Tolinski?

  Yeah, because that's getting in front of a completely different group of people.

• 36:26Speaker 01

  Yeah, exactly. A lot of people were, a lot of iOS development, yes, you can do it in other editors, but Xcode is where you live.

• 36:34Wes Bos?

  That's where everyone's using.

• 36:35Scott Tolinski?

  You know what? I have been working on a video game with my son using Godot, and they have like a built-in text editor where you write GD script. And I found myself just opening the product in VS Code, simply to use Copilot with the Godot script. But like, again, it's interesting to think about the future of using Copilot outside of VS Code. And yeah, man, yeah, that like reached a whole different amount of people. It's pretty amazing.

• 37:00Speaker 01

  Yeah, and that's, it's been cool seeing it being able to be added to so many places. And I think ultimately, that is what the team hopes to do is to just keep pushing it to as many editors as possible.

• 37:11Scott Tolinski?

  Yeah.

• 37:12Wes Bos?

  Yeah, although we always make fun of, make Jetbrains jokes on this thing.

• 37:16Scott Tolinski?

  Oh, gosh.

• 37:17Wes Bos?

  The number one comment on every video I do is,

• 37:20Scott Tolinski?

  Webstorm.

• 37:21Wes Bos?

  Webstorm already does this. Webstorm does it. And I always reply, what's that? It drives them nuts. Obviously, it's a fantastic editor as well, but that's my, that's my little shtick that I like to keep up.

• 37:35Speaker 01

  Respect. Commitment to the joke is what matters.

• 37:38Wes Bos?

  Yeah, exactly.

• 37:40Scott Tolinski?

  You got a lot of those where you just, you got them ready to go.

• 37:44Speaker 03

  Yeah, Horace has said every time we get to do like this live demo, it's like, oh, there's a Microsoft person with a Mac laptop.

• 37:51Scott Tolinski?

  Oh, yeah.

• 37:52Wes Bos?

  Oh, yeah. Yes. I bet you get that a lot. But lots of people use Macs at Microsoft, don't they?

• 37:57Speaker 03

  It's also, it's a cross-platform editor, like, when you use it heavily on everything. Yeah, I have a Windows machine at home.

• 38:04Wes Bos?

  Lots of people use it on Windows.

• 38:06Scott Tolinski?

  A lot of people that work at Google use iPhones. I mean, yeah, you gotta use what you like, yeah.

• 38:11Wes Bos?

  Yeah, you kind of have to. Just kidding.

• 38:15Wes Bos?

  Cool. Anything else we didn't hit? Do you have anything else there?

• 38:18Scott Tolinski?

  No, no, nothing explicitly, yeah.

• 38:20Wes Bos?

  And any, I can't ask you for any in the future. I'm sure you've been working your tail off for the last little bit.

• 38:27Speaker 01

  At this point, like, my brain is just kind of white noise where I'm like, wow, we made it here.

• 38:31Wes Bos?

  Yeah.

• 38:32Speaker 01

  I'm gonna sleep today.

• 38:33Scott Tolinski?

  Yeah.

• 38:33Speaker 03

  Yeah, I think one thing, if you, if you check out the experimental section and GitHub Copilot Chat, there's so much more stuff coming up that we didn't talk about so many quality of life things now. If you open chat, you see like this little context bubble that you can now control what goes into chat. There's so many little things, just like the implicit context detection or detection where it just invokes the right thing based on your prompt. So all the little things we haven't talked about.

• 38:58Speaker 01

  Yeah, like the code reviews are so cool. I wish I could have demoed that, but that's, I think it's coming out this week.

• 39:04Speaker 03

  Yeah, it's all access. It's coming out to all, because it's, it's public waitlist. Also subscribers have access.

• 39:11Wes Bos?

  So anyone who has Copilot subscription can get access to all these features. That's cool.

• 39:16Scott Tolinski?

  Okay, to be clear, for people who might be listening to this, how do you get in, they're in VS Code? How do you turn on experiment? Because you've mentioned chat experimental.

• 39:23Speaker 03

  So go into Settings, scroll down on the left side for GitHub Copilot Chat. You can do like the tag search as well. If you tag experimental on the right side of the search. And then there's a whole set of preview and experimental settings. Some of these are more self-explanatory. Like we have, one is temporal context. If you open, like one thing completions does kind of magically, it, it looks at your open tabs and what you recently edited.

• 39:46Scott Tolinski?

  Yeah.

• 39:46Speaker 03

  And we kind of brought that into inland chat. Like what if inland chat knew that you just edited something over here? And it brings that, that file context at least over. So there's some of these ideas that are, we're still kind of trying to figure out what exactly the shape is.

• 40:00Scott Tolinski?

  Yeah.

• 40:00Speaker 03

  There might be side effects, like one, there's a big section on Copilot instructions in there. You can have Copilot instructions for the test command. You can have Copilot instructions for specific areas. Like the review one as well. So just, just more, more power user ops, but also things we're kind of exploring. We're going to feedback on.

• 40:18Wes Bos?

  That's awesome. And if people want to learn about all these different features, what's the best spot to?

• 40:24Speaker 03

  VS Code will tell you when there's an update and then you can.

• 40:27Speaker 01

  I know the GitHub blog has been just kind of pumping out posts about stuff.

• 40:31Speaker 03

  Yeah, change logs.

• 40:32Wes Bos?

  The once a month where the, the, the change log comes open, there are a lot, a lot of stuff will be in there as well. I love going through that every time it pops up.

• 40:40Speaker 01

  We got to chat about it more, I think, because. There's so many cool things that come in, but we're

• 40:45Scott Tolinski?

  There's things I miss, yeah.

• 40:47Wes Bos?

  Oh, yeah.

• 40:47Scott Tolinski?

  I feel like I read it all and I

• 40:48Speaker 03

  Just a fire hose.

• 40:49Wes Bos?

  Yeah.

• 40:50Scott Tolinski?

  Totally.

• 40:50Wes Bos?

  I feel like that's, they do, it's a pretty good job at like doing a quick rundown

• 40:54Speaker 01

  Yeah, it's a good rundown, for sure.

• 40:56Wes Bos?

  of the new features in there.

• 40:57Speaker 03

  Yeah, if you follow a code handle on Twitter, I think that's where you learn to kind of breaking down into smaller bits in videos. So I think that's

• 41:04Wes Bos?

  At code, yeah. And Burke does a pretty good job. Burke does a lot of videos.

• 41:09Speaker 03

  Burke Olivia, I had the whole team. He's rocking it.

• 41:11Wes Bos?

  Viasco, big on TikTok as well.

• 41:12Scott Tolinski?

  Big on TikTok, yeah.

• 41:13Speaker 01

  Really good at TikTok.

• 41:14Scott Tolinski?

  I know.

• 41:15Speaker 01

  I feel like I learn new things all the time. I'm like, oh, hey.

• 41:19Wes Bos?

  My, another one of my shticks is anytime they use my theme in one of the TikToks, I comment, what theme is that?

• 41:25Scott Tolinski?

  Oh, yeah. He comments on her own videos, great video, guy.

• 41:31Speaker 01

  That's good.

• 41:32Wes Bos?

  Oh, great. Cool. All right, I think that's, that's all we got today.

• 41:36Scott Tolinski?

  That's all we got, yeah.

• 41:37Wes Bos?

  Thanks so much for coming on. Really appreciate all your time. This is really cool. I'm sure you guys are zapped by now, so I don't know if it's a party tonight or not, but sleeper party.

• 41:46Speaker 01

  Yeah, I was going to say a nap party.

• 41:48Wes Bos?

  Nap party.

• 41:49Scott Tolinski?

  Nap party, yeah. I'm feeling that right now, too.

• 41:52Speaker 03

  So there's probably a nice dinner somewhere, hopefully.

• 41:54Scott Tolinski?

  A nice dinner, yeah.

• 41:55Speaker 01

  For sure.

• 41:56Wes Bos?

  Well, congrats on an awesome conference and thanks again.

• 41:59Scott Tolinski?

  Yeah.

• 41:59Speaker 01

  Thanks for having us.

• 42:00Scott Tolinski?

  Congrats.

• 42:00Speaker 03

  Peace.