Granting Sufficient Permissions to a Copilot Extension

[andrewlayer]

Describe the bug
In a fresh chat (and after hard refreshing the browser) we get the following issue:

The error message seems to be indicating that the Github Copilot extension is asking for insufficient permissions when being installed. here are the permissions requested when installing the application:

To Reproduce
Steps to reproduce the behavior:

1. Install buildwithlayer (You will receive a 40X error because we just use this app to test and intercept requests).
2. Delete all existing chats, and start a new one with @buildwithlayer as the participant

Expected behavior
No error or warning. Also, we do not actually receive the content. Here is an example payload that we receive at our route with all these permissions enabled:

payload.json

As you can tell, the repo context is still redacted.

Desktop (please complete the following information):

• Tested in github.com, on multiple browsers (arc, chrome)
• Tested on mac (but unlikely to be the issue)

Additional context
This is is installed at both the personal and organizational level. My account is owned by an organization that has the same "all read permissions granted"

[theodoracheng]

@andrewlayer when testing in the browser, what page do you have open? That error is shown when a reference is passed that the extension does not have access to and is simply a warning.

I see the extension is installed at both the personal and organization level. Just to confirm, that means an org admin installed has installed the extension at the org account level?

[andrewlayer]

So this happens anytime I open a new chat after having refreshed the browser and made a new chat. It only happens on the first message. It also happens for all extensions (I got the same issue with Docker and Mermaid Charts)

Yes, both the organization & the user of the account have the extension installed.

[theodoracheng]

@andrewlayer what page do you have open when refreshing the browser? When using the chat, we send an implicit resource to the extension based off of what is showing in the page. So if the extension doesn't have access to the resource on that page, it would show that error. If the extension is installed at the org admin and individual account level, that error should not show when those resources are displayed on the page.