[Feature]: vscode extension - AI features should be disabled when `chat.disableAIFeatures` is enabled

[DetachHead]

🚀 Feature Request

these "Context for AI" dropdowns are useless for me because i don't use any AI tools (they also never actually seem to contain anything?). i have chat.disableAiFeatures enabled in vscode, which disables copilot and all other AI related functionality. playwright should respect this setting too

Example

Motivation

• i'm in a corporate environment where we're not allowed to use AI tools
• i also don't want any AI related features in my IDE

[rahulsinghpharthyal]

Hi! I think this is a great and practical feature request. If the core team decides to accept this and move forward, I would love to pick this up as my first open-source contribution. Let me know if I can help out with it!

[github-actions]

Thanks for the report — this is a reasonable request, and it's not currently implemented.

The "Context for AI" block is the error-context attachment (a page snapshot captured at failure) that the VS Code extension appends to the test failure message. It's added unconditionally whenever a failing test has an error-context attachment — see extension.ts (_extractAIContext / _testMessageFromText):

if (aiContext)
  markdownString.appendMarkdown(`<br><br><details><summary>Context for AI</summary>\n${aiContext}\n</details>`);

Nothing in the extension currently reads chat.disableAIFeatures, so the block shows up regardless of the user's AI settings.

chat.disableAIFeatures is a real, window-scoped boolean setting in VS Code ("Disable and hide built-in AI features provided by GitHub Copilot"), so gating the block behind it is straightforward — read workspace.getConfiguration('chat').get('disableAIFeatures') and skip appending when it's true.

Two things worth deciding as part of this:

• Whether to hide only the "Context for AI" disclosure, or the underlying snapshot capture / attachment surfacing as well.
• The setting is window-scoped and can change at runtime, so the extension would want to react to onDidChangeConfiguration rather than reading it once at startup.

Marking as a valid feature request for the VS Code extension.

[rahulsinghpharthyal]

Thanks for the exact pointers! Could you please assign this to me? I will start working on extension.ts handling both the disclosure and the onDidChangeConfiguration event.