In Github Copilot Chat - How to include all opened files as a context reference

[michaelmiscanuk]

By default only one my opened file is attached as a context. I know there is a way to include files clicking button "Attach Context" a manually selecting files in a list (opened files appear). But this have to be done basically for each prompt. I wonder if there is some better way to include all opened files, probably via some # command (#Editor does not work) or even better via some setting.

Thank you.

[bamurtaugh]

Hi there, thanks for the feedback. Just to double check - where are you using Copilot Chat? In github.com, VS Code, VS, or somewhere else?

[michaelmiscanuk]

In vscode.

[bamurtaugh]

Thanks for clarifying! You could use #codebase to attach your entire codebase, if that would work for you?

[michaelmiscanuk]

Hi, this will not help, i just tried it. I have huge project with many files, I just want to open several, and be it as a context, without explicitly pointing to it or attaching it. #codespace used unnecessary files not currently opened in a context, and weirdly one of my opened files was not in the reference.

See in the screen where i tested it.

Thank you.

[tripl3a]

I have the same issue. It would be really helpful if there was a command to add all the open editors to the context.

[bamurtaugh]

Thank you all for the feedback!

It is actually possible today to add all open editors to the context. You can use Add Context... from the chat panel:

and then select Open Editors:

[bamurtaugh]

Though it sounds like folks may want to automatically include Open Editors in every prompt, without having to select this?

Have you tried using custom instructions to specify this too: https://code.visualstudio.com/docs/copilot/copilot-customization? Custom instructions will be automatically applied to every conversation.

[michaelmiscanuk]

Hi, yes I noticed the "Open Editors" option, thank you, good middle ground :) Didn't try the custom instructions yet.

[impredicative]

@bamurtaugh If I have a prompt file in .github/prompts/, how can I mention it in the prompt file itself to include "Open Editors"? Would referencing #editFiles in my prompt file accomplish it?

[impredicative]

@Angel-William All of those approaches are less specific than manually attaching "Open Editors". Real developers need the LLM to have a specific focused context. This issue is clearly about "all open files" only without having to attach the entire workspace or individual files or folders.

[dmathisen]

This is such a common use case that it should be way quicker/easier to do this - definitely from the keyboard. Typing #openFiles or similar should be available.

[impredicative]

@bamurtaugh How about allowing #editors or #openFiles to add the open editor files? There is nothing in the copilot-customization resource for it.

[zliang-akamai]

Can we have entire codebase as context automatically without adding them one by one, which is super annoying?

[impredicative]

Doesn't specifying #codebase already allow it? It should not be automatic because excessive context is costly and is a distraction. It can also be selected from the Send with #codebase menu choice.

[yasirroni]

In my case, using #codebase did not trigger this for Raptor Mini, but works with Claude Sonnet 4.6. Do you know why?

[EddieGreen]

Will not help VS Code users but I've just published an extension for VS 2022 that copies selected files in the solution explorer to the clipboard as references that can be pasted into the chat.

See Copy CoPilot References

Copy CoPilot References Extension

This Visual Studio extension simplifies referencing files in GitHub Copilot Chat by copying their relative paths to the clipboard, formatted for immediate use.

How to Use

1. In the Solution Explorer, select one or more files.
2. Right-click the selected file(s) to open the context menu.
3. Click on "Copy CoPilot references".
4. The formatted references (e.g., #file:'YourProject/YourFile.cs') are now on your clipboard.
5. Paste the text directly into the GitHub Copilot Chat window.

Features

• Single & Multi-file Selection: Copy references for one or multiple files at once.
• Correct Formatting: Automatically formats the paths with the #file:'...' syntax required by Copilot Chat.
• Relative Paths: Generates paths relative to the solution directory for cleaner references.
• Easy Access: Integrates directly into the Solution Explorer item context menu for a seamless workflow.

[nooogle]

I've just tried this and it's great! (I had to rebuild the extension to support ARM64 as I'm on a VM on OSX, otherwise no issues.)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[dmathisen]

I'm glad this is getting attention. I think the #editors or #openFiles suggestion deserves attention :)

https://github.com/orgs/community/discussions/155219#discussioncomment-13805534

[pramaat]

note sure if this is solution in chat settings but i will continue like this. Later might remove it, please do remind

[pramaat]

not working, thrown