VS Code Insiders: Copilot Chat tool reports "sessionId" error even when file operations succeed

[anthonypdawson]

Select Topic Area

Bug

Copilot Feature Area

VS Code

Body

Bug Description:

When using GitHub Copilot Chat to perform file system operations (like creating a file with create_file or editing a file with insert_edit_into_file), the requested action is completed successfully in the VS Code editor. However, the Copilot Chat panel reports a tool error, and the AI model believes the action has failed.

The specific error message is: Cannot read properties of undefined (reading 'sessionId')

This indicates that the VS Code extension is correctly executing the file operation but is failing internally when trying to report the successful status back to the Copilot model.

Steps to Reproduce:

• Open a workspace in VS Code.
• Open a file.
• Open the Copilot Chat panel.
• Ask Copilot to perform a simple file edit, for example: "Can you add a comment to the top of my current file?"
• Observe that the file is correctly edited in the editor.
• Observe that Copilot Chat displays an error message for the tool call.

Expected Behavior:

The file should be edited, and Copilot Chat should show that the tool call was successful, allowing the conversation to proceed based on the successful action.

Actual Behavior:

The file is edited correctly, but Copilot Chat shows an error. The AI model is informed that the tool failed, leading to confusion and requiring the user to manually confirm that the action worked.

System Information:

VS Code Version: Version: 1.104.0-insider (Universal), Commit: 57235e35e5be1ea9db32da9b57862c9ea1880a7f
GitHub Copilot Version: 1.362.1759
Operating System: macOS

Logs:

Below are the diagnostics collected from the GitHub Copilot: Collect Diagnostics command.

Environment

• Plugin: GitHub Copilot for Visual Studio Code 1.362.1759
• Editor: Visual Studio Code 1.104.0-insider
• Operating System: Darwin 24.5.0 (arm64)

Copilot

• Version: 1.362.1759
• GitHub Account: anthonypdawson
• Session ID: 920e3332-dc25-4cdd-add4-8d00471336e71756225461377
• Send Restricted Telemetry: disabled
• Content Exclusion: enabled

Network Configuration

• Proxy: N/A
• Proxy Authorization: N/A
• Proxy Kerberos SPN: N/A
• Proxy Strict SSL: enabled
• Fetcher: Helix
• Number of Root Certificates: 150
• TLS Default Min Version: TLSv1.2
• TLS Default Max Version: TLSv1.3

Reachability

• github.com: HTTP 200
• api.github.com: HTTP 200
• proxy.business.githubcopilot.com: HTTP 200
• api.business.githubcopilot.com: HTTP 200
• telemetry.business.githubcopilot.com: HTTP 200

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