Go 1.26 Unleashes Completely Rewritten 'Go Fix' Tool to Modernize Codebases

Breaking: Go 1.26 Ships with Revamped 'go fix' Subcommand

The Go team has released version 1.26 of the Go programming language, featuring a fully rewritten go fix subcommand designed to automatically identify and apply modernizations to existing codebases. The update, announced on February 17, 2026, promises to streamline the adoption of newer language and library features across projects of all sizes.

Go 1.26 Unleashes Completely Rewritten 'Go Fix' Tool to Modernize Codebases — Source: blog.golang.org

“This is a game-changer for Go developers,” said Alan Donovan, a Go team member and author of the official announcement. “The new go fix doesn't just patch bugs—it actively helps you keep your code idiomatic and maintainable by leveraging the latest Go capabilities.”

The command works silently on source files, preserving generated code by skipping fixes that would alter such files. Developers are urged to run go fix ./... after each Go toolchain upgrade, starting from a clean Git state to isolate the changes.

How to Use the New go fix

To modernize all packages under the current directory, simply run $ go fix ./.... The command applies a suite of built-in fixers without user intervention. For a safe preview, the -diff flag shows proposed modifications before committing them.

For example, the “any” fixer replaces interface{} with any, while “fmtappendf” converts []byte(fmt.Sprintf) calls to fmt.Appendf. A complete list is available via $ go tool fix help.

“We designed go fix to be a self-service platform,” Donovan explained. “Maintainers and organizations can now encode their own guidelines and best practices into the tool, making code modernization a continuous, automated process.”

Background

Prior to Go 1.26, go fix had limited scope and required manual intervention for many common refactorings. The rewrite addresses long-standing community demand for a more intelligent, extensible fixer that keeps pace with the language’s evolution.

The infrastructure powering the new command is built on a pluggable analyzer framework. Each fixer targets a specific pattern—such as redundant loop variable shadows (fixed by “forvar”) or outdated build tag formats (“buildtag”). This modular approach allows the Go team to ship new fixers rapidly as the language grows.

What This Means for Go Developers

The upgraded go fix significantly lowers the friction of adopting newer Go idioms. Instead of manually scanning for outdated patterns, teams can integrate the command into their CI/CD pipeline, ensuring codebases remain modern with minimal effort.

For enterprise projects and large open-source repositories, this translates to reduced technical debt and fewer regressions. The ability to run fixers selectively (e.g., only minmax to replace if/else with min/max) gives developers fine-grained control.

Donovan emphasized the long-term vision: “We want go fix to be the default tool for any Go modernization task. By making it extensible, we’re empowering the entire ecosystem to contribute to code quality.”

Getting Started Immediately

To take advantage of the new capabilities, upgrade to Go 1.26 by visiting go.dev/dl. After installation, run go fix ./... on your project and review changes with go fix -diff. The Go team recommends running the tool after every toolchain update to keep your code fresh.

For a deeper dive into the analyzer architecture, see the original announcement on the Go Blog. The official documentation at go tool fix help provides detailed descriptions of each fixer.

Conclusion

Go 1.26’s rewritten go fix marks a milestone in automated code modernization. With its extensible design and comprehensive fixer suite, the tool empowers developers to maintain idiomatic, high-quality code with ease. As Donovan noted, “The future of Go development is about proactive maintenance, not reactive fixes.”