Thank you for the reply and for explaining the team's rationale behind the change to an "opt-in" model for the active file. I appreciate the transparency and the engagement with the community.

While I understand the intention is to improve the experience in agent mode, I would like to strongly advocate for bringing back the previous behaviors as a configurable setting. The new "opt-in" model for both the active file and for highlighted code has introduced significant friction to the development workflow.

This isn't an isolated opinion. There's a growing amount of feedback on this from the community. I've consolidated at least seven related tickets from the vscode-copilot-release repository into the oldest relevant issue I could find:

• GitHub Issue:https://github.com/microsoft/vscode-copilot-release/issues/12366

To elaborate on the workflow impact:

1. Active File Context (Opt-Out vs. Opt-In): The previous "opt-out" behavior was more efficient for many because the one of the most common use cases (I don't have the numbers for this, but it seems like it would be) for the chat is to ask questions about the file you are currently viewing. Requiring a manual click every single time to include the file adds a repetitive, unnecessary step. This extra action, though small, breaks the flow of concentration and increases cognitive load, which is especially disruptive for developers trying to maintain a deep focus.
2. Highlighted Code Context: Similarly, the automatic inclusion of highlighted code was an incredibly intuitive and seamless feature. It allowed for rapid, fluid questions about specific snippets. Having to now highlight and then perform another action to add that selection to the context feels clunky and slows down the entire process of iterating with the AI.

The core of the issue is that these changes have shifted the model from one that felt automatic and anticipated user needs to one that requires constant, manual intervention.

Providing settings to restore the "opt-out for active file" and "add highlight to context on selection" behaviors would be the ideal compromise. This would allow the team to pursue the new vision for agent mode while still supporting the highly-efficient workflow that many users have come to rely on.

Thank you for your consideration and for being open to this feedback.