Skip to main content

Giving Copilot Agent in Visual Studio a try

After using the GitHub Copilot Agent mode for some time in VS Code, I finally found some time to give it a try in Visual Studio. Agent mode got introduced as part of the 17.14 release so if you are still using an older Visual Studio version, please update first.

Remark: Other interesting AI features in the same release are Next Edit Suggestions and AI comment generation.

Let’s dive in!

  • Open Visual Studio and go to the GitHub Copilot Chat window:

 

  • Click on the dropdown icon next to Ask and choose Agent:

Remark: Notice that the Edits feature has disappeared. So you only have Ask or Agent. I don’t know if the feature is still there, but at least I couldn’t find it…

  • Now we can ask the agent to perform specific tasks or let it figure out a solution based on a PRD (Product Requirement Document) or similar you’ve provided. So far so good.
  • The not-so-secret superpower of agents is that they are not limited to your IDE but can interact with the outside world. Out-of-the-box, you get access to MCP tools that can interact with GitHub:

 

  • Of course you are not limited to GitHub only and we can add other tools as well. Therefore create a .mcp.json file in your solution folder.
    • Notice the . in .mcp.json. This is not a typo!
    • The mcp configuration can be stored in multiple places. Some of these locations require .mcp.json while others require mcp.json. Don't ask me why!

 

    • In our MCP configuration we can point to multiple MCP servers. STDIO, SSE and HTTP based servers are supported.
    • After the file is saved and if the configuration is valid Github Copilot Agent will restart and the tools become available:

     

    • In case it doesn’t work, have a look at the GitHub Copilot information in the output window:

     

     

    If you prefer a video, here is a good starting point:

    More information

    GitHub Copilot Agent mode (Preview)

    Copilot Agent mode is GA- What has changed?

    Agent mode for every developer  - Microsoft for Developers

    Visual Studio 2022 v17.14 is now generally available! - Visual Studio Blog

    Use agent mode - Visual Studio (Windows) | Microsoft Learn

    Use MCP servers (Preview) - Visual Studio (Windows) | Microsoft Learn

    Labels:

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
    Read more

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
    Read more

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
    Read more