Unity scripts created with Copilot in Visual Studio are placed under "Timeline" assembly instead of correct assembly

[NeriDavid1]

Select Topic Area

Bug

Copilot Feature Area

Visual Studio

Body

Hi,

I’m experiencing a consistent issue when using GitHub Copilot with Visual Studio for Unity development. Whenever I generate a new C# script using Copilot in Agent Mode, the script is placed in the correct folder in my Unity project, but Visual Studio assigns it to the Timeline assembly instead of the expected assembly definition.

This causes a lot of compiler errors and makes the generated script essentially unusable until I manually move or fix the assembly references. Because of this, Copilot in Visual Studio becomes very difficult to use for Unity projects.

Steps to reproduce:

Open a Unity project in Visual Studio with GitHub Copilot enabled.

Use Copilot (Agent Mode) to create a new script.

Observe that the script is created in the correct folder, but it appears under the Timeline assembly instead of the project’s main assembly.

Expected behavior:
Scripts generated by Copilot should be placed under the correct Unity assembly (e.g., Assembly-CSharp or the appropriate .asmdef) instead of being forced into the Timeline assembly.

Actual behavior:
Scripts are consistently created under the Timeline assembly, which results in numerous compilation issues.

Environment:

IDE: Visual Studio (latest version)

Copilot: Enabled with Agent Mode

Unity: 6

OS: Windows 11

Impact:
This breaks the workflow for Unity developers, since Copilot-generated scripts cannot be used without manual fixes.

thanks !

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