Feature Request: Enable Copilot Chat IDE Extension to Index and Search Copilot Spaces Source Files

[eglauko]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

API

Body

Hi,
Currently Copilot Spaces are very useful for sharing documentation and instructions, but the Copilot Chat extension in IDEs (like VSCode) can't read or index files added under the “Source” section of a Space—only those in the actual Git repo. As a result, if an organization centralizes onboarding guides, corporate standards, or specialized Copilot instructions in Spaces, they're not discoverable via @github in Copilot Chat for IDE.

It would be extremely valuable to:

Make all documentation and sources in a Space indexable/searchable by the Copilot Chat extension in the IDE using @github.
Optionally, enable Spaces to export or copy selected files directly to a chosen directory in a target repository.
This would simplify knowledge sharing and maintenance considerably.

Thank you for your consideration!

[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. ⭐

[syedsafeer]

This is a solid feature request! Integrating Spaces directly would solve a lot of onboarding friction.
Until this is natively synced, the current 'Pro' way to achieve this is by using GitHub Copilot Knowledge Bases. You can point a Knowledge Base to the repository or documentation source that feeds your Space. Once indexed, you can use the @github agent in VS Code with the /kb command to query those corporate standards and guides directly.
It’s not a direct Space-to-IDE sync yet, but it’s the most effective way to index non-code documentation for the team right now.