VS Code, GitHub & Copilot - UNIVERSE 25 Announcements + Reactions

Welcome to Syntax live from, where are we, San Francisco, live from New York.

We are not live at all. We're recording here at GitHub Vercel twenty twenty five. We're here last year, which is pretty interesting, and it's it's nuts to see. Like, last year, we're talking about, like, better copilot, like, tab completion and stuff like that. And now it's just like agents and all the stuff CJ hates. So we're gonna we're gonna go through a couple things here. We're gonna kinda rattle through all the announcements that they have and and talk about that as to, like, are they catching up to to Cursor and all these things, and and what are what are the interesting stuff, and how does it all work together? We're gonna talk about our badges, which is really cool. I think possibly very maybe even more interesting to some of the audience.

And, yeah, it was good. We had we had a meetup last night. Thanks to everybody who came out. That was a hoot. Oh, good time. That's great. Everybody man, we had a big turnout last year for the meetup. Yeah. And, it was a just like a great mix of the types of folks from all different companies and working on different problems, fans of the show. And this year was just even better. We had a massive table of free stuff. We had

security guards and police officers coming up and being like, can I get some of this stuff? It was like a Yeah. Check X for the car. Yarn Francisco cop driving around the city with our hat on. Yes. Yeah. Our Internet hat. Internet hat on.

Yeah. Props to everyone who came out. That was that was always really fun having meetups and getting to chat with people, because you get to hear the type of stuff people are working on, the problems that they're hitting, what they're learning. You don't necessarily hear that stuff every single day. We try to solicit it as much as we can, but just talking one on one with people. And, also, like All night long. Talking one on one. There's a lot of devs who came from companies that are not allowed to talk about stuff that they work on.

And, like, they they gave us the scoop on some of that stuff, and it's always really interesting getting to to hear from these, like, huge companies that use this tech, but they're not allowed to to talk about it. Huge companies that we cannot name. Yeah. Yeah. Just fruit companies and stuff like that.

Oh, man.

Yes. I I it was it was great. So shout out to everybody who showed up to that. And then we also had a big, Sanity team meeting. We got the whole team here from all over the globe. We are a global team now. We We have a Canadian podcast with Oh, sure. Yes. Well, I thought it was a global team. You know, you always see the stuff like made in America with,

international components. Like, this is a Canadian podcast with international

Okay. Help. I I think only, what, a a very small percentage of the team is in Canada now. I don't know if we can continue to say that. But Doesn't matter. You would just declare it as, like, a It's like a grassroots. It began

in Canada mostly.

Just as much as the team lives in Colorado.

Colorado podcast. Yeah. Oh, alright. I'm here too, by the way. Hello?

CJ. What's up? CJ is joining us in the Bos at at GitHub View. JS our resident AI hater. Yeah.

And I'm going into this blind, so I did not watch the keynote. I'm just gonna be live reacting to what these guys tell me, and, I'll give you the the real

feedback about it, I guess. I don't know. Yeah. So, yeah, Wes and I will give you the, the Microsoft shell take, and

then CJ gives you the real deal. Leave leave your comments right now. Yeah. We hear you.

We're shills and everything like that. No. We're not this is not an ad. Scott getting paid for any of this.

We're simply just just checking it out and and reporting what's going on because I we know a lot of a lot of you guys use these tools.

Speaking of, Schilling, these GitHub badges are really sick. It's the coolest part of this this conference. Last year yeah. Last year, the badge had an e ink screen, and it you could hack it to put whatever you want. Yeah. This year, it's a it's a different level. I don't know. I'll I'll have to post pictures of this. I made a, a GoldenEye sixty four logo for syntax and put it on here. But there is a flappy bird. There is an Etch A Sketch. There is a Tamagotchi.

It is a whole last screen. It's a It's a Tamagotchi? I don't know.

So last year, it was a it was it was made by Raspberry Pi, but it was technically like an Arduino.

And I believe that is the same this year, but it also has a Wi Fi chip in it. So it basically, the whole badge is a printed circuit board that has a Wi Fi, chip in it. It's got a LiPo 3.7 volt battery, USB c to to plug in. And then the whole thing is running MicroPython, which is like like you you code these apps in Python. You can you can run any code you want on it, but, like, the the sort of the framework for building apps on this thing is preloaded, so you you write them with MicroPython. And absolutely

wild, that is a printed circuit board This is a badge. To work on it. Yes. Yeah. We're not clear. This is a conference badge. You know, the thing that's normally it's just some little plastic thinking.

My kids are gonna go absolutely nuts

playing flappy bird. I'm gonna I got an it just gets running on it. And, as soon as I can, I'm gonna hook it up to the Syntax API and, like, pull the latest episode or or something like that because now that it literally has Wi Fi on it. Like, previously, it was e ink. So you had to hook a battery up, and then once the e ink was set, you can unplug it, and it will just stay that way for forever.

But this is this is an actual full color display.

Brought in my GitHub contributions

Yeah. So I I haven't hooked mine up yet. Like, to connect it to the Wi Fi, you actually have to connect it to your computer and, like is it, like, modify a config file? Is that what it was? Or Yeah. You modify a config file. And then I I actually was messing with the gallery, and I was trying to install some other images. I had this really wonderful photo of Wes

with his long hair, that I was trying to get on my badge, but it it kept crashing the memory on it for some reason. I think it's this photo specifically.

Mhmm. That's his face. The badge was just like, I can't I can't let you do that. It's good. And

so I actually bricked mine. Not crashed it. I bricked it. You had to reflash the firmware? Or Well, what had happened is is that, like, I uploaded the Wi Fi credentials, and it wasn't working. So I was just, like, holding down random combinations of buttons, and I, like, totally bricked the thing to a point where it started running in, like, a bootloader mode. And, like, a bootloader mode on these these things is where you can change, like, the lower level software that it runs on, and I did something. So luckily,

they took it back and gave me another one. Oh, nice. Just, like, goofed it up pretty far. Can we just appreciate that out of all the types of people who would end up breaking their badge, Wes managed to probably be the first person, which is so endlessly predictable.

And I told the folks from GitHub, and they're like, good. Like Yeah. It's it's hacker mentality. You know? Dip into it. We're happy that you bricked your badge. Yeah. We're very happy about that. Yep. So So pretty pretty fun. May maybe are due for another. We did we did an episode on, like, like, electronics and and microcontrollers maybe, like, a year and a half ago. But

now that we have, like, this little thing, I think there's there's a an appetite for something else. I had a great time on this last night. In fact, I I didn't even, like, go to bed because I was, like, up in in the Python for this last night. Because you guys got yours early, so you've been able to to hack on it a little bit. Oh, yeah. Yeah. So tonight, CJ will stay up. Exactly. Year round That's my night. And be able to do it. Yeah. Cool.

Do we wanna get into the keynote now and talk a little bit about some of the announcements? Yeah. Yeah. So the the keynote at these things, as you could imagine, is always, you know, we're at GitHub universe. So at GitHub universe, you can imagine a keynote's going to be fancy new features in GitHub. There's also quite a bit about Versus Code as there was last year. Like, last year with with during the keynote, it was a lot of, like, yeah. Okay. Versus Node is starting to compete with Cursor. Like, are we even allowed to talk about Cursor kind of situation. Right? Where like, this year, it was definitely, like, a a a big message was features that exist already that are now being way more useful. So there's a a new center, mission control center for agents within GitHub, where, basically, you are able to control and send agents off working on problems within GitHub Yeah. In a more organized manner. So you could assign things even last year or half a year ago, whatever. You could have a a PR. You could assign it to Copilot.

Copilot could go off and work on it. It could do it in the background, and then it would come back with answers.

But now with this, with this new Mission Control, it's a lot more integrated where you can send a cloud agent to go and work on it.

That cloud agent can start to work on it. If you want to pick it up yourself, you can then have it open directly in your editor, continue working on it. You can use other agents in there. You can use Cloud Code. You can assign things now to Cloud Code. You could assign things to codex rather than just assigning it to Copilot.

How Yarn we feeling about that? Have you guys used assigning issues

to to Slightly. I've done I've done it like in a Copilot. In a GitHub issue. You can say, like, hey, Copilot. Check this out. Yeah. And then it goes off, and there's a link that will pull up, like, the in browser editor showing you what it's doing. So I I've done that a couple of times. I think the big thing that they're fixing here is that it just felt clunky

previously. So, like, if you wanna kick off an agent to to build a task, you have, like, a couple options. Right? You can use cloud code on your computer. You can throw cloud code, like, on a VM, but then it doesn't have access to all of your things.

You can kick it off on GitHub, but then, like, I found in that workflow, it's like, well, it didn't really do what I wanted. And now now I have to, like, sit here and wait for it and then go back and type on what I wanted. And it's like, well, I now I wanna edit some of the Node. So, like, now I gotta, like, check that out. And, like, now the seems like the flow of this seems to be a lot easier where, like, the the blur between it actually happening on GitHub and and happening in your editor is a lot better. So all of these agents run-in GitHub actions, and GitHub actions can run-in your own infrastructure, which is that's huge Yeah. For for people, they wanna bring their own infrastructure. You don't wanna either necessarily pay for that or there's, like, security concerns. You don't you can't run your own code on somebody else's servers for whatever reason. To me, that seems like kinda just, like, the biggest

feature here is Node you have a place to run your agents. You don't have to, like, set up a server. You don't have to, like, configure things manually. Yeah. Yeah. It's kind of just like a nice point and click way of having your agents running in the cloud in the background. I think the biggest

thing here was the fact that you can bring cloud Node. You can bring codex. You can bring Yeah. You bring your own agent. Because, like, I was watching this keynote, and I was like, this is awesome, but, like, what if we don't wanna use the the GitHub flavor of everything? You know? Is it is it gonna be their only their own thing? GitHub is just like, yeah. You do what you want. Like, GitHub is where we have all of our software, all of our our actions. It's where we build everything. And if when it comes to all this agentic stuff and it doesn't it's either, like, bolted on the side, you know, via some, like, plug in. But, like, no. This is, like, first class support for In the workforce.

Yeah. And and one thing they teased was that you can now if you have, like, a GitHub Copilot subscription, you can just log in to Node Yes. Which is OpenAI's coding agent. And, like, it just comes with your subscription Totally. To to have access. I don't know what the, like, gotchas are on that yet, but that's pretty sick. And I'm curious about that because I've had a Copilot TypeScript. Because I am a GitHub star, I get access to the Copilot stuff. Oh my god. Yes. I get loyalty over here. Yes. I and I I pay for it with my own money. I know. And and that is why I got the side of the the podcast booth all to myself because they said the star needs He's a star. Yes. K. Hold on. Can we pause a second there? Like, quick poll. How many of you got to meet Satya and Nadella today? CJ? I did not. No. I didn't I didn't know. Okay. There. Yes. Oh, yeah. I actually got to hang out with we'll we'll put the thing over top of the thing, but Wow. I gotta so Microsoft will, like, will email us with these, like, guests. They have, like, a PR company, and they'll email us with these guests. We're just like, no. We're not having, like, your, like, CSS suite whatever Yeah. Like, on here to bullshit about x, y, and z. Like, that's not interesting for the people that the actual developers who write code that are listening to this type of thing. So so, like, who can we get? I was like, how about Satya? And they're like, we're working on it. And I'm like, alright. Yeah. Right. Yeah. And then I got, like, a a weird message last night being like, hey. Come to ten p 10AM. Come to this location. Come to the pier. Yeah. Yeah. Wes can't. And Satya comes in and just pops out. And, man, that was that was really cool to to meet him. I gave him an Internet hat, which you can get in our swag store, and that was it was a cool experience. That's the Wes Node, though. Anytime they're like, can, can someone so come on and it's like, how about Zuck? Can we get Zuck? Like, like, what's he's always asking for? My goal is I wanna get Zuck, but, like, only ask him about, like, coding. Yeah. Yeah. I don't give a shit about it. Like, whatever your actual thoughts about React JS. Yeah. How do you feel about Next JS? Or just like, so Sanity was talking about how, like, he used to be a developer, and now, like like, the he still understands development, but it's like it's how you develop is is much different than Sanity did a long time ago. I was like, can we get him on a CSS battle? Oh. You know? Vibe off. Get a little Yeah. Get a vibe with the the copilot.

Me and Scott will do like, NCJ will do no AI, and we'll we'll go head to head. That'd be great. Yes. Let's make it happen. Yeah. But Anyways, you're a GitHub star? Yes. I am. And and, because of that,

I don't even know what I was talking about. We're talking about the free, codecs access. I've been using the Copilot stuff. You can have access to agents or not agents. You can have access to any of the models with, like I could have Claude, Sonnet, whatever Yep. Via Copilot, not via a Claude subscription.

And you could use Copilot CLI instead of Sure. Cloud Code. Right? But I could also in OpenCode

or anywhere else, I'm signing in with Copilot and then having access to the models. But my understanding of that is that the context windows are all shrunk Okay. On that via Copilot.

Okay. So that's what I'm curious about with, Node.

If you're signing in with codex, is it is it the same as the good? Is it is it the Or is it the Walmart version? Is it the whole hog? Yeah. Yeah. That's fair. Yeah. I guess it took to get the skeptics' take here, like, I'm looking at their blog post on, Agent HQ, they're calling it, and there is a box for third party agents. So it would seem that if the third Yarn you have, like, direct third party integration, third party access, you would get the full version of Claude or or whatever else. It kind of I mean, I don't know the details, but it would seem like you would need a a subscription for each of those to kind of, like, set them up maybe. But I don't know. Skeptics take, like, this is, it's cool. I I think, honestly, one of the things that burned me out about AI was I was trying to build a an agent dashboard. Yes. I Vercel that. And, like, I was coding it up, but I kept running into so many issues. And to have a nice polished product and that uses your same subscription and supports all the stuff you like, it's decent. I'm I'm not I mean, I I wanna see it. I wanna try it out. But Yeah. It it looks cool. It looks cool. Yeah. You know, if it for me too, there's you end up using this stuff and you you go so far in one direction of like, okay. Now I'm managing

Node I'm managing context. I'm a context engineer. Okay. Now I'm getting into I've hit these issues with agents. I need to be more deterministic. I'm getting into more deterministic workflows and tying in MCP servers with code rather than just, like, constantly LLM stuff. And you you just end up going further and further down this road just to get something that plays nice a little bit. And one thing that I I found to be absolutely fascinating with any of this stuff is when CJ released his AI coding rant, the comments, you can tell where people are in that exact same journey based on the comment they leave. Because it's like I almost wanna be like Just wait. Just wait, like, a couple weeks until you hit this specific issue, which you will, and then you're gonna use this to solve it. And then you're gonna go down this path. And then you're gonna go down this path. And it's almost like pulling that that one more prompt lever, just in a different way of being like, yeah. Okay. Maybe this next one is gonna actually solve all the Yeah. The issues here. But, no. These tools are are are neat. And you know what? As somebody who who did like to use the Copilot, assigning it to Copilot, especially for shit I didn't wanna do, like, CI stuff. Oh, I wanna set up a change sets and, like, release workflow with change logs. And I, honestly, I got better stuff to do in my time than just do that. So, like, telling Copilot, hey. Just go knock that out for me, and having it do that, was really nice. But then there's other times when I'd say, hey. Fix this bug, and

it takes a long time. The feedback loop is really long. That's that's the biggest one for me. It's like the feedback loop that group bugs. Long. And then you need to, like

I need to hop it out of the agent ESLint your editor. If it fails, you're just like, well, I suppose I'm just gonna close this issue and then just do it myself now. Yeah. Yeah. So that's that's something I'm really curious about because it was an impressive demo to be like, alright. Let's hop into our editor Node. Because, again, like, sometimes you just want the AI to get started. Yeah. Sometimes you just warp to do something and, fix a bug or whatever and then, you know, move. I can do it. And Yeah. That's really hard with the the previous, current one. And if you want to see all of the errors in your application, you'll want to check out Sanity at century.i0/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 century.i0/syntax.

Again, we've been using this tool for a long time, and it totally rules. Alright.

I think that nobody has figured out the workflow to that yet. Yeah. And, like, that's what a lot of people are saying. This is the this is the new workflow. Like, will this be the workflow of, like, you you kick it off? And, like, there's also, like, you can have multiple custom agents, like, one that's really good at, like, Kubernetes, one that's really good at test driven development.

That to me has been effective. I I do have agents. I have a Svelte Pro agent, and that that's good for Svelte specifically because the API changes. So having an agent that says, validate specifically with Svelte MCP Yeah. Use this specific instructions or use this, that has been way more effective than just yellowing Yeah. Props. Do you have a custom agent instead of an MCP server? I have a custom agent that uses the MCP server to do various things. But the agent codes, and then it it validates the code with the MCP server or it looks up docs. Yeah. Okay. So it's like specific instructions for how to use the MCP server that doesn't load the context because that one agent has it? When to use, yeah, when to use the MCP server, when to yes. Yeah. Cool. And that that agent is good at doing

certain types of work? Yeah. Specifically, Svelte UI work. Yeah. Okay. Yeah. That makes more that makes a lot of sense because, like, especially if you're in, like, an app that has, like, back end and front end and TDD Yeah. And

those might need to be different. And then you move it out of custom instructions because then I, like, I can tell it these are the like, maybe Scott, like, these are the general things that I'm I'm using, but these are the syntaxes that I would prefer to have or the do not ever write my CSS. And if you do and, like, just delete yourself from my computer.

Yeah. Yeah. I know. You Yarn not good at this.

What else? We got here. Plan mode. This is something that Kiro launched. When did you do your video on Kiro? No. Plan mode is more like

Like Claude plan mode? Node is more like Claude plan mode, the Wes than Kiro. So it's not it's not specs. It's just plans? Yeah. Okay. Okay. It's not spec driven development. Okay. Yes. Because when I saw that, the first thing I thought of and I was gonna tweet, oh, this this Curo. Yeah. But it's not because they they actually did add, like, to dos in Versus Node. But I found that Node offense to the Versus Code team because I know that that was, like, a much wanted feature. I have found that those to be largely just decoration and kind of useless. Where in, it's more like, here's the pnpm. Here's the steps. Let's dial in on this one thing, and we can tackle this as a thing. But this plan mode that they announced is not that. This plan mode is definitely like a going back and forth with the agent before you begin any work Okay. In which can be, in my mind, the most effective way to work because you can get a lot of these issues worked out ahead of time that it might just start going off on the wrong path. What kinds of stuff? Like like tech choices or what? Yeah. For instance, when I was I was working on a an analytics thing for us, and I have all the CSV data. And it was like, for me, that's like a a an interesting way to work with AI because I personally like, taking in CSV data like, I can give it the the CSV data structure and say, just build me, like, a parse and a database that fits into this structure, and we can, you know, scoop this all up with papa parse or whatever that, CSV, is. And I wanna use temporal for this. And it came back and said, okay. Here's what we're gonna do. We're gonna use this temporal polyfill. And that's I know I know the temporal polyfills. There's multiple. Yeah. Like, that's the wrong one. So I can go back and forth and be like,

you're using the old Okay. You're using the old polyfill. Yeah. Rather than, like, doing it After it's already implemented. And trying to have to rip it out and Right. And use, like, an old version or, like Yes. Old version of Zod. Like, what are the other ones that happen? Oh, yeah. It's Tailwind three. It always uses stuff before. Using Npm instead of PNPM. Yeah. So, like Bro, you know what I'm using. Like, you do see an NPM lock file in there? You can see the PNPM lock. You can see it. Yeah. But I I got to the point where I wasn't coding anything without a plan. Even if, like so I was even if I was using Versus Node that didn't have plan mode, I would prompt it to create plan dot md.

So now that it's integrated, that's that's pretty sweet. But they are, like, really late to the game because Really late? Like, very late. Because because Cursor has had it, and then Wes, I mean, Claude, obviously, first, and then Cursor added it. They added their to dos, not the greatest. I've had issues with to dos inside of Cursor. Like, it forgets that the to dos are even there. Has to dos too? Yeah. Okay. Yeah. I feel like Hero JS the only one who's figured out

to dos, but it's Yeah. It's like a whole ass thing that you're agreeing to. It's not just to dos. It's the whole spectrum of an effort, and that's, like, a that's a a different box that you're opening. But you are right. Everybody else and their grandmother had a plan mode before this. Yeah. But that said, I do use it. It's one of the things I use constantly in cloud code. So yeah. Here's a question.

Chris rolled this out a couple months ago. Now they have is is being able to fire off an agent from Slack? Mhmm. Yeah. I don't get that. JS that useful? Not for me. I don't give a shit about that. That to me is, like, the lowest totem pole for me out of there. Just like, or you're talking back and forth in Slack about a feature, and then you just you

at Copilot and say, go go build this thing. I I think that is useful to some people, and I think it's very useful to some people.

But for me personally,

I'm never ever gonna I'm never even gonna It seems like if you're gonna fix something or or do some sort of feature, there should be a, like, a little barrier, like,

clicking a button. For for me, it's like, yeah. Yeah. If I'm gonna do that type of flow Yeah. I'm gonna go to a GitHub issue. Okay. That's a good place to start. Yeah. Or even, like, a linear task even though we don't use linear. But I would go to something like that long before I would ever go to Slack, which Right. Yeah. I completely agree. I think, like yeah. So you go where your where the work is happening. So in GitHub Yeah. Or in your your, planning tool or Kanban board. Because, I mean, like, Slack, sure, it would have the context of the conversation, but that likely needs to be a little bit more formalized before you send an agent off to start working on it. So I don't know. Then it's not useful for me. Yep. Maybe

like, I I can imagine, like, if something were to roll in in one of your Slacks, you know, you're monitoring something. Yeah. And it comes in Yeah. And it it's auto. I just don't use Slack like that. I use Me neither.

GitHub for for a lot of that. And Sentry.

I use Sentry @sentry.io.

I see code, Sanity Street for two months for free. Yes. I use I yeah. That comes in. And, seriously, I mean, it does, though. And I I I get my errors in there, and I I get logs? I get my logs. I I click the little buttons, and then and it tells me how to fix my problems, and I do. And that to me seems more like what I what I would use that for, like, you know, where the issue is happening, where where the code is. Here's, another feature I'm curious

what and I think a lot of people are gonna hate is they have a Copilot metrics dashboard Yeah. For so if you have an organization, say you have a thousand developers, there's now a dashboard to see, who's using it in error or maybe who's using it or, like, how how many people are using it. Yeah. And, like, I have heard from so many people in the last three months of, like, I have a a manager that is so heavy handed AI Yeah. That said, like, you should not be writing a line of Node code, like like, that far Wow. Pilled. And now they got Isn't it weird how it's always managers who aren't pushing that? Like Yeah. Yeah. It's not. Yeah. And as as as much as we love this stuff, I don't think that that's the the move.

But I I think people are are curious to see, like, oh, we're spending all of this money on a on a subscription. This is more of, like, a corporate enterprise feature. They wanna be able to manage their spend and see how much people are using it. Yeah. I think it's I think it's ESLint gonna have to snitch on people not using it, though? I think it is. I'm looking at the screenshot here. It's got agent adoption. So the the screenshot says 2,400

of 3,000 active users.

And so I I I've talked to people where, like, part of their development plan and part of their promotion plan is how much AI are you using. Man. Like, they have a quota for, like, they have to be using, like, 90% of their code pushed with AI or, like so, yes, they're definitely gonna use it to call people out. CJ, I'm getting a little concerned. I've noticed that your AI usage is hovering around five panda this month. Are you alright? I'm gonna write an agent to pretend to use it's like a mouse jiggler for anything else. And I've I've I've I've built I have built I have built multiple mouse jigglers, like like work dot j s. Fire it off. It just spins the mouse, and then yeah. So That is very funny.

Yeah. You could just have a a a trash repo that is just constantly pushing Spinning. Yeah. CJ,

your AI score has improved by 95. Wow. Yeah. Yeah. I'm loving it. I'm just so much AI. AI is so great. You could build, like, a, like, an MCP that just, like, retypes all of the code that you did by hand. Yeah. It's like a constant feedback loop. Yeah. Like yeah. Alright. That's gonna be a thing in Ohio.

Jiggler JS or something. Yeah. Like a paid service to keep your AI usage up for sure.

Syntax, we we patent that. That's ours. Don't touch it. Don't take it. Don't take it.

You know, the other thing they've they announced was, effortless MCP integration. This is actually something that had been inside of, Versus Node already. So this is a Versus Code feature, being able to install MCP servers, from the extensions market.

It's it's cool. I, like, I when I one of the issues I also had with trying to work with AI is finding decent MCP servers. And, like, all the directory websites, so many times, the MCP servers listed were just, like, spam. Yeah. So Yeah. If this is, like, officially sanctioned or you can see the number of downloads, they also potentially like, with Versus Node extensions, there's, like, a publisher name. Yeah. So you could be more sure that the MCP server you're installing is more legit. I I like that. I I think it has to happen that somebody

needs to be able to, like as much as we hate, like, a, like, a a governing hand, is that, like, if one of these MCP servers goes rogue Mhmm. That somebody needs to be able to pull the plug on it. And, like, Chrome does that for extensions. Right. Versus Code does a good job of that with their Versus Scott. In fact, I met a guy at the meetup yesterday who forked my Cobalt two theme, and he called it Cobalt three. And he's he said he got he's like, I got, like, 3,000,000 downloads. Like, it got really popular.

And then he Scott an email the other day. Like, they pulled it. Oh. Because they said it was too close to my I didn't I didn't complain or anything like that. Well, you got forked, and, they pulled it. And it's so funny because I was like, yeah. It kinda was cheesy when I see, like, people would, like, fork it and make cobalt two better. Yeah. Because you can you don't need to fork a theme to change it. You just you put your chain your own personal changes on top of it. But then I realized, like, it's called Cobalt two because I've I forked Cobalt. Cobalt one. Yeah. Yeah.

The original Node.

So

yeah. That's allowed. So I I think that that that is fine. Hopefully, they add integrations for more stuff. Right now, it's just, like, it's just Versus Node. But, like, I wanna be able to click it, and it's installed in, like, cloud chat or Yeah. Obviously, cursor, but I don't know if they'll ever

yeah. Hey. You know what? MCP servers were one of those things that I felt like a little bit of, okay. Now I gotta install it these ways or do all of this stuff. And for some, you just get used to it, and then it's fine. So I don't know. I used to want a UI for this, and now I maybe don't care as much.

I would love if they were to add my CSS MCP to this because that's a yeah. No. I think discoverability is a a big flaw. It's a discoverability. Yeah. Absolutely. I'm talking more about, like, the install management process. The Century MCP server in here, top tier MCP server right there. Yeah. Century mentioned on stage a couple of times. That was pretty sick. Yeah. The Century stuff was was up right front with all of it, which JS really cool to see.

Yeah. It's so funny working for a a company now and being, like ESLint, like, pride in that. Man. Yeah. That's my boy. That's like that's like, hell, yeah. Yeah. I think three years ago, I would have been like, oh, okay. Cool. That's my seer. Yeah. Fixing the bugs. Yeah. So all in all, announcements, you know, I feel like these are all good things. They're all Yeah. I didn't feel personally, like, blown away by anything, but I do I I do appreciate everything they added, I would say. I think we're past the the the place in AI now where there's, like, this,

like, jaw dropping model or this amazing tool Yeah. That does that. And it's it's all just about, like, how do we fit this in our workflow? Yeah. How is it getting faster? Is the DX is really good? And then, of course, like, all the the enterprise tools of, like, I have 5,000 developers. How do we roll this out

to to so that everyone can use it efficiently? How do we make sure that they're using AI as much as we would like them to? Exactly. Yes. Right. Yeah. So Scott lot of interesting stuff, but I think we kind of hinted at it. It's it's honestly just it feels boring. It feels like it's like it's nothing new. It's stuff that other people have already Deno, not that innovative.

So AI skeptic take,

it's fine. It's getting better. And if and if you're already using Versus Code, great, because you have a lot more features now than we have in all these other tools. But, otherwise, yeah, it's fine. That that's AI skeptic take. It's fine. And now it's time for the AI skeptic. Skeptic. Yeah. Yes. I'm I'm pretty excited about it because, like Okay. Like, as much as I love and, like, I'm I'll say this as, like, a primarily cursor user in the last probably eight months, the software dev still happens on GitHub. You know? And I'm I'm cheering for GitHub because I want like, GitHub is an awesome place. And Because you want Satya on the podcast. Yeah. No. Yeah. No. I guess. I I will kiss no asses except for Satya. Yeah. But the fact that the software dev happens on GitHub and Yeah. These tools are going to need to be integrated into GitHub at some point. And the fact that this is happening and we're we're we're working on workflows, I think, is is overall good.

So stoked about it. So, yeah, I I would say my thoughts are are somewhat similar to both of yours even though your thoughts were opposing.

I I do feel like Right in the middle. Yeah. You're playing both sides, the sunny mean right now. I know. Exactly.

No. I I agree with you, Wes, and, like, GitHub is where the stuff happens, and GitHub is still just always innovating.

Right? GitHub could have easily become Bitbucket and just, like, been someplace, you stash your Node, and GitHub has never been that. They've always been pushing it. Bitbucket. I wonder if they've even added labels yet. Do do you remember? There Wes, like, a thing there was, like, an issue on Bitbucket for, like, ten years. Like, can you add labels? Like, like, it it could have easily turned into something like that. Yeah. But instead, they've always been bringing new stuff. And so for me, I I I like US. I I am rooting for it because I have such a fondness for GitHub overall and GitHub proper. I I think the the the stuff that they are adding are things that needed to be here.

There was nothing in this announcement that shot my socks across the room, but in the same regard, I'm gonna use all this stuff. Yeah. So, yeah, I'm I'm, I'm I'm happy. Simultaneously, nothing crazy.

Happy that it's here. I hope that, like, what GitHub did for software development over the last fifteen years Yep. Is also what they do for AI development. Yeah. I don't know if that is true Node that they're a mega corporation owned by Microsoft, but I hope.

Yeah. And it's like an institution, and they've done so much good stuff. And that man, I love the improvements that GitHub brings all the time. So and they just hired

Jared Palmer who, we've had him on the podcast in the past. We've, he JS the guy who created Formic, and then he created turbo Repo.

And then he created v zero at Vercel, if you heard of it. And then he recently just joined Microsoft. And he's just been, like, just been on on Twitter being like, hey. What can we fix about GitHub? People have been, like, whining about laggy diffs and, like like, performance issues on GitHub and all of these things. And it's gotten even worse as I'm sure a lot of their end has been pulled off to work on AI stuff. And he's like, he seems to be fixing a lot of it, and he gives a shit about performance, obviously. Yeah. So Yeah. No. No. I see that. I love it when a talented hire gets brought in anywhere. Yeah. Shake it up. Yep. Sanity. How what's the ETA between, when do you think GitHub's gonna add the what will you build today,

search box on there?

Wes will github.com be a a vibe coding Yeah. Platform? Yeah.

Yeah. Yeah. What will you build today? No. I I'm stoked to give a lot of this stuff a try. So, shout out to GitHub team for constantly shipping and,

yeah. Alright. Thanks, Eric, for tuning in. Thanks, everybody, who came out to the meetup.