How the GitHub Copilot coding agent works | GitHub Checkout
GitHub Copilot's coding agent runs asynchronously in the cloud to handle backlog issues, bugs, and refactoring by opening draft PRs, executing tools via MCP, and running tests before requesting human review.
Highlights
3 clips · 5 min of 7 min-
- Developers can select multiple backlog issues and assign them directly to Copilot on github.com.
- The coding agent works on these tasks in the background and opens pull requests automatically.
- This allows developers to delegate routine tasks and focus on challenging feature work.
-
- Copilot immediately creates a draft PR that updates its plan and checkboxes as progress is made.
- A dedicated session view lets developers trace internal agent reasoning, tool usage, and test runs.
- External integrations like Notion requirements are fetched seamlessly using the Model Context Protocol (MCP).
-
- Developers can highlight code blocks in the editor and instruct Copilot Chat to open a background PR.
- This workflow avoids context switching, enabling developers to stay in the IDE while delegating refactoring.
That’s all the highlights.
Questions this video answers
6 · every answer cites the moment it was said01 How do I assign tasks to the GitHub Copilot coding agent? 2 sources · 0:53
You can assign multiple GitHub issues to Copilot directly from the issues page on github.com. The coding agent will pick up those issues to work on them simultaneously in the background.
02 How can I monitor the progress of the coding agent? 2 sources · 1:54
As soon as a task is assigned, the agent creates a draft pull request with a basic title and body. As it works, it gradually updates the pull request body with a plan and ticks off completed items.
03 Can the agent use external information outside of GitHub? 2 sources · 1:36
Yes, the agent can connect to external services like Notion using the Model Context Protocol. This allows it to pull in necessary requirements and context that reside outside of the repository.
04 What steps does the agent take before asking for a review? 2 sources · 2:48
The agent uses tools to explore the repository, runs tests to ensure the code works, and executes linters. This ensures that the generated pull request is clean and ready to go rather than half-baked.
05 Can I trigger background agent tasks directly from my editor? 2 sources · 4:36
Yes, you can highlight code in VS Code, open Copilot Chat, and ask it to open a PR for a refactoring task. The chat interface will trigger the background workflow and provide a pull request URL.
06 What subscription plans currently include the coding agent? 2 sources · 6:01
The coding agent is currently available for users with higher premium plans such as Copilot Pro Plus or Copilot Enterprise. GitHub plans to open access wider in the near future.
Section-by-section summary
3 parts
Delegating backlog issues to background agents
GitHub Copilot's coding agent moves beyond synchronous IDE completions by executing tasks asynchronously in the cloud. Developers can select multiple backlog items, assign them to Copilot, and let the system generate pull requests without blocking local workflows.
Tracking progress and leveraging external context
As the agent works, it maintains a draft pull request that updates its execution plan in real time. Through Model Context Protocol (MCP) servers, the agent can pull requirements from external tools like Notion, execute bash commands, and run linters to ensure quality before requesting a review.
Triggering background tasks directly from the editor
Developers can invoke background agent workflows straight from Copilot Chat in VS Code by highlighting code snippets and requesting refactors. This integration prevents context switching, functioning like an asynchronous team of AI interns handling tech debt and test coverage.
n next · p previous clip · t highlights/full
< > slower/faster · / search what was said
-
GitHub Copilot coding agent8× · first 0:15
An asynchronous background agent that handles backlog issues, bug fixes, and refactoring by opening draft pull requests.
-
Model Context Protocol1× · first 3:14
A protocol used to provide external services and context from outside GitHub to the AI agent.
-
Copilot Chat3× · first 2:32
The chat interface in the IDE used to interact with Copilot and trigger background tasks.
1,595 words · about 6 min to read
Andrea: I am so excited for the future where all these agents are doing my boring work for me. I’m Andrea Griffiths, Senior Developer Advocate, and today, we’re exploring something that’s going to change how you manage your development backlog. We’re diving into the world of GitHub Copilot coding agent. Welcome Tim. Tim: Thanks, Andrea. Andrea: So, what in the world is GitHub Copilot coding agent?
Delegating backlog issues to background agents
1 Highlight · Assigning multiple backlog issues to Copilot in the cloud
Tim: Well, really the goal with GitHub Copilot coding agent is to take all the great stuff we’ve already done with agent mode in the IDE that lets you have Copilot help you write and then test code, and turning that in something that isn’t just running on your machine, but something that you can run in the background. Andrea: Could we take a look at how it works? Tim: Yep, definitely. So here I’ve got my GitHub issues on github.com. And like any project, I’ve got a bunch of stuff here. There’s new features I want to add, bugs to fix, teach debt that I want to work on as well.
And that can get kind of overwhelming when you’ve got this big backlog. And the great thing with the coding agent is that I can pick the thing that’s maybe most interesting, most exciting, and most challenging, and I can have Copilot work in the background on some of the other stuff, and I can actually assign multiple issues at the same time. So, I’m just going to pick a bunch of issues here, click into the “Assign” menu, and then pick Copilot. Now, Copilot is going to pick all those issues up at once, work on them in the background, create a pull request, and then once it’s done, it’ll ping me for review.
Andrea: Wow. So you can move on and go work on that exciting new feature you want to add to your project, and Copilot is taking care of all the boring stuff?
Tim: Yeah. That’s right. And then when Copilot’s done, it’s going to kind of bring you in and ask you for feedback. Here’s an issue that I assigned to Copilot a bit earlier on today. And this issue is a bit interesting because it doesn’t actually have a lot of the details in the issue itself, and rather, it links out to Notion, which has the document that the product manager wrote with all the requirements. So, not everything we need
Tracking progress and leveraging external context
2 Highlight · Monitoring the agent via draft PRs, session views, and MCP
is in the issue. Earlier on, one of my team assigned that to Copilot and our pull request was created here. And we can click into that and we can see this pull request that Copilot has created for us. So, right at the beginning, as soon as you assign the task to Copilot, it’s going to go ahead and create that pull request as a draft and then it’s from that pull request that you can monitor the agent, understand what it’s doing and keep track of its work. So when it first gets started, we’re going to have a very basic pull request body and a very basic work-in-progress title that just says— basically has a copy of the issue.
Then as Copilot works, it’s going to gradually update that pull request body and say, “Here’s my plan. This is the stuff that I’m going to do.” And then gradually tick off things from that list as it works. So, I can really keep an eye on Copilot and know what it’s doing. Of course, you can also go into more detail and just like you have the chat logs in VS Code or in JetBrains, we also have a session view in GitHub where you can really see in detail what the agent is doing.
So I’ve just clicked into that here. We can see the agent talking to itself, and then we can see it using tools to basically understand the problem and explore the repo to figure out what code it needs to change, run tests to make sure that the code it’s writing actually works, and then when it’s done, it pushes and asks me for a review. So here we can see it’s looking at the package.json so it understands how the repo works. It’s looking at files. It’s running bash to find things.
Another interesting bit here is where it actually goes to Notion to find that document that I linked in the issue. So that’s powered by MCP. I can include model context protocol service with this agent that it can use to get other information and get other context from outside of GitHub. And actually from within GitHub with a GitHub MCP server. If we scroll a bit further down, then we’ll see the agent is even running my linter. So, at the end, when Copilot pushes and requests review from me, I’m not getting a PR that’s half-baked and broken, but most of the time I’m going to get a PR that’s good and ready to go, and hopefully I can merge it right away.
So, going back to the pull request here, we can see Copilot requested a review from me and then I can review that just like a PR from a member of my team.
I can decide to work on that myself, or I can leave comments. And Copilot is going to pick up those comments and do the stuff that I tell it to do. So it’s really easy to iterate. Andrea: Very cool. So you can keep control of what Copilot is working on. And then if it’s completely off-base, then guide it back to where you want it. Tim: Yeah, that’s right. Hopefully, what we could do with this is let developers do more of the stuff they really like,
Triggering background tasks directly from the editor
3 Highlight · Triggering background agents directly from VS Code chat
and let Copilot take over the boring stuff. Andrea: Fantastic. Okay. So what happens next? Tim: One of the other really nice things we can do with Copilot coding agent is actually trigger it straight from VS Code. So, here’s just an example of— this is a React component. And I’ve got a loading indicator here. And that’s quite a big block of HTML. So it’d be really nice to move that into its own component so it’s separate and abstracted out. I could do that now, but that’s going to distract me from my work.
So what I’m going to do instead is I’m going to highlight this, going to head over to Copilot Chat. And I can say, “Open a PR to refactor this into a separate component.” I send that off to Copilot and Copilot Chat is actually able to trigger this background workflow as well. So, obviously I’m used to working synchronously, directly with Copilot in Copilot Chat, but now we have the ability to actually say, “Can you go and do this thing for me in the background?” And it’s going to, in exactly the same way, open up a pull request and then tag me when it’s done.
And you can see here in chat, we’ve literally got the URL of that pull request. I can click onto it. And then from here I can see Copilot start to work. Andrea: That’s awesome. So while are you working and you don’t have to leave the editor to kick off another— Tim: Yeah, that’s right. You don’t have to get distracted. You can stay in the flow, stay on the stuff you’re working on, but also start to be in this world where you’re a developer working on your own thing, but you’ve got almost a team of AI interns who can be doing stuff for you
in the background and helping you to get more done, and hopefully, leaving the fun stuff for you. Andrea: This is amazing. How do you see teams using GitHub Copilot coding agent? Tim: Just an example, our billing team used it to increase their test coverage for their main projects. They didn’t have time to do that because of other priorities, but they could have AI do that for them in the background, and they just came in, gave it a review, maybe made some tweaks, and then they’ve got this project that’s a lot more maintainable and a lot more reliable for the future. Andrea: That’s amazing. So tech debt does not stand a chance.
Tim: I hope so. Hopefully this is going to be the end of tech debt. So at the moment this is available for people with Copilot Pro Plus or Copilot Enterprise. So that’s our higher premium plans, but we are looking at opening this out wider in the near future. So if you don’t have one of those, go ahead and upgrade, it’s a great opportunity to try this. But if you don’t, then watch this space and we’ll have something for you soon. Andrea: Thank you, Tim. I appreciate you coming by and showing us. I am so excited for the future where all these agents are doing my boring work for me.
Tim: No worries. I’m excited for that too. And for my open source projects, I hope they’re going to get a lot less tech debt in the future. Andrea: And that’s your first look at GitHub Copilot coding agent. Drop a comment below. Let us know how you’re using this in your repositories. And if this was helpful, please hit that “like” button and subscribe to GitHub’s YouTube channel for more feature updates and dev tips. Push these changes to main and we’ll catch you in the next release.


