Skip to content

Conversation

Copilot
Copy link
Contributor

@Copilot Copilot AI commented Aug 29, 2025

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 the ChatImplicitContextContribution.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:

if ((setting === 'always' || setting === 'first' && isFirstInteraction) && !isPromptFile && !widget.isLockedToCodingAgent) {
    widget.input.implicitContext.setValue(newValue, isSelection, languageId);
} else {
    widget.input.implicitContext.setValue(undefined, false, undefined);
}

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
    • Triggering command: 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.

Add check for isLockedToCodingAgent in ChatImplicitContextContribution to prevent setting implicit context when a chat widget is locked to a coding agent. This ensures that when opening a Coding Agent Chat in a new window, active files are not included as context.

Co-authored-by: joshspicer <23246594+joshspicer@users.noreply.github.com>
@Copilot Copilot AI changed the title [WIP] Open Coding Agent Chat in new Window should not include active file as context Prevent active file context in locked coding agent chat sessions Aug 29, 2025
@Copilot Copilot AI requested a review from joshspicer August 29, 2025 23:46
Copilot finished work on behalf of joshspicer August 29, 2025 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Open Coding Agent Chat in new Window should not include active file as context
2 participants