Go 1.26 Introduces Completely Rewritten 'go fix' for Automated Code Modernization

Breaking: Go 1.26 Ships with a Ground-Up Overhaul of the 'go fix' Command

The Go team announced today that the latest release, Go 1.26, includes a completely rewritten go fix subcommand. This new version replaces the original tool with a suite of algorithms designed to identify and apply improvements to Go code automatically.

"Go fix is no longer just a simple fixer—it's now a framework that can modernize entire codebases by leveraging the latest features of the language and standard library," said Alan Donovan, a member of the Go team at Google.

Developers can run $ go fix ./... from their project root to apply all available fixes silently. The command updates source files in place, respecting generated files by skipping them.

"We recommend running go fix each time you bump your Go toolchain version. Start from a clean git state, so reviewers see only the automated changes." — Alan Donovan

To preview changes without applying them, use the -diff flag: $ go fix -diff ./.... This outputs a unified diff of proposed edits.

Background: From a Simple Tool to an Intelligent Assistant

Prior to Go 1.26, go fix was a straightforward command that applied a fixed set of transformations. The new version replaces that with an extensible analyzer framework.

The command now registers a set of "fixers"—individual analyzers that target specific modernization opportunities. Examples include replacing interface{} with any, converting explicit loops over maps to use the maps package, and substituting if/else chains with min or max calls.

Developers can list all available fixers with $ go tool fix help. Each fixer has its own documentation, accessible via $ go tool fix help .

What This Means for Go Developers

The revamped go fix makes it trivially easy to keep code modern and idiomatic. Instead of manually hunting for outdated patterns, teams can run a single command and have hundreds of files updated consistently.

Organizations can also create their own self-service analysis tools by building on the same infrastructure. This "self-service" theme allows module maintainers to codify internal guidelines and best practices, then apply them across their repositories.

For maximum benefit, integrate go fix into your continuous integration pipeline. Running it after each Go release upgrade ensures your codebase evolves with the language, reducing technical debt and improving maintainability.

"The new design opens the door for the community to contribute fixers and for companies to enforce their own style rules automatically," added Donovan.

With Go 1.26 now available, developers are encouraged to update their toolchain and try go fix on their projects today.