Increasing problems with ChatGPT 5.2 in Code Spaces

[LostLogic]

Select Topic Area

Bug

Body

When working in spaces - the shared files in the space has always been easily available to whichever LLM model I've chosen.
But recently, ie - past month - it's become more and more tedious.

I keep getting the following replies whenever I work with files that are more than 50+ lines of code / markup:

The file content shown is heavily truncated (a lot of markup missing). So I cannot verify:
Whether you have required validation for Title and Description
Whether Model.Kind is actually bound to a dropdown/radiolist
Whether bug-specific fields (StepsToReproduce, Expected, Actual) are shown only when Kind == Bug (you started this pattern and it is correct)

When I tell it to pull code from the repo directly, it will usually do so - but needs to be prompted to perform the operation. It doesn't assume the data is invalid if it's garbled / stripped - so I need to either tell it to re-pull or give it an OK for it to re-read the file from the repository.

The MainLayout.razor file attached here is heavily minified/stripped of markup (lots of whitespace but not actual component tags), so I cannot reliably place the button “next to” it without seeing the real markup in the repo’s current master.
If you want, I can re-read MainLayout.razor from GitHub at master and base the placement on that.

This makes it very difficult to work with LLMs in code spaces as I constantly need to assume it's not seeing the full picture and have to verify end of code snippets etc.

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