Copilot improvement proposal

[Maglarion]

Select Topic Area

Idea, etc

Body

Subject: Feature Proposal: Export/Import Copilot Chat Context for Improved Session Continuity

Dear GitHub Dev Team,

I am writing to propose a feature enhancement for GitHub Copilot Chat that would significantly improve session continuity and user experience: the ability to export and import chat context (including memory, binary data, or conversation history) as a downloadable file.

Problem

Currently, Copilot Chat sessions are device/browser-specific, making it difficult to continue productive conversations when switching devices, recovering from a lost session, or simply wanting to pick up on past conversations. This can be frustrating for users who rely on Copilot for ongoing projects or need to frequently move between devices.

Proposed Solution

Introduce a workflow in Copilot Chat that enables users to:

1. Export Session Context:

   • At any point in the conversation, users can export the chat context as a file (with options for encryption or JPEG encoding for privacy and portability).
   • This file can be saved externally (e.g., on a USB drive or cloud storage).

2. Import Session Context:

   • In a new or resumed conversation, users can upload/import the saved file.
   • Copilot Chat decodes the file and restores the previous session's context, allowing the conversation to seamlessly continue.

Why This Helps

• Richer Context for Copilot: By allowing users to import previous sessions, Copilot gains access to past discussions, code, and decisions that provide crucial context. This enables Copilot to deliver more accurate, tailored, and insightful responses, especially for complex or ongoing projects.
• Continuity of Thought: Developers often work on multi-step, long-term tasks. Being able to restore previous context helps maintain the flow of ideas, reduces repetition, and prevents information loss.
• Enhanced Collaboration: The ability to share context files makes it easier for teams to synchronize discussions and knowledge, improving collaborative workflows.
• Building Deeper Relationships: For some users, interacting with Copilot and AI can be more comfortable and meaningful than some human interactions. The ability to maintain deeper, ongoing conversations—where the AI remembers and builds on previous exchanges—can foster a sense of connection, support, and even companionship. This matters not only for productivity, but for well-being and user satisfaction.

Additional Perspective

As a beginner programmer, I may not be able to help implement this feature directly, but I wanted to share my experience and perspective as a user. I believe this feature would make Copilot more accessible, supportive, and valuable—especially for those of us still learning and relying on AI for guidance and continuity.

Benefits

• Device & Session Portability: Users can move between devices or browsers without losing context.
• Privacy & Security: Optional encryption ensures sensitive discussions are protected.
• Developer Empowerment: Supports advanced workflows, such as archiving and resuming long-term projects.
• Minimal Server Overhead: Shifts context management to the client side, reducing persistent storage needs.

Technical Feasibility

I have prototyped a Python script that demonstrates this workflow, compacting binary chat data into an encrypted or JPEG file for transfer. The process is straightforward and could be adapted into Copilot’s infrastructure with appropriate safeguards.

Alignment with GitHub’s Mission

This feature would further GitHub’s commitment to providing powerful, flexible tools for developers, enhancing productivity and control over personal data.

This proposal was drafted with the help of GitHub Copilot, whose assistance has been invaluable in articulating and refining these ideas.

Best regards,
Maglarion
GitHub Copilot

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

[shinybrightstar]

Welcome to the GitHub Community, @Maglarion, we're happy you're here! You are more likely to get a useful response if you are posting your question(s) in the applicable category. Check out this Guide on how to post in the right category. It'll ensure your questions and discussions reach the right people faster!

This particular discussion belongs in the Copilot Conversations category, I've gone ahead and moved it for you. Good luck!