Improve GH Copilot desktop app and Openspec integration + add chat inline md preview support

[aautere]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

I'm currenty using openspec workflow with copilot desktop app. Copilot app and openspec both are great. And the experience with Copilot in VS Code with openspec is really good. Recently I have been moving to Copilot desktop app and I have faced some issues with the app and opespec.

It would be awesome if copilot would know better how to handle and display (preview) opencode original artifacts.

The challenge is that by default copilot saves the artifacts to~/.copilot/openspec which is outside of the repository and thus the files are not visible for the user. When the user opens a file that the copilot links the artifact md file is opened in the app as a scratch copy of the file to the session. Usually the copy is opened in md edit mode, where the md is hard to read as it is not in preview mode and copilot does not support md preview when the md is opened in chat.

What is even more frustrating is that copilot may not always clearly state that it opened a scratch copy, not the original file. The user may easily miss this and start modyfying the file without realising that this file is a copy and modifying does not result in changing the actual requirements/specification/design. This leads to rework and confusion.

User can create workarounds (skills, guidelines and copy scripts and what not), but it would be much better to include support for better integration for openspec and chat inline md preview feature.

Thanks,
Aleksi

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