Feedback: Copilot Chat Multi-end Sync & Large File Context Issues

[RickyYang0325]

Select Topic Area

Product Feedback

Copilot Feature Area

Visual Studio

Body

1. Lack of Chat History Synchronization Across Devices

Problem:
When using Copilot Chat on different platforms (e.g., VS Code extension, web-based GitHub Copilot Chat), conversation history is not synchronized. Chats started in VS Code are not visible in the web interface, and vice versa.

Suggestion:
It would be highly beneficial if chat history were unified at the account level, so users could seamlessly continue conversations regardless of the platform or device. Cloud-based history, or an import/export feature, would also be helpful.

---

2. VS Code Copilot Chat Breaks When Referencing Large Files

Problem:
When I reference a large file as context in a Copilot Chat session in VS Code, the following issues occur:

• VS Code becomes extremely slow, with high system resource usage or even freezing.
• Any further message sent in the chat results in errors such as HTTP2_PROTOCOL_ERROR.
• Opening a new chat session works normally again, but the original chat remains unusable.

Possible Causes:

• The backend may be exceeding memory or request size limits when processing large context files.
• The VS Code extension might not gracefully handle resource exhaustion or backend errors.

Suggestion:

• Optimize large file handling (chunking, summarization, or limiting context size).
• Provide clear warnings or restrictions when users try to add excessively large files.
• Ensure that chat sessions recover gracefully from such errors, rather than becoming permanently unusable.

---

Environment:

• GitHub Copilot Chat (VS Code extension, and web)
• Same GitHub account across devices
• Most recent versions of VS Code and Copilot extensions

Thank you for considering these improvements! Copilot Chat is already extremely useful, and resolving these issues would make it even better.

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