Visual Studio Code
A cross-platform code editor with syntax highlighting, completion, debugging, testing, Git, terminals, tasks, extensions, remote development and optional AI features.
What Visual Studio Code is for
Visual Studio Code supports multi-language editing, Git workflows, debugging, testing, terminals and remote development. Extensions add language services and integrations, but the editor is not a compiler and does not make dependencies, extension code or AI output safe by itself.
Version and platform notes
The indexed build is 1.132.0. Choose a package that matches Windows, macOS or Linux and the processor architecture. Linux packages may be provided as DEB, RPM, TAR or Snap assets; platform support and system-library requirements should be checked before installation.
Extensions, trust and data boundaries
The Microsoft-distributed product and the upstream source repository have different licensing and service configurations. Extensions can read a workspace, start processes or make network requests. Workspace Restricted Mode reduces automatic execution for an unfamiliar folder, but it is not an operating-system sandbox. Telemetry settings also do not make updates, extensions, synchronization, remote tools or AI services fully offline.
Maintenance note
This page reviews the 1.132 release line, platform packages, workspace trust, telemetry, extension behavior and remote-development boundaries. Content review date: 2026-08-06.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Visual Studio Code to this cloud drive
Baidu Netdisk
Save Visual Studio Code to this cloud drive
Visual Studio Code 1.132 installation, extensions and workspace trust
Select the package that matches the operating system and architecture. Open a small trusted sample first, confirm the local toolchain, then add only the extensions needed for the project.
Before you start
- Confirm the supported operating system and CPU architecture, and keep the current editor settings and extension list backed up.
- Install the compiler, interpreter or SDK required by the target language and verify its version in a system terminal.
- Treat unfamiliar repositories, tasks, launch configurations and extensions as code that may execute locally.
Installation steps
- 01
Select an installation mode
Choose user, system or portable installation on Windows, the matching DMG on macOS, or a distribution package on Linux. Verify the architecture before launching it.
- 02
Check the base environment
Open a small trusted project and test saving, search, the integrated terminal, Git and the command palette. Confirm the shell, working directory and account are expected.
- 03
Add extensions one at a time
Prefer a clearly identified publisher and a recently maintained release. After each installation, observe activation, processes and network behavior instead of importing an unreviewed extension bundle.
Quick start
- 01
Inspect an unfamiliar project in Restricted Mode
Review tasks, debug settings, workspace files and extension recommendations before trusting the folder. Restricted Mode is a review step, not a complete sandbox.
- 02
Configure build, test and debug tasks
Point tasks at a verified local toolchain, run a small sample and check the working directory, environment variables and exit code before relying on a larger build.
- 03
Set boundaries for AI and remote features
Before enabling AI, SSH, containers or tunnels, confirm the account, subscription, code-transfer path, command approvals and server-side components. Keep production credentials separate.
Usage tips
- Extensions can read workspace files, start processes and access the network; marketplace popularity is not a security audit.
- Workspace trust reduces accidental execution in unfamiliar repositories but does not replace ordinary-user permissions, least privilege and code review.
- Commit current changes before enabling an agent that can edit files or run terminal commands, and review generated changes before accepting them.
Troubleshooting and uninstall
Why does an extension or debugger stop working?
Reproduce the issue with extensions disabled, then inspect the extension-host log, shell, PATH and toolchain versions. If it only happens in one folder, review workspace settings and trust state.
Why did an update change project behavior?
Review the release notes and deprecated settings, temporarily disable experimental features, and restore a known settings backup instead of overwriting the project directory with an unknown old package.
- Export settings and project stateSave settings, keybindings, snippets, extension lists and required tasks. Back up source files, local databases and untracked work independently.
- Uninstall selectivelyRemove the editor through the operating system's application settings. Decide separately whether to keep user data, caches, extensions, Git, SDKs, containers and SSH keys.
Frequently asked questions
Is Visual Studio Code the same license as the upstream vscode source?
No. The Microsoft-distributed product includes its own branding, service configuration and components, while the upstream source uses MIT. Check the terms for the exact build and redistribution plan.
Why can an extension not compile or run my code by itself?
Extensions usually provide editing, language services or debug adapters. The compiler, interpreter, SDK, container runtime and Git often need to be installed and configured separately.
Does turning telemetry off make the editor fully offline?
No. Updates, extension services, settings sync, remote development, AI features and third-party extensions can still use the network and should be reviewed separately.