articleschannelstagsspacestoolkit
Microsoft Dev Blogs

How we build GitHub Copilot into Visual Studio

View Original
thumbnail

Building GitHub Copilot into Visual Studio

Journey from IntelliCode to Copilot Support

  • Visual Studio began its AI journey with IntelliCode in 2018, focusing on small language models for efficient execution on lower-powered machines.
  • IntelliCode includes an 'in-process' component within devenv.exe and a 'model host' within a ServiceHub process, seamlessly integrated into the VS ecosystem.

Introduction of Copilot Completions in VS Code

  • In 2021, GitHub introduced completions functionality in VS Code, followed by a similar extension release for Visual Studio in March 2022.
  • The 'copilot-language-server.exe' process handles web requests to GitHub for context, response processing, and additional features like content exclusion.

Copilot Architecture Evolution

  • The recent Copilot X release in March 2023 integrated new features, such as chat integration into Visual Studio.
  • The architecture now includes separate .NET 8 processes tailored specifically for Visual Studio, moving away from shared processes with other clients like VS Code.

Conclusion

  • The history traces Visual Studio's AI evolution from IntelliCode to Copilot support, highlighting the shift towards dedicated .NET processes for enhanced integration and client-specific functionalities.