microsoft/vscode

Choose this fork if you want a customized, AI-centric IDE and can accept significant divergence from upstream VS Code. Avoid it if you need close upstream parity, frequent security and bugfix updates, or the lowest-risk maintenance path.

Choose this fork if you want an opinionated AI-first editor and are comfortable owning a heavily diverged VS Code base. Avoid it if you need close upstream parity, fast security/bugfix intake, or minimal maintenance burden.

Choose this fork only if you need its specific legacy customizations or test/perf work. For general editor use, extension development, or a maintainable product base, upstream VS Code is the better default because this fork is stale and materially diverged.

Choose this fork if you want a branded, cross-platform IDE distribution centered on Chinese ecosystem workflows and can accept major upstream lag. Avoid it if you need current VS Code features, low maintenance overhead, or easy upstream compatibility.

Choose this fork if legacy Windows support matters more than staying current with upstream VS Code. Avoid it if you want the latest features, fastest security updates, or low-maintenance upstream compatibility.