GitHub Copilot App Launch - Rubber Duck Takeover!

Hello everybody and welcome Welcome to a special edition of Rubber Duck Thursdays. In case you haven't been here before, this is our weekly stream where we talk about code. We talk about what you're working on, what we're working on, what's new at GitHub, and more. But this edition is very specifically about our brand new GitHub co-pilot app. And it's not just the Cassidy show here. We have some special guests that will be here today. And so, in case you don't know who I am, that's cool. My name is Cassidy. I'm on the developer advocacy team here at GitHub. I've got this really cool trophy I wanted to show you. At first, look at that. It's an octacat. It's a little bit cursed, but I'm obsessed with it. I got it at Microsoft Build a few weeks ago. Anyway, we've got all kinds of props. We got all kinds of things. We got all kinds of releases. And now we got all kinds of people to bring on. And so, first I will introduce Burke. And then I will introduce Pierce. And then I will introduce Enrique. Hello everybody and welcome to Rubber Duck Thursday. Hello. I'm excited to be here. Hey. Hello. Wow, what an intro. That was awesome. That was pretty. And I liked how you literally like had us come in right as you said our name. That was some prolevel producing right there. Yeah. Just know that I'm actively clicking buttons while I do this. Really trying to make it look smooth. Um, show show the award again. Can you Yeah, look at this. Aley Willis on our team at GitHub. She 3D printed this. It's It's almost creepy, but it's It's also kind of fun. I I think it's very fun. My toddler is very confused by it. She She literally looked at it. She's three and was like, "Is that an octo cat?" And I was like, "Yeah." And she said, "It's so shiny." That's all I got. It's an Oscar, right? It's supposed to be like an Oscar. I think so. Yeah. It says best vibes because I got it after a vibe coding thing at Microsoft Build. Nice. It's pretty fun. Yeah. Um, we should talk about the app, y'all. Um, could you all introduce yourselves and talk about why you care about the app? Yes, I'll start. So, hey chat, what's up? It's good to be with you. My name is Burke and um, usually I'm over on the VS Code chat or the VS Code live stream, which happened for a while. But today we're going to be talking about the GitHub Copilot app, which Pice is about to tell you all about and why we're doing that today. What is it, Pierce? Why are we doing it? Why are we doing it? Um, hey, I'm Pierce. I am uh the product lead for VS Code and other GitHub co-pilot things uh uh over at GitHub and Microsoft. I just do things here. Burke asked me at Build, "What do you do here?" And I was like, that to you? Yeah. Uh we kicked off like our live stream at Build and you were like, "So, what do you do here? Questioning your job. I was like, I do things. I think is was my response. Uh it doesn't sound like something I would do. I'm just maybe we just blacked out because we we went live and then we were just like, you know, on camera and and weren't thinking things through. But anyways, it's kind of fair. It's like right now, everybody. Yeah. Right. This is what happens, chat. You go live and you just think, can I get through the next hour and a half without getting fired? Let's see. We'll do do our best. Yeah. Yeah. So anyways, I guess like um the longer story is um like when I started working in AI, we had no agents, right? That was 2024. I think we had co-pilot edits, we had ghost text, we didn't even have next nextedit suggestions yet. And so um that was kind of a weird world. And then we got agents and I think the models we had at that time were like GBD41, you know, poor one out for GBD41. You know, you served us well. Um but we have this game track. Yeah, we have this metric we track called like retain code from agent and it's basically like a measure of how much people are trusting the agent and m what percentage of the code generated by the agent makes its way into a commit and so for GBD41 that was like 50%. which is still amazing like it was 0% before right like and then 50% of my code and then like over the last year right like the models got better and better and better and now with the latest opus and GBD models we're like over 90 almost 95% of code being committed from the agent and so if that's the case like also like how we partner with these tools change right I remember like when agents first came out I was staring like at this at the chat I don't know about you guys I was staring at the chat like what is every single little thing this is doing. I need to approve everything. I need to review every single diff that this thing puts out. And that was how I partnered with agents when they first came out because the models were still not amazing, right? But as the model capability increased, like we also like now trust these things more, right? I think most of us are like kind of just go do the thing like maybe we do a plan or something like that, right? But then we fire it off goes and does the thing, right? And then once you're like I don't even need to look at this thing anymore, then you start getting tempted well how do I run multiple things, right? So that becomes the new temptation. But then once you do that, you're like, "Oh man, my head is kind of spinning." Because now I'm doing like five things at once and I'm shipping, you know, I'm writing code very fast, but then you have other problems, right? Like you have to constantly decide like what am I going to pick up next? Like before we would work on one task at a time as a developer because that's all our brains could handle, right? And now I have to constantly decide what's next. So that's like another problem that emerged. And then like also okay sure like you have a coding agent session that produced some code you have to actually land that in the codebase right and so like uh kind of as nature of like how our partnerships with AI changed over the last year or so uh with agents like we felt like we needed a new tool to to kind of solve those problems and so enter the GitHub copilot app. So that's what we're here to talk about today. So, that's we're gonna do that for the next hour and a half, folks. And before we get to the chat here, uh, we got one more person. We got Enrique. Enrique, who the heck are you? Yeah, who are you? Hello, folks. Yeah, who the heck am I? Uh, I'm a developer in the GitHub app team. So, that's why I'm like the new kid today, you know, like, hey, I'm a developer. Give me like five minutes to talk about something that's not code. Uh, yeah. So, I work with mainly with peers on this. been working on the app for the first sorry for the last couple of months I would say. Really excited to show you some stuff that we're working on and really excited to you know to work on the app and and you know build some features that you'll get to enjoy. I hope. Awesome. Well, thanks for being here. So, let's do this. Cassidy, I think we can let you we'll take over the stream and uh hang out. Yeah. No, I'll be here. I got to drop I got to drop all my commentary on all of these things. I got opinions to share because I think what you were saying, Pierce, is so true in that our AI use has changed so much even in the past six months and and how how we navigate software development. I think software developers are here to stay, but our work is fundamentally changing and it's really interesting to see this next step. So, I'm going to switch to PICE's screen and let's let's hear it. So, I guess first like I'm going to show you this app. This is this is the un unveil unreal unveil. What am I trying to say? Un the unveiling of this app on the stream. Um first time it's ever been featured here, I think. Right, Cassidy? Um, so I'll kind of start by giving like a high level tour of this app, but I'll I'll start by saying like if you don't already have the app, uh, just go to gh.ioapp, you can probably add that as a banner on the bottom. Uh, go download it. If you have a paid GitHub copilot subscription, whether that's, you know, pro, pro plus, max, business, enterprise, you have access to this app. Um, and if you're already using things like the CLI, your sessions will automatically show in this app as well, so you can jump back and forth between the two. So, go download it, try it out, and I'll give you a quick tour. If you download it, you can start playing around with some of this stuff with me. Um, so kind of at a high level, like we'll we'll do a little bit of a tour, and then I want to show you like what does a day look like for me in this app. Um, so, uh, we have a home screen here. This is just kind of my my, you know, home base for kicking off any prompt that I want. So, I can come over here. You know, I have kind of typical model picker things. So, I can select what mode I want to kick things off on. So, we have plan interactive for when I want a more synchronous partnership with the model or autopilot for when I feel confident about the plan I built and I just want the the model to go do the thing. Uh we have model picker. Uh so, just as of today, um we've started rolling out uh the MAI code one flash model to the app. So if you're an individual subscriber to GitHub copilot, you should start seeing these things show up in GitHub copilot CLI and the app. And then of course I can control reasoning effort and things like that as well. Um and then interestingly like the cool thing about the app as you're already probably seeing in the lefth hand side here is I have a bunch of projects and these projects can be um you know remote GitHub repositories. They could be another arbitrary remote such as an Azure DevOps repo. They could be a git repo that I've cloned locally on my machine. They could be a folder even. It doesn't even have to be a git repo, but these are essentially all the projects that I have here. And we'll jump into those in a second. But essentially from this drop down on the home screen, I can pick, you know, the different uh repos that I I've started. I I've cloned on the machine here and kick off tasks in them. Um so like I can do that from the home screen. I also have uh this option to create things in a new work tree, local repo or cloud. So what do each of these options mean? So for new work tree, if you're firing off multiple tasks in the same repository at the same time, you probably don't want those agents to collide with each other. And so what this work tree option does is it basically creates an isolated copy of that repo from whatever branch you select, in this case main over here, but I could pick any branch. Um, and that makes it so that I could run multiple tasks at once without worry that they're going to interfere. If you don't want that behavior, you can just pick local repository. And then Enrique is going to show us some cool stuff we can do with cloud later where the agent loop is actually not running locally on my computer but in a cloud sandbox. Um so that's the basic thing. Um we also have my work over here. So like I was saying earlier I feel like there's a lot of kind of session managers in market right now where you can kick off tasks and run multiple things in parallel. But one cool thing about the GitHub copilot app is it's deeply grounded in my GitHub context. And so my work is is where I'll generally start my day is jump in, see what issues I'm assigned. You can see you can go in here and actually create your own views for what you want to see. This is Pierce. This is all of my assigned issues and things like that. There's also a GitHub app uh thing that I've created here. There's other pre-built filters as well. And so I come in here and like this is where I might do an initial triage. So I can jump into some of these issues. So I could say like okay, click on this and I can kick off a session directly from here. So I could I could go through this issue. I could click new session. that's going to go and create a new session and whatever repo that is, in this case the VS Code repo. So directly from kind of this triage experience, I can go kick off sessions. Um, we also have automations here. So I'll go deeper on these in a second, but these are essentially uh different ways for me to automate the repeatable toil that exists in my day. So a couple of the ones I have here, um, so I have a triage one. Uh so that one is basically going through and triaging top issues, hot issues on the GitHub app repo. I have some for even things like telemetry analysis. So you can see I have one here. Let's see. We have my turn analysis. I have one on onboarding analysis and I have a business report with like our KPIs I generate. Obviously not going to click into those now. Um I have a today one that basically helps me to prep for my day. It looks at my meetings uh via work IQ. uh it looks at assigned GitHub issues I have and basically helps me to prepare like with all of the inbound I have in messages and issues and elsewhere. What are the things I actually need to focus on today? So I have an automation for that. Um and then I also have some for like other things like uh triaging our enterprise feedback from our account team. So I have a ton of automations that I've set up and after I go through my work and my assigned issues and especially anything that's new from like the last 24 hours, I generally jump over into these automations and review what's going on in each of these. And of course I can create um I can create this automation and it could run locally uh or it could run in the cloud which we'll show later. And I just basically add a prompt. So all of these things are prompts. They have access to MCPs. So for example the telemetry one is using the Azure MCP and and executing queries and uh Azure data explorer. So any any prompt that you can submit with the tools and skills you have with within whatever project context you want that can now be an automation which is super cool. Okay, so let's actually jump into some sessions. So like I said over here I can come in come in I can clone kind of any GitHub repo I want any uh repository Earl even if that's not a GitHub repository or I can add a local folder. We also have this quick chats thing. So if I want something that's not specifically scoped to um to like a project then I can go kick that off. So like here's an example of one I kicked off earlier. I have a presentation to our our sales team at GitHub on like what is the app, why does it matter, what are core functionality and so I mentioned I use this app for literally everything like not just coding. I already showed you some of my triage and uh telemetry analysis workflows but I also have workflows for doing things like uh creating powerpoints and stuff like that. So here I'm actually literally creating a PowerPoint um based off the GitHub copilot app repo um and also the documentation and marketing pages we have on github.com. So I do this sort of thing all the time in quick chats. Like if you just want to you know do like a very basic I want to ask a question type of thing and you don't care about it being scoped to a repo, you don't need isolation, then that's totally fine to kick off in this quick chats experience. But let's jump into the GitHub app. Uh and so I'll kind of show you like what my flow would look like. So earlier I asked what are the top five issues that surfaced yesterday as part of the GitHub app launch. Um you know pretty typical thing. Um I could have done this from automations or my work. Uh you actually can have an automation that will create a session in uh in one of these repositories. So like if I wanted to just have an automation that basically did this automatically I could. Um, but it's pretty common like, okay, I'm investigating multiple things. And I think we all have this like collective exhaustion around kicking off chats, right? Like I don't want to manage all of these chats. Sure, I'm doing more work, but like our brains can only handle so much. And so, one really, really cool thing about the GitHub Copilot app is I can use one session to drive five other sessions, right? And I can stay high level in my partnership with the AI. So, let's go ahead and do that. Hey, uh, can you kick off five different sessions in the app for each of these issues in plan mode using GP 5.5 in high reasoning effort? So, we'll go ahead and kick this off. And you you can see we also support voice mode. That's what I just fired off there. Um, so if you uh go to the settings in the app here and then you select voice mode, uh, you can go and configure that, download a local model. None of that leaves your machine, your voice or anything. is all happening locally and then it's just option uh spacebar on Mac to actually dictate but of course works on any OS. So what are we doing here? So look at this. We just saw five sessions get created from the app. So the app is now driving the app, right? So each of these things have been kicked off. Let's jump into one. So it looks like CLI parody is is top of mind. So you can see it's it's getting kicked off now. Um we are in plan mode. It just switched over. we are using GBD5.5 and we are in high reasoning effort and so I can basically come back to this thread and I can say okay like those things are getting kicked off you can see they're running over here and because we're using git work trees each of these are happening in their own isolated context now I just kind of want to like stay high level so I can say hey it looks like those things got kicked off but I actually want you to report back to me progress on these things as they move forward in particular when the plan is actually ready for my review can you let me know uh so that I can jump over and review the plans that each of these sessions have generated. And so, not only can the app kick off sessions, but it can also uh pull these sessions and monitor other sessions for me. And so, you can see we kind of have like a nested tree thing here. But say I don't want all that noise. I'm just going to like unexpand those things and I'll just stay in this thread. And there are notifications and little sounds that you get when sessions are complete. And so like if I wanted to go do something else, say I have a meeting or something like that, I can jump over and there will be a little notification sound when one of these sessions completes and I can just watch this chat, right? I don't have to go watch the five other chats and that's super cool. So then like you know let's let's jump over to something where I've actually written some code. I wanted to add like a fun little Easter egg to the app. So uh in this case like I went and just very basic prompt for demonstration purposes. it it created some code. And I think like one cool thing about the app is I like to say that one of the things that's changed with my partnership with AI is I typically actually don't review the disc first. I would say I'm more outcome focused in how I partner with the AI. And what I mean by that is like not that I don't look at the code, of course I I still look at the code, but it's not my primary review artifact. Typically I want to know did you do the thing? So uh inside the app we have a one-click run experience. Um, so you can actually just run the app. If you configured run scripts, that should just work. And if you have something like the browser, let's ship over to my coloring book app. Um, and run that. That should, you can see it it booted the terminal. We're compiling my thing. And here is my coloring book app. And so what I mean by like I can stay high level in my partnership is I can come over here and like I'm actually running the app. Did you do the thing? And like say I want to inspect different things. I can use pick and polish and I can come in and say like uh why does this say 2024 when it's 2026 and so uh like this is what I mean by this outcome focused thing I'm giving feedback on the actual outcome of the session and not so much on the code so that's like typically what I do first but jumping back over to the Easter egg say I do want to actually give some code review comments um I can jump in here and I can like just like commenting on a word doc I can click into this diff and I can give feedback back to co-pilot. Um, so I can say like I don't think this test is measuring all the right things including Perf. Can we fix that and I can send that to Copilot and that will actually go start working on my on my comment. So I can kind of comment on the diffs exactly like I would in a word doc. So when I am ready to comment on the code I can do that as well. And of course, if I really want like to to go through all of the code, I can do that by opening in my editor ID of choice like VS Code with a one-click button that will actually open VS Code with this session and it will show in this Oh, maybe I should just do it. It' be a fun demo if I just did it. So, let's do that. We're booting up VS Code. It's on my other monitor. Pull that over. And so the interesting thing is we just opened up the GitHub app on this uh on this branch and you can see if I scroll up I actually get chat continuity as well. So you can see here like I have add a fun Easter egg to the app and all the stuff that happened. So my chats from the app also flow through to me inside of VS Code. So all these tools work super great together. So if you're familiar with CLI your session automatically I can continue in VS Code, my session continues there as well. Okay, so I've given kind of some uh some review of this code. I've given a review of the outcome. What's next? So I kind of mentioned this earlier, but uh I'm sure Enrique is is super pleased to have PMs contributing to his codebase. Um and and one problem with AI is it encourages you to start a lot of work, but like finishing it, like sure, you can add PRs, but like even before AI, PR review was a bottleneck for so many teams, right? And now it's way worse because we're all doing more and you have people like me who are not even engineers on the team contributing to the codebase. Um, and so we have more PRs than ever. So how do we manage this? Like how do we how do we deal with like all the issues that come from actually being successful with AI? So in the app, uh, because it's deeply grounded in GitHub context, you can see here I have my PR open. I just kind of created another session where we had this for demonstration purposes. And I can jump in here and see, okay, cool. We got some GitHub actions. Looks like we have some performance things to investigate. And the cool thing is like I can actually go into each of these comments and I could individually ask co-pilot to go fix it. So if there's one that I'm like I really want to make sure this is fixed, I can come in, I can fix it. Looks like all of our CI pass, but if we had CI failures, there'd be a button right here saying, hey, we have a CI failure. Do you want to fix that? But then you kind of ask yourself, you're like, well, like if I'm having to just basically go and click buttons and say, hey, the CI failed, or hey, like can you make sure you address the code review comments? Why do I have to do that? like that becomes a new source of something I have to babysit, right? And so one really cool feature in this app is something called agent merge. So what is agent merge? So it will basically constantly pull this PR, check the code review comments, check for CI failures, and check for any blocking actions and proactively address those things for me. And so certainly there's some PRs where you may not want to enable this, but I would say generally my confidence with agent merge is very, very, very high. Um, I've seen it push back on code review comments from both humans and copilot where uh I I don't think the comment made sense. So, it won't just like blindly follow any, you know, code review comment it has. It will push back if it doesn't think it makes sense. It will go and look at CI failures. Like it could be, hey, we just have flaky CI and we just got to bump it again. It could be there's a real issue and it could actually go address this, right? Um, so I really love enabling this. So, I just enable it. Now, agent merge is on. It's just going to keep doing the thing, right? and it's going to keep pulling this PR until it actually gets merged. In the case of this repo, I'll need a human reviewer to actually, you know, give me the final thumbs up. But this will go and address some of these code review comments like the uh performance gate we have right here. So yeah, that's the basic end toend for how I partner with this thing from kind of what work I pick up, the initial issue to my partnership for actually building it out. At a high level, I build a plan. Uh I once I feel confident with the plan, I kick that over to autopilot to go execute. Maybe I use a pattern like uh the chief of staff model like I used at the beginning where I have one session that's controlling other sessions. Um so that that's possibly something I can do. Um and then I stay outcome focused and how I actually partner with this app, right? I don't typically look at diffs as a first thing, but of course I always have that available to me. I can go in and I can add comments once I get a PR up. I can immediately go and uh turn on agent merge so I can make sure that I don't have to babysit all the PRs I'm sending and that the right things will happen and this will actually land in the codebase. Uh we also showed off automations for automating kind of repeatable toil as well as like all the other things that I use this app for that are not just writing code but like telemetry analysis, feedback analysis, even doing PowerPoints. Um I actually do I have my message one I want Yeah, I even have one that triages all of my messages in Slack and Teams. That one's super fun. Um, I run that one manually because it was if I had that on automation, I'd be a little worried about the token spend on that one. Um, because I get a lot of messages. But there's one more thing I want to show you. Like I gota I got to do the seed jobs. One more thing. So I already kind of referenced this, but like I think we're all kind of collectively getting exhausted by like managing all these chats. It can get overwhelming even with this like CEO model. Um, and so, you know, something we've been playing with a little bit in the app is a concept called canvases. Um, so I'm going to say open the GitHub Copilot app triage board canvas. And so it'll become more clear when I show this in a second, but a canvas is essentially some UI that my agent can create, but that UI can also drive the app. And so Cassidy, I think, had a really cool one in the uh in the Microsoft Build keynote that's worth checking out where she built a canvas for PR review. It's a fun one showing you can do anything where she would basically do thumbs up, thumbs down. If she gave thumbs up, PR was reviewed or PR was approved and that would send a comment back to the session and go actually uh you know approve the PR and get it merged into the codebase and if she denied it, nothing would happen. Um so you can do those sorts of things, but I'm going to go ahead and full screen this. So you can build any sort of canvas like this is just UI, right? Um so like for example like in the run-up to launch like I created a launch board and that was all the things that I needed to care about for launch and it wasn't just GitHub issues. It was the feedback we were getting on our internal um Slack channels and teams channels and things like that all in one place. Um I've even seen people do things like Trello boards. So you can ask the app to create a Trello board and as you drag uh uh as you drag items from one column to the next it will actually move things forward in the app. So let's just go ahead and and actually show this off. So like here you can see there's one looks like this one is about sub agents. When a sub agent needs to delegate back to the main agent we have a hang. Okay. So I kind of want to investigate this. Um so like I'm just going to go ahead and click start session. And so then if I go back to the app, you can see from this UI we just generated, we went and actually I'm now driving the app. So we have the triage board. We have a sub issue here that's been kicked off where it's actually going and creating a session from that UI and investigating what might be going on with this uh with this hang we have in the application. So this is really really cool because I can basically just full screen this thing and I could live in this all day, right? I don't even have to go back to chat if I don't want to because this UI is not just some, you know, static, you know, here's my triage list of issues I need to focus on. This UI is actually driving the app now. Um, so there's a lot of really really cool things we can do here um with this canvas construct. There's some already built into the app. So we have markdown which I did not show. We have browser. Um, and there's a couple more coming to the app very soon. Um, so I'm gonna wrap up now. Uh, but I think canvases are really cool and it's a it's a nice exploration into what the agent native like UI for partnering with these things looks like and how we go beyond chats in the future to kind of escape this thing of like having to manage all the chats mentally. So with that, I'm going to wrap up. Uh, that was Pice's long spiel uh and tour on the GitHub Copilot app. Like I said, uh, go give it a try at g.ioapp. And with that, I think I'm going to pass back to the group. Bravo. I have I have the power to do this. Wait, watch. That was so cool. Thank you, Pierce. I feel like Yeah, there we could do entire streams on so many different aspects of the and I think that it's really exciting. There was a lot of commentary, a lot of questions about so many different things. I thought this one from tamed craziness was a good one with all the branches in the Kitub app workspace. How will co-pilot know which ones to merge before having to rebase? I wanted to point out that we recently just published a blog post on git work trees and how the app uses those because I think that is a very useful thing to know. And so you could go to github.blog and it's one of the first posts listed or you could go to this mega URL that we just shared there. I'm gonna hide the comment so we can see Burke's face again. There we go. But um anyway, that was really cool. Does anybody have any specific questions about things? I think canvases are super powerful. I've been like noodling around playing with all of those. I feel like the automations I don't take enough advantage of those. And then meanwhile, I was talking to uh my manager Ashley Willis who has like 40 going on any given day. And so I like that with all the things that you showed, the app enables us to work how we want to work. That's right. Everyone is using it in very different ways and it's cool to learn from different people that way. Totally. Yeah. Like I think it's one of those things like it's a very like marketing thing to say like this is my home base for work, but like it it really is, right? Like it's not a joke. Like I start in the day, I look at all these automations, like I see what's going on, and then from there I start kicking off sessions and I jump back and forth. And of course, like I'm on kind of a manager schedule, right, where I have less focus time. But the cool thing about the app is like I'm still contributing to the codebase, exploring these things, even you know, being in meetings all day because the app is kind of allowing me to to do all of that in the background. So it's cool seeing like how everyone partners. Enrique is on our engineering team and like his job is to build the app literally. So, I'm interested to see like his flow for how he works because like you said, Cassie, like every single person is so different in how they partner with this thing. Yeah, I have to say our goal developing the app is or at least my goal is how can I do my job without leaving the app? Let's let's make sure I can do everything I want to do there, whatever that is. Um, so yeah, that's exciting. By the way, I love canvases. The one that you show is great. We actually use this every day in standup to triage bugs. Again, we've built all sorts of canvases. I've been like video games once just because, you know, I'm bored. All sorts of things. Um, so I think there's some stuff I want to show you guys. Uh, should we just get into it? Let's do it. Pierce, did you fall over just now? I'm okay. My camera has fallen off at Pierce fell into the mas over and I fell. I feel like we could invent some lore here, but let's we'll just get into the app. Awesome. I'm I'm glad you're okay, Piers. All right. So, I'm sure if you're working with these types of apps, h you face this issue. You have a session going, you have an automation going, but it's like I was going to say 5:00 p.m., maybe a little bit later, and you have to go for dinner, whatever. So, what do you do? Do you close your laptop? Do you like leave it in this weird like how much can you close the lead without putting into sleep so that your assertions are all going and then the next morning you have to like open it up right like it it it's really annoying. So, uh, what we've tried to do and a couple of things that we we have shipped for GI that I'm pretty excited about is cloud stuff, right? So, you can close your laptop, go about your day, do whatever, pick up a different device, maybe open the website on a different computer, maybe grab your phone on the sofa, you know, let's let's do full workaholic lifestyle, right? You're just like working on all of your devices non-stop. Um, so I want to show you some stuff about that today. So yesterday, um, I was thinking, okay, what repo can I build to demo some of these things and not going to lie to you, we shipped GA yesterday, so I am pretty tired at this point. I'm taking some time off on Monday. So I thought, okay, let's build really simple example. Is it Friday or not, right? Because I I really need to be I really need it to be Friday. Um, unfortunately it is not Friday yet. Uh, so what's going on? There's a bug in the app, right? Like it is saying it's Friday. It it clearly is not unfortunately. So uh let's use the app to do uh some stuff there. So first of all, you can now create a session that's going to run in the cloud. So I can close my laptop and the session is going to keep uh executing. So let's pick the project. Is it Friday? Very original. Let's change the session to run on the cloud and let's implement something simple like uh you know uh when it's Friday animate the confetti with CSS. Okay. And that's going to create a cloud session and it's going to execute basically the agent is going to run in the cloud and you're going to be able to do things like uh what PICE was showing you before but now it's going to be in the cloud. If I close the app everything is going to keep working. So as you can see when the cloud session connected this thing at the top changed and now there's an open on remote link as well as a QR code. You can scan the QR code with the GitHub phone app and just continue the session straight from your phone or you could like click open on remote and that's going to open this session on github.com and you can continue there. You can see that this is working through it. I don't want to have you here waiting for this thing to be fixed. I just want to show you I did one earlier today um to implement dark mode. same thing cloud session and I'm just going to switch to com and you can see that this is the session uh that I kicked off earlier to art mode and you can see it was working through it right so now I'm on the website I am continuing the session from before so you know it did the code but I didn't actually commit it so I'm on the website could be on a different device I'm just going to say cool um you know create a new branch change to week slash uh dark mode. Commit the changes there and send a PR, right? Okay. Well, the demo gods are not with me today. There's some flakiness going on there, but uh we can come back to it later. this thing will continue executing the cloud and commit the changes and create the PR. So let's switch on to uh something else. Uh what about automations? So PICE was talking about this earlier. Um similar concept we now support cloud automations, right? We support local ones, but those need your app running on your computer. What if you just want something running like all the time? And what if you want other types of triggers? For example, when a pier is created, you want something to happen. Maybe you get a message on your Slack channel. Um, when an issue is created, you want to do something about it. So, let's actually do that. Let's uh start automating. You've probably heard a lot on Twitter about agent loops. This is a way you can create an agent loop that's al always going to be running when you create an issue. So let's say fix issues all the time. I'm going to change the trigger to issue created. So every time I an issue is created in my repo, this automation is going to run. You can filter it if you want and you can narrow down what tools you want. I like to leave in yolo mode. So you know, let's just have everything on. I'm going to select my project. Is it Friday? I'm going to switch the model to auto and I'm just going to copy paste a prompt that I wrote before. There you go. I just walk through it. Really simple honestly. Um, a new issue was just created in this repo describing a bug. Your job. One, read the issue. Understand what's going on. Two, reproduce the problem by inspecting the index html file. Three, make the smallest correct fix. Do not refactor unrelated code. Four, open a pull request using conventional commits. Five, post one comment on the original issue. Just saying what's up. Keep everything consens don't don't reinvent the wheel. So, let's create that. Nice. So, now we have this cloud automation. And again, it's going to work even if my laptop is closed. Let's go back to the ribble and let's create an issue. terrible. It's only Thursday, but the website says that it's Friday. Unusable. Fix it. Very well. Looks looks like a pretty typical bug report to me. Yep. So, uh there you go. We just created the issue on the ribble and we have the automation here waiting to pick things up. So, let's give it a bit of time to um listen to the trigger. By the way, I'm going to show you if we go to agents, you can see these cloud automations from github.com as well. If you go to agents automations, you can see that it's here. Fix issues all the time. So you can access them from here. Okay, looks like it picked up the new issue and it's working on it. Let's see what that looks like. So you can see that it's doing its stuff and you can check it from the website. So on any device or if we switch to the app, you know, eventually we'll pick up the run. Yeah, it's running, right? So you can follow with what it's doing. And we don't have to sit here waiting for it to finish. I can just show you what it looks like with one that I created yesterday. Same bug. And um this is the issue and this is what it posted. Uh great catch. The root cause was a oneliner in compute Friday blah blah fixed in PR number five by changing the code. So if we actually go to that PR you'll see that it actually created the PR in draft mode. So you can take a look before it completes. And now you would be able to review it, complete it and actually um fix the issue. Let's check on how this is doing. Done. The bug was a oneliner. PR number server is open. Okay, awesome. Let's actually check that. Terrible. That is my issue. You can see it posted the comment. Let's go to that PR. Yep. Let's take a look at the code. Yeah, pretty easy fix. I mean, it looks good to me. Let's review it. Yeah, not drop right for review. Yeah, let's merge it. Awesome. So, as you can see, h you can automate anything that you want. This is like a simple example, but really the sky is the limit. You can do anything you want on issue created. And I have some cool news to share with you, which is we're going to extend two things very soon. One is the the triggers. So, we're going to support more triggers, but also the timebased triggers. Today, we support daily, hourly, and weekly. We're going to have more flexibility here. We're gonna let you choose what day of the week, what time, multiple times, and even like a full-on chrome type trigger. So, if you want to write a chrome expression to trigger it just the way you want it, you're going to be able to do that very soon. I don't want to promise a date, but like very, very soon. We're talking days here. So, that was my demo. I'll take it back to the group. That was awesome. Hang on. Yeah. Where's the Where's the applause? Got to do the applause. So I got a question actually. You you did that code review process and stuff on the website. Would you be able to do that in the app as well? Oh yeah, definitely. This is actually something that I love doing. Uh because it happens very often. So Cassie, if you give me a second. Sure. Uh I'm sure this has happened to you. You're working with another dev and they tell you, "Hey, I have this PR. Can you review it? can or even like you just want to pull it locally and test it, right? So, you just come here, you grab the URL of the PR and I just go to the app and I just do command K or control K if you're on Windows and literally paste the URL. No way. I didn't know you could do that. New session. Cool. That's going to create a new local session targeting that PR. So, it's targeting that branch. It's pulling that branch locally. You can see that I can see the changes here. Uh it's linked to the PR and right from here if I wanted to like I can do whatever I wanted. Like I could do like ah actually I don't want to review it myself because whatever but let's do like a rubber duck since we're in the rubber duck session. Let's do a rubber duck and this is going to do that. So yeah, you can do this is something I use every day with the rest of the team. Honestly, I love it. That's so cool. I did not know you could just paste a URL in there. That has changed so much suddenly in how I work. The way Cassidi, it works also with issues and with PRs. Does it have to be an issue or PR that you own? No. Okay. This is very good news for me. Yeah. There's so many times where I'm working on open source projects or someone asks me to review something just to get another set of eyes and it might be on a repository that I don't own, but I contribute to it or or something and I might not have it pulled in the app. And so having that URL sharing that that's pretty neat. I'm glad to learn that today. Yeah, I really like the um it's the little things. So, the fact that you can get started on a repo without having to clone it is huge to me. I know it's small. I know it's a small thing. I know how to clone repos, but a lot of times I won't work on something because I have to clone the thing. And it's like I got to go to my hard drive. I got to create a folder. I have to go into that folder. I have to clone this in. I have to open the tool. And being able to copy the URL in is just like another example of kind of it being abstracted away from you. So, it's like if you just want to work on the thing, just work on it. Okay, just start, which is great. It's just until somebody did it, it had never occurred to me that I would be more apt to work on things if I didn't have to clone them to my machine. And I really like the cloud thing because that's even then it's even better. then it's even it's just not on my machine at all. Which is really good for people working in enterprises where they're just not that keen on the idea of you putting allow all on your local machine and letting the agent go nuts, which is understandable, but at the same time, if you don't have y'all chat, if you don't have YOLO mode on, you're just not you're just not doing it uh in a way that's going to be fun at all. Right? Like if you're gonna do a development with AI, it's got to be able to to to work autonomously. Anyway, those were my thoughts that no one asked for actually work. If I if I may jump in, I'll just say take it with a grain of salt, but I develop the app every day, all day, full jolo mode all the time. Never had an issue. Doesn't mean you're not going to have an issue. I'm just telling you like I never had an issue. Way easier to work with it. So, at this point, I trust it a lot. trust is a thing. Sorry. Go ahead, Cassie. No, I think developing that trust is a thing where I I feel like people are more and more learning that they can trust agents with thing again because models are improving, capabilities are are getting better, guard rails are improving. I It's scary to me still to do YOLO mode, but on some projects I'm like actually I could do that and I let it go. But I also have a problem with control and wanting to make sure things are done the right way. I think the scariest thing is like I I'm kind of in a similar place as Enrique like I basically yolo all the time. I would say the one case where I do I am showing some restraint and not running yolo is like you have to be careful when you give it like tools that can do things like modify infrastructure and things like that. That would be my that would be my only thing is like if you're using the Azure MCP heavily for things like you need to you need to make sure that like you're you're being careful with YOLO mode and things like that. But like my perspective is like on my code like if I don't give it any tools that I think are super dangerous. I don't think it's going to generally do anything that I find that scary and say it like deletes all my code. Well, like I have git, right? And so that's kind of the whole point, right? So like I I always feel confident that no matter what happens locally in my session, I can always recover what happens, right? And so um for me it's like of course there's risk and everything and you have to decide where you're at on that spectrum. But to Burke's point, like if you really want to free yourself and start running multiple things at once, to some extent you do have to come to acceptance at some point that the only way you can do that without just having to supervise all these things constantly is to run and yolo. Yeah. And I think that's where the mental overhead matters a lot. Well, and when you're just clicking like allow all the time, it just trains you to not Yeah. People aren't even looking at these problems. You're not reading it. Yeah. So, we saw that in VS Code. Yeah. It would be like, can I delete production database? You'd be like, yes, go. Right. Like, because you wouldn't know. Yeah. Human nature. To Enrique's point and actually Cass's point as well, I've been using agents for like two years now. Has it been or like 18 months Pierce we've been at this like hardcore which by the way in AI years is 17 years human years right but to the point like I do trust it I actually trust that the agent is not going to nuke my hard drive it's not going to do anything because it never has in thousands and thousands of conversations it's never done that but I can just imagine trying to tell like a CIO at a place where like you have credit card data or something like look you have to trust the agent like No way. But that's why cloud sessions are great because they're sandboxed and and you're you're safe. Like it can't it can't hurt anybody out there. I I think like one of the challenges for me with cloud sessions in the past had been like I don't want to wait like forever for a VM to boot and like get set up like but you saw his demo like the you're getting you're starting getting streaming results back from that from that cloud automation very very quickly, right? And so I think for me like I can almost partner with it similarly to a local agent and for me that's the huge unlock right like that that's been my problem with some cloud agents is the p in the past is it was almost too much like like I like running in yolo and not being involved but at the same time I still want to be somewhat involved and sometimes with the cloud sessions like in the past it's just like I assigned it this issue and then I guess I come back like a day later and I look at it but like with these cloud sessions it feels like I'm still more in the loop right and it's fast and it's almost just as fast as local and So then it's not even just the security benefit. It's that it follows me across my devices. It's available anywhere. I don't turn my local laptop into a server, which is not my preferred approach for making sessions accessible everywhere. And I don't fill up even my local hard drive space, right, with work trees and things like that because it's happening remotely, right? So I think there's just so many benefits to that partnership model. And I think like the cloud sessions and automations in the app is like a super underrated feature because of those things. I have a question for all of you and I know that we're all actively like working on and with the app. What's something still missing that you wish were in it? I have the first one which I've already actually talked about with the team. I want to have voice mode in canvases. That's a good one. I feel I feel like that would unlock the next level of interaction for me. I have one. Are we taking requests right here? We're doing write it down. here. Go build that. I need dev container support. I need WSL. I need remote SSH. Like I have all these systems already set up. And a lot of people do, right? Like if you're using Chad, I'd be curious if you're using VS Code, you're probably using the remote capabilities of VS Code in some way, shape, or form. I want to be able to just like look uh use those use the ones they already have set up instead of having to use other ways of doing it. Totally. You do that. Just vibe that in this afternoon, Enrique. Well, we're we'll probably have good news for you pretty soon about that. Let's go. He promised here right now live. Um, I think for me like uh Enrique mentioned like this concept of not wanting to leave the app and uh I'm kind of the same way and there's still like some some small little paper cuts like in the issues and PRs experience where things you can do on.com like are not still yet totally possible in the app from just like an editing the issue or PR perspective. And so I think for me like as someone who spends a lot of time in issues and things like that that's like a quality of life thing we need to clean up but we're also working on that as well. The other I would say is bring your own key. I love like hooking up like Cerebras or using local models or things like that. We also have very good news for people on that front coming very very very soon. Uh bring your own key support will be in the app. So that's amazing. But that's another big one for me because that's something I love about using VS Code is like I use the the Cerebrus bring your own key and that's like a thousand tokens per second. So like when I need like a task that I just want done extremely quickly like using the Cerebrus models in the app, it's like you feel like you're flying, right? Because it's literally 10x what like the tokens per second is for like some of the other cloud-based models that we have in the product. And so that that's a super fun one when you're like I want to actually partner synchronously with the model and not just fire off something and check back in on it later. So I'm pretty excited to have to have bring your own key inside the app soon. Enrique, what what's what's top of mind for you? Honestly, bring your own key was the one I was missing the most, but I'm not going to have to miss it for too long. But, you know, something maybe not that I'm missing, but like I would like to discover in the future is the idea of reviews, right? Like, okay, you have a lot of sessions, you're creating a lot of PRs, right? Not we're not all ready to trust the agents. How do we do that? Do we need to revisit the way we are reviewing our artifacts? is code the right level the right granularity for reviews. Do we need something a bit more abstracted? Do we need different levels of reviews? So really what I want is to spend some time thinking about this and figuring out like new patterns that make our life easier because as I said like we use the app every day all day. We have a very small team building this and we send a lot of PR. So this is like a very real problem that we need to solve for ourselves. So that's what I love. we find a problem, we we like find a solution and then hopefully we share with with you and uh it's useful for you too. Yeah. Plus one to all the things. I I know that a lot of my team uses the local foundry models too and and is able to spin those up and being able to integrate bring your own key with that too would be amazing. We're getting there slowly but surely and quickly but surely honestly actually. So yeah, we are moving quite fast. In fact, it's been that way for like 18 months. But it is true that like it's the feature that you want. It's like already there. You asked for it. It's like there plus 10 others that you didn't ask for that you didn't know about. For for some of the behind the scenes of of Microsoft Build for any of you all who saw the event or or anything, there was a point where uh there was the opening keynote. I was delivering it. Burke was behind the scenes running all kinds of things. PICE was in the room with us and as we were using the app, he would be just like, "Oh yeah, we can improve that." And would just like make fixes as we were rehearsing and it was an amazing turnaround time and it made the keynote that much better and so many things that much better. But it was wild how fast it was going. Yeah. And by the way, special shout out to the GitHub app team for GitHub co-pilot app team for shipping a release the day of the keynote or no pressure. It was one of the two. And Pierce is like, "Yeah, just so you know, they just shift the release. We're like, no, please." But also, also Cassid's demo where she does like the thumbs up, thumbs down. So that was Cassid's idea. When she had that idea, the cameras didn't work inside. Yeah. And so we we pinged the engineers. We were like, "Hey, we got this idea for a demo. Can you get it in the app?" And it was in the app that same day. It was amazing how fast that was. Yeah. I uh I have a video of said keynote if y'all want to see it. Let me pull it up. Oh, I accidentally pulled in a UTM link there. Ignore that part. Just know that is the YouTube link to that video. I pulled it from I pulled it from my own newsletter because that's where I know the link lives. Um, one feature I'd like to see in GitHub is the ability to pull an OS and build onto it. Oh, just large large files. I see. Oh, it's like LFS support. Yeah, that's what it sounds like. LFS should work. Uh because I have to have that for for VS Code repo contributions as a team member and and that should work in the app. Um yeah, person who just gave that if if there's if there's more color you can add to your comment, that'd be awesome. Yeah. And if you hit any specific issues with an open source repo, just open a bug in the in the app and we'll look at it and we'll figure out what's going on. I liked this comment that Burke nightly Burke shrinks down and lives the little town behind. It's actually not to illusion. It's so far back there that if I was to walk back, I It's an actual town. Oh yeah. If you walk, you would actually like get in the little bus and be like, "Bye." Wait, do you have like the Christmas version of your town? Like my grandma had one of those and I I love that thing. Like every every Thanksgiving we would put up the Christmas decorations and there was like the Christmas town. They make a Lego version of that. You can get lighting kits and like make them light up. But it's a it's a horrible pain. So I don't do it. And frankly, I regret doing this because I could have invested that money in like Nvidia or something. Number one. And number two, it's all dusty. the the dust thing is very real. That being said, Lego has like increased in value more than gold or something at various points. So, I don't think it's a total Yes. If you don't take it out of the B if you just like Yeah. investment idea, just buy Lego and is it Legos? Just keep it there. Lego bricks. Bricks. Yeah, Lego bricks is is the correct term. Wait, I'm I'm also now realizing this is like a totally aside. What happened to like your old thing with the light and all that work? Are you in like a Did you move offices within the last couple? I'm just now internalizing this. I'm in the same spot. No, you used to have like the light in the back and you we do the fun demos. It's right there. Yeah. It's just the camera just moved. Oh, I see. This is just turning into everybody vetting each other's setups. Guys, I got a new keyboard stand this weekend. It was really exciting. I saw that thing. I saw you posted that from like the Amazon link or whatever to that. Oh, yeah. Or it was made by a small shop. I went to a keyboard convention. This is what's going super off topic. keyboard convention. Uh, one of the vendors there makes those stands. It's nice because it has USB ports for Bluetooth stuff and like for Yuba Keys. That's been really nice. Well, Cassie, I'm looking for a mechanical keyboard to buy, so maybe we should chat afterwards. Recommendations. You've come to the right place. This is This is We could Let's extend the stream another hour. That would be good. Yeah, we had a side conversation going. It was yesterday about mechanical keyboards. Yeah, we fully took over a meeting. it ended up like the the like AI summarizer was just like what is this about and like had to dis uh distinctly add chapters to what happened in that meeting. Um okay, that being said, I'm I'm noticing the time. Thank you all so much for coming to Rubber Duck Thursdays and showing us all about the app. It's been very very exciting. Are are we done? Are we not going to Are we going to do more? We we are at time actually unless unless we we could go over time. No, I uh we are indeed at time. No, no, I got a video to make and I rode Cassidy in last night at like 11. That's true. We got we got some stuff to do. But if y'all want to check out the app, you can go to github.comfeatures app. I also think it's at gh.ioapp. Let me Yes, g.ioapp. And so you can check that out. You can download it. You can play with it. You can use it with your GitHub copilot subscription. And once again, thank you all so much for being here today. It was very fun. Thanks everybody. Thank you. Okay, we'll talk to you later. Bye.