# golang/vscode-go: the Go extension for VS Code, and what it actually installs > The Go extension for Visual Studio Code wraps gopls and a set of optional tools behind one status bar. Here is how the pieces fit, how to get a first Go file running, and where the extension stops being the right answer. **golang/vscode-go** — Go extension for Visual Studio Code - Repository: https://github.com/golang/vscode-go - Website: https://marketplace.visualstudio.com/items?itemName=golang.Go - Stars: 4,263 · Forks: 931 - Language: TypeScript - License: NOASSERTION - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/golang-vscode-go ## What golang/vscode-go is for, and who it is not for The extension exists to give VS Code the same depth of Go support a dedicated IDE would provide, without asking the editor to understand Go itself. Everything language-aware is delegated: the README states that the extension depends on go, gopls (the Go language server), and optional tools depending on your settings. The extension is the glue, the UI, and the command surface. That design decides who benefits. If you already live in VS Code and write Go, you get completion, code navigation, formatting, import organization, diagnostics from build, vet and lint, plus testing and debugging support, all inside the editor you already use. If you want a single binary that owns the whole toolchain, this is the wrong shape: the extension prompts you to install missing tools rather than bundling them. The requirements are narrow and worth checking first. VS Code 1.90 or newer, or an editor compatible with VS Code 1.90+ APIs. Go 1.21 or newer. A machine that can fetch gopls if it is not already present. ## How the extension, gopls and the optional tools divide the work The architecture is a delegation chain. VS Code loads the extension, the extension starts gopls as the language server, and gopls does the analysis that produces completions, definitions and diagnostics. The extension's own job is to translate between the editor's protocol and the Go toolchain, and to expose commands. The status bar is the visible part of that chain. Opening any Go file or go.mod file activates the extension, and the Go status bar appears in the bottom right corner of the window showing your Go version. The README describes a lightning-bolt sign next to the Go version that indicates the language server is running. If gopls is missing, the extension tries to install it. That install path is where a first run can stall, because it needs network access and a writable Go tool directory. Syntax highlighting sits outside this chain on purpose. The README notes that the default highlighting for Go files comes from a TextMate rule embedded in VS Code, not from this extension. For better results it points at semantic highlighting through gopls' ui.semanticTokens setting. Telemetry is the last piece of the mechanism. The extension relies on Go Telemetry to learn about performance and stability of both the extension and gopls. Uploading is disabled by default, and enabling it is a separate command the user runs. That is a sensible default, and it also means a fresh install reports nothing until someone opts in. ## Installing the extension and running your first Go file The README's quick start is three steps: install Go 1.21 or newer, install the VS Code Go extension from the marketplace, then open any Go file or go.mod file to activate it. Nothing is configured by hand at that point; the extension reacts to the file you opened. After installation, open a Go file and check the bottom right corner. You should see the Go status bar with your Go version, and the lightning-bolt sign once the language server is running. If gopls was missing, the extension attempts to install it during this activation. The README also documents the "Go: Install/Update Tools" command for installing additional tools and updating them later. Semantic highlighting is not on by default. The README recommends turning on gopls' ui.semanticTokens setting for better highlighting than the embedded TextMate rule provides: ```json "gopls": { "ui.semanticTokens": true } ``` To run the file, use the integrated terminal and the go command you installed; the extension follows editor conventions rather than inventing its own. Debugging has its own configuration path, and the README links a debugging troubleshooting guide for when a launch configuration does not behave as expected. If you want new features before they are stable, the README documents a pre-release channel. The version scheme distinguishes the two: an odd minor number is pre-release, an even minor number is stable. In the extension management page you select "Install Pre-Release Version", or "Switch to Pre-Release Version" if the extension is already installed. ## Where the extension falls short The first limitation is environmental. The extension needs VS Code 1.90 or newer and Go 1.21 or newer, and it needs gopls. On a locked-down machine where the editor cannot download a language server, the headline features do not degrade gracefully; they are simply not there. The README's answer is the "Go: Install/Update Tools" command, which assumes you can reach the network. The second is that the extension is not the source of truth for Go syntax colors. If your complaint is that Go code looks wrong in VS Code, the README points at a TextMate rule embedded in VS Code, and the fix it suggests is enabling semantic tokens through gopls. That is a different component from the one you installed. The third is workspace layout. Module mode removes the old requirement that code live under GOPATH, but projects with multiple modules or uncommon layouts still need workspace folders configured, and the README defers the details to a supported workspace layouts document. If your repository is a monorepo with several go.mod files, plan for that configuration step rather than expecting it to be inferred. Finally, the extension is not a build system or a task runner. It surfaces build, vet and lint errors as you type or on save, but the commands that produce them come from the Go toolchain. If you want a single tool that owns compilation, testing and packaging end to end, you are assembling that yourself. ## gopls in the editor versus the go command in a terminal The real alternative is not another extension; it is not using an extension at all. The go command already provides build, test, vet and format from the terminal, and gopls can run as a standalone language server for any editor that speaks the protocol. Choosing that route means you own the wiring: you start the server, you point your editor at it, and you decide when tools update. The difference in approach is who manages the toolchain lifecycle. The extension automates discovery and installation of gopls and the optional tools, and gives you a command palette entry to install or update them. The bare setup leaves that to you, which is more work but also more predictable on machines where automatic downloads are blocked or where you pin tool versions for reproducibility. There is a middle path the README itself supports: keep the extension for editing and debugging, but treat the terminal as the place where you run go test and go build. Nothing in the extension prevents that, and it avoids depending on the extension's task integration for the parts of your workflow that must be identical in CI. ## Maintenance, releases and the licence question The repository is not archived, and the last push was on 2026-09-19. Recent releases are v0.56.1 on 2026-08-27, v0.56.1-rc.1 on 2026-08-26, and v0.57.2 on 2026-08-18. The presence of both a release candidate and a stable release in the same window matches the documented pre-release scheme, where the minor version number tells you which channel you are on. The upgrade cost is mostly the extension's own update, plus whatever gopls and optional tools the new version expects. The README gives you "Go: Install/Update Tools" as the mechanism for the second part, and the pre-release channel as the way to try changes early. Running pre-release means odd minor versions, and the README frames that as early access to features and bug fixes rather than as a supported default. Licence is the part the repository does not settle on its own. The repository carries a LICENSE file and the GitHub metadata reports the licence as NOASSERTION, which means the platform did not classify it automatically. Read LICENSE in the repository before you depend on the extension in a commercial setting, and note that the tools it installs are separate projects with their own terms. That is a reading task, not a conclusion anyone else can draw for you. ## Telemetry: off until you turn it on Telemetry deserves its own section because it is the one setting where the extension's behaviour is opt-in and the README is explicit about it. Go Telemetry data uploading is disabled by default. The extension relies on that telemetry to learn about the performance and stability of the extension and gopls. Enabling it is a command you run yourself: ```bash go run golang.org/x/telemetry/cmd/gotelemetry@latest on ``` After enabling, the README states the language server uploads metrics and stack traces to telemetry.go.dev. You can inspect what is collected and what would be uploaded before or after deciding: ```bash go run golang.org/x/telemetry/cmd/gotelemetry@latest view ``` The go.mod file confirms the dependency is present in this repository, requiring golang.org/x/telemetry. If your organisation forbids outbound telemetry, the default state already satisfies that, and the view command is the way to confirm what a colleague with telemetry enabled would be sending. ## Conclusion Adopt golang/vscode-go if you already edit Go inside VS Code and want IntelliSense, debugging and test integration in the same window; the extension is published by the Go team and its last push was on 2026-09-19. Do not adopt it if you need a lightweight editor with no language server process, or if you cannot install gopls and the optional tools on the machine. Before committing, verify that your VS Code build is 1.90 or newer, that Go 1.21 or newer is on PATH, and that you understand the Go Telemetry mechanism, which stays off until the gotelemetry command is run. ## FAQ ### What is the VS Code Go extension (golang/vscode-go)? It is the Go extension for Visual Studio Code, providing language support for Go through gopls and a set of optional tools. It requires VS Code 1.90 or newer and Go 1.21 or newer. ### How do I install the golang/vscode-go extension? Install it from the marketplace listing, then open any Go file or go.mod file to activate it. The Go status bar appears in the bottom right corner of the window and shows your Go version. ### Why is Go to definition not working in VS Code with golang/vscode-go? Code navigation comes from gopls, the language server the extension depends on. The README states the extension tries to install gopls if it is missing, and the lightning-bolt sign next to the Go version indicates the language server is running; if that sign is absent, the server is not up. ### Is the golang/vscode-go extension still maintained? The repository is not archived and the last push was on 2026-09-19. Recent releases include v0.56.1 on 2026-08-27 and v0.57.2 on 2026-08-18. ### Does golang/vscode-go collect telemetry by default? No. The README states Go Telemetry data uploading is disabled by default and can be enabled with the gotelemetry command. Once enabled, the language server uploads metrics and stack traces to telemetry.go.dev. ### How do I get pre-release features in the golang/vscode-go extension? The extension uses the minor version number to distinguish channels: odd numbers are pre-release and even numbers are stable. In the extension management page you select "Install Pre-Release Version", or "Switch to Pre-Release Version" if it is already installed. ## Sources - [golang/vscode-go on GitHub](https://github.com/golang/vscode-go) - [Issues](https://github.com/golang/vscode-go/issues) - [Project website](https://marketplace.visualstudio.com/items?itemName=golang.Go) - [README](https://github.com/golang/vscode-go/blob/master/README.md) - [Releases](https://github.com/golang/vscode-go/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/golang-vscode-go