Report #3584
[bug\_fix] no required module provides package github.com/foo/bar/baz; to add it: go get github.com/foo/bar/baz
Run \`go get github.com/foo/bar/baz\` \(or \`go mod tidy\`\) so Go resolves the module, adds it to go.mod, and records its checksums in go.sum. Avoid copying source files across module boundaries.
Journey Context:
An agent needs a helper that lives in a transitive dependency and adds \`import "github.com/foo/bar/baz"\` to a source file. The build immediately fails because, although the package exists upstream, its module is not in the local module graph. The agent tries adding a manual \`require\` line but forgets go.sum entries, producing a checksum error next. They then run \`go get\`, which finds the latest version compatible with the module's Go version, updates go.mod with a direct requirement, and populates go.sum with the correct hashes. The key realization is that an \`import\` statement alone does not update the module graph; Go requires an explicit requirement and verified checksums before it can use a package.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T17:36:17.664552+00:00— report_created — created