Copilot Extensions now in Public Beta #137975
Replies: 13 comments 18 replies
-
|
Feature request - Chat participants, and thus copilot (and copilot chat) extensions, don’t seem to work for inline-chat For example, try @ workspace in an inline chat. This seems to limit ability of extensions, especially since (in my experience), I tend to use more inline chat vs chat view. |
Beta Was this translation helpful? Give feedback.
-
|
That's great feedback @kyleli626! definitely looking into how we support extensions to inline chat :) |
Beta Was this translation helpful? Give feedback.
-
|
I have a question (for the future versions of this beta). Will GitHub send references (such as selected code) to the endpoint along with the history, just like how GitHub Copilot works? Because I need to make a VS Code extension to get the code references from the IDE, but if I do that, the extension adds another participant to the chat and probably I need to implement a separate system within the extension, which would differ from the one my server currently uses to handle requests from GitHub, especially because I get different data from the VS Code API. I also wonder if other chat extension capabilities will be added. Because I would like to send custom buttons, follow-up messages etc. to the chat. And the most disappointing part is I expected to create commands for my Copilot Extension without having to build an IDE extension. I would like to have these features because with the current usage of Copilot Extensions (I also took a look at the dreamcode), we can only provide a chat experience to the users, which is far away from helping to code. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Tolga1452!
Currently, "references" within the scope of extensibility are sent. We are going to support additional context, like selected code, within the next two months. This will apply specifically to Copilot Extensions built as GitHub Apps. For VS Code Chat Participants, selected code is available as context. You can refer to the VS Code documentation for details on VS Code Chat specific capabilities.
Capabilities like custom buttons and follow-up messages are common requests that we're tracking. While these aren't on the immediate roadmap, we are considering these features for future updates. We understand that a lot of builders want more capabilities beyond chat, and we’re actively exploring ways to support deeper integration as we continue building out the platform. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! ❤️ I'm looking forward to the future updates |
Beta Was this translation helpful? Give feedback.
-
|
Does GitHub plan to include references (e.g., selected code) and history in the API for easier integration with extensions like VS Code? |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Thank you for the public beta - it has great potential! I was able to build a simple chat participant VS Code extension using this guide, which sends user queries to our internal LLM and posts the API responses back to the Copilot Chat window. In this scenario, does Copilot read the data from our internal LLM that is posted back to the chat? If so, will this data be treated the same as the prompts and suggestions mentioned in the Trust Center? I am a GH Enterprise user. |
Beta Was this translation helpful? Give feedback.
-
|
As the entire chat is send back and forth, GitHub will see the response you send back to the client. So yes. Also be aware that the response is also send to Azure OpenAI for the content and safety filtering. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, Rob. I assume that the same would apply to any Copilot Chat responses, and the same data privacy policies would be applicable in this case as well. |
Beta Was this translation helpful? Give feedback.
-
|
Are we able to have private extensions created only for our organization organization? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @htekdev. Yes! You can create private extensions at the organization level. The process will be the same as GitHub Apps (here's the link to our docs on how to do that). Currently, we don't support internal enterprise-level apps or extensions that can be shared across multiple organizations under the same enterprise. But this is on our roadmap and scheduled to release during Universe at the end of this month. |
Beta Was this translation helpful? Give feedback.
-
|
Hi VS Code PM here 👋 Just wanted to add to the initial announcement. You can also build Copilot Extensions in VS Code. This is an interesting path if you already have a VS Code extension. More details about this can be found here Thanks 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Hi VS Code extension dev here. My current company only use on-premise LLM, and I was hopping to integrate them in VScode using this lm and chat APIs but I got a little confused using them, could you clarify if
While testing, I triggered some Vscode-native chat dialogs (ex: "workbench.action.openQuickChat") yet my test extension was not called after entering some prompt. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there 👋
Right now no. But these APIs are designed to be generic, and this might change in the future depending on user feedback and potential scenarios.
Design decision we did that we believe makes it easy to extend Copilot on the VS Code side.
I suggest to do these two tutorials to help get started |
Beta Was this translation helpful? Give feedback.
-
|
How Can I Create a Private Extension at the Organization Level? I followed the steps in this documentation to create a private GitHub App for my organization, configured the extension, and installed it in the organization. However, the option for Copilot Chat does not appear with the @ prefix. GitHub Copilot Extension is enabled for my organization, but it does not show up in the options. Interestingly, when I follow the same steps for a personal GitHub App setup, the option appears and works correctly. For testing, I used https://github.com/copilot-extensions/blackbeard-extension, ran it locally, and set up the generated ngrok URL as the endpoint. |
Beta Was this translation helpful? Give feedback.
-
|
@D1M1TR10S should be able to help |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I believe github Copilot Extension feature is not available for Copilot Only Subscriptions for Enterprises. We don't have Github Enterprise accounts . We are not able to Enable the option for copilot extensions from policies. We also can't deploy Github apps or create repositories since we have copilot only accounts. Is there a roadmap to serve this feature for also Copilot Only accounts? This will be a huge leap for us if we have this in our organization. |
Beta Was this translation helpful? Give feedback.
-
|
It's available to everyone with a GH Copilot subscription now. |
Beta Was this translation helpful? Give feedback.
-
|
I'm encountering an issue with the Stack Overflow extension. I added it to my account, but whenever I try to perform a request to it, my IDE reports an error (empty response). This is very strange though, because it seems it has the necessary permissions:
Perplexity AI estension is working on my account, though. When I ask for some info about GitHub Copilot extensions, I get: Any help? |
Beta Was this translation helpful? Give feedback.
-
|
I revoked the Stack Overflow authorization, then I performed again a request to the Stack Overflow extension. I got this answer: Clicking on that link led me to:
I clicked on "Continue", but then a page loaded with this TXT answer (no HTML): Could my issue be related to that? Why it is happening? I own a regular Stack Overflow account. Also, why that Stack Overflow Teams website was opened instead of the "regular" one? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. It seems like API access to stackoverflow is only for paid account with them. But no where in the GH Copilot Marketplace they mention anything about that. This need to be reviewed, as it gives a cryptic error and make people believe that this extension is free to use which is misleading. |
Beta Was this translation helpful? Give feedback.
-
But @hmorneau I suppose this is your hypothesis? |
Beta Was this translation helpful? Give feedback.
-
No, that's according to their documentation: "The Stack Overflow application programming interface (API) allows you to access your Basic and Business Teams data for automation, reporting, and more. Business Teams can use the API to read and write Teams data, while Basic Teams have read-only API access. Free Teams do not have API access." |
Beta Was this translation helpful? Give feedback.
-
|
I am unsure of this StackOverflow extension's usefulness. Initially, I believed it would serve as a search engine to access and summarize StackOverflow posts. |
Beta Was this translation helpful? Give feedback.
-
|
I find the way to find extension confusing. In the copilot chat inside VS Code when you invoke @ you have the option to install chat extensions which search the market place with this tag: @tag:chat-participant |
Beta Was this translation helpful? Give feedback.
-
Copilot Extensions now in Public Beta
We’re thrilled to announce the public beta release of GitHub Copilot Extensions, available starting September 9th, 2024. Whether you’re a developer looking to leverage existing extensions or a builder excited to create new integrations, Copilot Extensions now offers a platform to make that happen. Copilot Extensions allow developers to build or install integrations into Copilot Chat on GitHub.com and all supported editors (Visual Studio and VS Code) to increase productivity by seamlessly integrating external tools and context into the developer workflow.
What's New in the Public Beta?
Get Started Today
Explore the GitHub Marketplace to try a Copilot Extension, or check out our Getting Started Guide to build your own.
Feedback
We’re eager to hear about your experience, as a user or builder, during pubic beta.
For general feedback or feature requests around using and building extensions, please post in the comments below.
For detailed builder feedback to the GitHub product team, fill out the Extension Builders Survey.
For user feedback to a specific extension publisher, please file an issue in the user-feedback repo with a label for the publisher's listing name attached.
Beta Was this translation helpful? Give feedback.
All reactions