[Bug] Reference files not getting sent to only one of two copilot extensions (same settings, same code)

[chrisyxlee]

Describe the bug
We have 2 Copilot extension apps. Same code and settings, two different environments and GitHub app instances.
Our DEV app receives the reference files just fine.
Our PROD app doesn't receive any reference files, but the PROD app was receiving reference files 3 weeks ago.

To Reproduce
Steps to reproduce the behavior:

1. Authorize the Copilot extension on my GitHub user.
2. Install the Copilot extension into my org, allowing it access to only my target repository.
3. Open VS Code.
4. Start new chat
5. @<extension> do thing
6. See that the chat message is missing reference files in the logs

Expected behavior
The PROD app should be receiving reference files

Screenshots

The chat message at 2025-01-06T21:20:37.660973415Z:

When it was working at 2024-12-18T22:20:47.224846352Z (about 3 weeks ago):

---

It is currently working with our DEV app (same code and settings, different GH app instance)

Timestamp: 2025-01-06T21:34:53.253350074Z

Desktop (please complete the following information):

• OS: Mac OS Sonoma 14.3
• Browser: Chrome
• Version 131.0.6778.109

Additional context
Add any other context about the problem here.

[chrisyxlee]

For posterity, it seems like it was a permissions issue with VS Code. I somehow got it to trigger the "allow workspace access to extension" by forcing an error in the extension?

And here's the additional information VS Code provided - https://code.visualstudio.com/docs/copilot/copilot-chat#_extensioncontributed-chat-participants

Still no idea how to reliably trigger the VS Code prompt though... 😅

I filed this instead:

• Bug: Copilot extension did not trigger "Grant access to editor context" on first mention microsoft/vscode-copilot-release#3906