Prevent active file context in locked coding agent chat sessions #264108
+146
−1
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.
When opening a Coding Agent Chat in a new window, the active file was incorrectly being included as context. This happened because the
ChatImplicitContextContribution
automatically adds active file context to all chat widgets without checking if they are locked to a coding agent.The Problem
The implicit context system would add the currently active file as context to any chat widget, including those that are locked to coding agents. This is undesirable behavior because coding agent sessions should operate independently without automatically inheriting context from the user's current workspace state.
The Solution
Added a check for
widget.isLockedToCodingAgent
in theChatImplicitContextContribution.updateImplicitContext()
method. Now, when a chat widget is locked to a coding agent, no implicit context (active file) will be set.The change is minimal and surgical - only one condition was added to the existing logic:
This preserves all existing functionality for normal chat sessions while ensuring that locked coding agent sessions don't receive unwanted active file context.
Fixes #263505.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
electronjs.org
node-gyp
(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 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.