Use getChatSessionType for proper session type handling in multidiff content #281369
+12
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses review feedback from #281316: Using
resource.schemedirectly is incorrect for local chat sessions.The
getChatSessionType()function properly handles:vscodeChatEditorscheme → returnslocalChatSessionTypevscodeLocalChatSessionscheme → returnsresource.authorityresource.schemeChanges:
resource.schemewithgetChatSessionType(resource)in context overlayChatContextKeys.agentSessionType.key💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.