Skip to content

Add Copilot Coding Agent integration post and related assets #8608

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

burkeholland
Copy link
Contributor

This commit adds the Copilot Coding Agent integration in Visual Studio Code blog post.

This commit adds the Copilot Coding Agent integration in Visual Studio Code blog post.
@burkeholland burkeholland marked this pull request as draft July 12, 2025 17:32

## What’s next?

The Copilot Coding Agent integration in Visual Studio Code is currently in preview, but as with everything we do, we do it all in the open and you can use it all today. If you want to light all of this up in your editor, all you need to do is make sure you have the GitHub Pull Requests extension installed and add the following settings...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to list 5 things that are coming to make this paragraph interesting

@rebornix @bamurtaugh

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also mention the vision how we want to change the interaction with the coding agent in VS Code (if we plan to do that in July/August)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend linking to our GH Coding Agent July iteration plan: microsoft/vscode#255483, and including the high-level bullets from it directly in the blog (PR performance and rendering, bringing in the Copilot Agents command center already present on GitHub.com into VS Code, integrated chat view for Coding Agent sessions, sharing custom instructions between the Coding Agent and VS Code, and further documentation).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

made some tweaks to this section, would love feedback!

![A WIP PR shown under the "Copilot on my behalf" section with the "View Session" button highlighted](copilot-wip.png)

In this screenshot, the agent implemented a trending section complete with UI and database changes. All of this is one interaction so it's only one premium request.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a paragraph that covers how the VS Code team is dog-fooding on the coding agent. And would link to all the PRs that the coding agent has done - and this is increasing every milestone.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@olguzzar could i get a hand with this - this is a great idea

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find a way to filter PRs by copilot from the Pull Request page but this is a search link that lists all PRs for vscode repo https://github.com/search?q=is%3Apr+head%3Acopilot%2F+repo%3Amicrosoft%2Fvscode&type=pullrequests

Copy link
Member

@DanielRosenwasser DanielRosenwasser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't get to read the full thing but don't want to forget by tomorrow.


There’s a new **Copilot on My Behalf** query in the Pull Requests view. This shows you everything Copilot is working on for you. Want to see exactly what the agent did? Click "View Session" and watch the play-by-play. You get full transparency into every command and decision. You can also terminate the agent - all without leaving the editor.

![A WIP PR shown under the "Copilot on my behalf" section with the "View Session" button highlighted](copilot-wip.png)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the image, it might look more polished if you dimmed out most of the screen and made cut-outs. Let me know if you want a hand with this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - could use all the help i can get!


The coding agent then opens a PR and goes directly to work - skipping the issue step entirely. It distills down the context into a detailed PR description and you'll see that Copilot Coding Agent makes use of todo lists so that you can see what its doing and where it is in the process at a glance.

![A GIF that shows the delegate to copilot button in chat](delegate-to-coding-agent.gif)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Frame-rate on this GIF feels off - maybe worth re-recording somehow or with different software?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - I can fix this

burkeholland and others added 15 commits July 14, 2025 17:56
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>
Co-authored-by: Daniel Rosenwasser <[email protected]>

Instead of only having one agent in VS Code, you can now have multiple agents running at once working on your behalf. This is _actually_ being a 10x developer. It's officially a a thing. You get to hand off any work you need done to to a squad of AI teammates.

In this post, we'll take a look at what the coding agent is, give you an exclusive preview of the integrations coming to VS Code and even tell you how you can start using them today.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To help differentiate GitHub's Coding Agent vs VS Code agent mode, I'd suggest we capitalize instances of Coding Agent:

Suggested change
In this post, we'll take a look at what the coding agent is, give you an exclusive preview of the integrations coming to VS Code and even tell you how you can start using them today.
In this post, we'll take a look at what the Coding Agent is, give you an exclusive preview of the integrations coming to VS Code and even tell you how you can start using them today.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made these changes - but I do think it's a bit confusing that we use different capitalization than what GitHub does, seems we should stay consistent across products

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good feedback. I think for this post, using the capitalization you've now added consistently is fine, and then we can revisit in future docs.

@Mrkell76
Copy link

This commit adds the Copilot Coding Agent integration in Visual Studio Code blog post.

@gmail.com

Copy link
Member

@rebornix rebornix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

![A WIP PR shown under the "Copilot on my behalf" section with the "View Session" button highlighted](copilot-wip.png)

In this screenshot, the agent implemented a trending section complete with UI and database changes. All of this is one interaction so it's only one premium request.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find a way to filter PRs by copilot from the Pull Request page but this is a search link that lists all PRs for vscode repo https://github.com/search?q=is%3Apr+head%3Acopilot%2F+repo%3Amicrosoft%2Fvscode&type=pullrequests


![A GIF showing Copilot assigned to an issue from within VS Code](assign-to-copilot-gif.gif)

As with every VS Code feature, the VS Code team itself uses the Coding Agent integration in their own development. In fact, you can see just how many PRs have been assigned [to Copilot Coding Agent in the VS Code repo](https://github.com/search?q=is%3Apr+head%3Acopilot%2F+repo%3Amicrosoft%2Fvscode&type=pullrequests) - and that number continues to increase.
Copy link
Contributor

@olguzzar olguzzar Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@isidorn @rebornix @bamurtaugh I added the dogfooding section here instead as I think it fits better, would love feedback

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants