Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?

Original Article ↗ Hacker News Discussion ↗

Allegation and Context

  • VS Code reportedly has “proposed” / hidden APIs used by GitHub Copilot and some Microsoft extensions.
  • Third‑party extensions are not allowed to use these APIs in the official marketplace, while Copilot can.
  • The binary “Visual Studio Code” distribution includes proprietary pieces; the open-source core (Code‑OSS) is separate.

Anti‑Competitive and Trust Concerns

  • Many see this as classic “embrace, extend, extinguish” behavior, echoing past Microsoft tactics (IE, Windows, Office).
  • Key concern: Microsoft’s own products can ship features (via private/unfinished APIs) that competitors cannot, unless they fork VS Code.
  • Forks lose access to the official marketplace and many Microsoft extensions (Pylance, Live Share, remote dev, etc.), which creates de facto lock‑in.
  • Some argue this undermines VS Code as a neutral platform and shifts it toward a Copilot‑centric ecosystem.
  • Several commenters stress that intent is irrelevant: even if driven by “velocity,” the outcome is anti‑competitive.

Defenses and Alternative Explanations

  • Others say this is standard platform practice: use internal products to test experimental APIs before stabilizing them.
  • VS Code APIs are described as carefully designed and slow to stabilize; some APIs have been “proposed” for years.
  • Some note that VS Code is free, not bundled with Windows, and faces competition from many editors; they question whether monopoly/antitrust applies.
  • A minority argues that competing AI tools can fork VS Code or build their own IDEs and already do so.

Open Source, Forking, and Ecosystem Effects

  • Forks like VSCodium, Cursor, and various cloud IDEs exist, but commenters highlight:
    • No access to the Microsoft marketplace by default.
    • Some key Microsoft extensions are closed or VS Code–only.
    • Maintaining a successful fork is hard; fragmented ecosystems weaken alternatives.

User Reactions and Alternatives

  • Some users are uneasy about growing proprietary pieces, AI‑focus, and telemetry; a few block VS Code’s network traffic or consider VMs.
  • Alternatives mentioned: JetBrains IDEs, Neovim/LazyVim, Zed, Sublime Text, Helix, Lapce, and others using LSP.
  • A number of people remain happy with VS Code’s overall quality and say they’ll keep using it until the experience clearly worsens.