{"id":34409,"date":"2024-08-07T09:00:57","date_gmt":"2024-08-07T09:00:57","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=34409"},"modified":"2024-08-06T22:26:56","modified_gmt":"2024-08-06T22:26:56","slug":"github-copilot-extensions-for-c-developers-and-beyond-now-available-in-vs-code","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/github-copilot-extensions-for-c-developers-and-beyond-now-available-in-vs-code\/","title":{"rendered":"GitHub Copilot Extensions for C++ developers and beyond now available in VS Code"},"content":{"rendered":"

GitHub Copilot is now more extensible than ever for extension authors in VS Code.<\/p>\n

At the Microsoft Build conference, we announced that VS Code extensions can now leverage APIs for Copilot to build custom chat participants<\/strong> that users can interact with in the GitHub Copilot Chat view in VS Code. To learn more, please watch the Build session on the new extensibility<\/a> and read more on the VS Code blog<\/a>. \u00a0Some notable extensions that have developed chat participants for public consumption include Microsoft Dev Box<\/a> and Parallels<\/a>.<\/p>\n

Another API that extensions can leverage LLMs with is the language model API<\/strong>. It enables you to integrate AI-powered features and natural language processing in your Visual Studio Code extension. To learn more about this API, please visit our VS Code docs<\/a>.<\/p>\n

What are chat participants?<\/h3>\n

You can read more in the VS Code docs for<\/a> more specifics on how chat participants work. These are specified by the user in the Copilot chat window, with queries using @<participant><\/code>.<\/p>\n

\"@Cat<\/a><\/p>\n

Some existing chat participants available in VS Code Copilot Chat that you may be familiar with include @workspace<\/code> and @vscode<\/code>.<\/p>\n

For example, @workspace<\/code> dynamically looks at all the code in your open workspace to provide relevant code snippets as context to Copilot Chat.<\/p>\n

\"Invoking<\/a><\/p>\n

On the other hand, @vscode<\/code> dynamically indexes VS Code settings to provide an answer.<\/p>\n

\"Using<\/a><\/p>\n

With the latest release, you now have access to build your own chat participant for your VS Code extensions, allowing you to provide domain knowledge to Copilot that would be relevant to your users.<\/p>\n

As a consumer, there are some chat participants to look forward to that utilized this API and are in the pipeline. For example, for users who have containerized development, there is a Docker Copilot extension that is currently in limited public beta<\/a> that allows users to learn more about containerization with regards to their app.<\/p>\n

What are language models?<\/h3>\n

With the Language Model API<\/a>, you can directly access and take advantage of LLMs contributed by GitHub Copilot in your own extensions, by specifying prompts, relevant context, and how requests should be sent to the model. You can utilize this API to enhance developer experiences beyond the Copilot Chat view.<\/p>\n

For example, one feature that utilizes the Language Model API is AI-powered rename suggestions, that allow you to dynamically rename symbols in your C++ code. These will automatically invoke suggestions when you go to rename a symbol in VS code when you have the Copilot Chat extension installed.\"AI-generated<\/a><\/p>\n

Additionally, the source control view utilizes the Language Model API to prompt how to automatically generate commit messages using AI for users that invoke it, based on the source code changes.<\/p>\n

\"AI-generated<\/a><\/p>\n

What’s next in VS Code Copilot Chat?<\/h3>\n

We are committed to enhancing the extensibility, quality, and customizability of Copilot Chat in VS Code. Stay tuned for exciting updates to make your experience with Chat.<\/p>\n

Some things coming up to look forward to in VS Code, which can be found in the original blog post announcement from the VS Code team<\/a>, include the variable resolving API<\/strong>, which allows extensions to contribute chat variables (via # sign) which provide context from the extension\u2019s domain. Additionally, VS Code expects improvements to intent detection, so that these chat participants are automatically invoked, and to provide GPT-4o language model support.<\/p>\n

Please file any issues or feedback in the VS Code Copilot repo<\/a>, try out building your own developments using Copilot for your extensions, or let us know any VS Code extensions you\u2019d like to see leveraging these APIs.<\/p>\n

To learn more about using GitHub Copilot in VS Code with C++, watch our introduction YouTube video<\/a> and others on the VS Code Channel<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

GitHub Copilot is now more extensible than ever for extension authors in VS Code. At the Microsoft Build conference, we announced that VS Code extensions can now leverage APIs for Copilot to build custom chat participants that users can interact with in the GitHub Copilot Chat view in VS Code. To learn more, please watch […]<\/p>\n","protected":false},"author":85413,"featured_media":34481,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,266,3940,275],"tags":[],"class_list":["post-34409","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus","category-cmake","category-copilot","category-visual-studio-code"],"acf":[],"blog_post_summary":"

GitHub Copilot is now more extensible than ever for extension authors in VS Code. At the Microsoft Build conference, we announced that VS Code extensions can now leverage APIs for Copilot to build custom chat participants that users can interact with in the GitHub Copilot Chat view in VS Code. To learn more, please watch […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/34409","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/85413"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=34409"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/34409\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/34481"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=34409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=34409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=34409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}