Go 1.26 Overhauls `go fix` Tool: Automated Code Modernization Now Available
Go 1.26 Delivers Completely Rewritten `go fix` Command
The Go team has released version 1.26, featuring a fully rewritten go fix subcommand designed to automatically modernize Go codebases. The new tool applies a suite of analysis algorithms to replace outdated patterns with modern language and library features.
How It Works
Developers can run go fix ./... to apply fixes to all packages beneath the current directory. The command silently updates source files, skipping generated files that should be fixed at the generator level. A -diff flag lets users preview changes before applying them.
“We recommend running
go fixover your project each time you update to a newer Go toolchain release,” said Alan Donovan, a Go team engineer. “Since the command may fix hundreds of files, start from a clean git state so that the change consists only of edits fromgo fix.”
Background: Why a Rewrite?
Prior to Go 1.26, the go fix tool had limited capabilities and was rarely updated. The rewritten version introduces a modular analyzer framework that allows the Go team to ship new checks with each release. It also opens the door for third parties to create custom analyzers.
For example, the new any analyzer replaces interface{} with the any keyword, while mapsloop converts explicit loops over maps to calls to the maps package. The forvar analyzer removes redundant redeclarations of loop variables that were common before Go 1.22.

“Go fix uses a suite of algorithms to identify opportunities to improve your code, often by taking advantage of more modern features of the language and library,” Donovan explained.
What This Means for Developers
With go fix now shipping with every Go release, teams can automatically keep their codebases aligned with the latest best practices. This reduces technical debt and improves code readability without manual effort.
Go maintainers and organizations can also encode their own guidelines into custom analyzers, enabling self-service modernization across large projects. The tool lists available fixers via go tool fix help, showing checks like fmtappendf (replace []byte(fmt.Sprintf) with fmt.Appendf) and hostport (validate addresses passed to net.Dial).
The Go team encourages developers to run go fix -diff ./... on their projects to see which improvements are available in the 1.26 release.
Related Articles
- Exploring Alan Turing's Legacy Through 'Breaking the Code' in Cambridge, MA
- Modernizing Go Code with the Revamped go fix Command
- Microsoft Opens a Historic Chapter: 86-DOS Source Code Released 45 Years Later
- Go 1.25 Launches Flight Recorder: Real-Time Diagnostics for Production Services
- The Slow Pace of Programming Innovation and the Sudden Rise of Stack Overflow
- Modernizing Go Code with the New go fix Tool: Your Questions Answered
- GitHub Strengthens SSH Security with Post-Quantum Key Exchange: What You Need to Know
- Pyroscope 2.0: Accelerating Continuous Profiling with Enhanced Scalability and OTLP Support