VSCode Agents should not be a marketing tool for Copilot

I wish to complain about Microsoft’s decision to restrict or gate VS Code’s integrated agent functionality behind a GitHub Copilot subscription when the agent being used is supplied and paid for independently.

I use Visual Studio Code as my development environment and already subscribe to, and use, third-party coding agents including OpenAI Codex and Anthropic Claude Code. I have no requirement for GitHub Copilot and do not wish to purchase a Copilot Pro subscription.

VS Code is increasingly presenting an integrated “Agents” experience which appears, from a user’s perspective, to be a general-purpose framework for running coding agents. However, access to parts of that interface and functionality has been tied to GitHub Copilot subscriptions, even where the underlying agent is not Copilot and where the user already has a direct subscription to the third-party provider.

I consider this an unreasonable product restriction.

There is a legitimate distinction between charging for Microsoft's own AI service and charging for VS Code functionality. If I ask Microsoft to provide inference, models, compute capacity or other Copilot services, then requiring a Copilot subscription is entirely understandable.

That is not what I am asking for.

I want VS Code to act as the development environment and user interface for agents for which I already have separate access and subscriptions. In that situation, Microsoft is providing the editor integration, not the AI service itself.

Requiring me to buy GitHub Copilot Pro merely to make full use of VS Code's agent interface with Codex or Claude Code amounts, in practical terms, to bundling Microsoft's paid AI product with access to editor functionality that should be independent of the choice of AI provider.

This is particularly disappointing given VS Code's history as an open and extensible development environment. Developers have traditionally been able to choose their compilers, source-control providers, language servers, debuggers, extensions and other development tools independently. AI coding agents should follow the same model.

I would therefore ask Microsoft to adopt a clear separation between:

1. **VS Code agent-host functionality**, which should be available to VS Code users independently of a Copilot subscription; and
2. **GitHub Copilot services**, for which a Copilot subscription can reasonably be required.

Users should be able to authenticate directly with OpenAI, Anthropic and other supported agent providers and use those agents through the VS Code agent interface without purchasing a redundant GitHub Copilot subscription.

I appreciate that Microsoft appears to be moving partially in this direction with newer Agent Host functionality and provider-native authentication. However, the current experience remains confusing and unnecessarily restricted, with some capabilities and documentation still treating Copilot as a prerequisite.

I would therefore like Microsoft to:

* remove any Copilot subscription requirement for VS Code agent functionality where Microsoft is not supplying the underlying AI service;
* allow direct provider authentication throughout the VS Code Agents experience;
* ensure custom VS Code agents can invoke supported third-party agent harnesses without requiring Copilot;
* clearly distinguish in the UI between functionality supplied by VS Code and services supplied by GitHub Copilot; and
* avoid designing future VS Code agent functionality in a way that makes Copilot a compulsory intermediary for competing AI services.

I am not requesting free access to GitHub Copilot. Quite the opposite: I do not want to use GitHub Copilot.

I simply want to be able to use the AI services I have independently chosen and paid for within my chosen development environment, without being required to purchase Microsoft's competing AI service as an additional prerequisite.

I would appreciate this complaint being passed to the VS Code product team responsible for the Agents architecture and commercial integration with GitHub Copilot, and I would welcome a substantive response explaining Microsoft's intended policy for third-party, independently authenticated coding agents in VS Code.