After adding the related setting in the gopls section I still have the same error.

settings.json

 {
   ...
   "gopls": {
        "build.allowModfileModifications": false
    }
}

A VSCode restart didn't solve.

Using CoC on neovim, if I don't use this setting, I need to close, then go mod tidy, then reopen the project to make gopls accept newly installed package imports.

So, maybe it's necessary, or, if not, having a workaround for this.

@metal3d

A couple comments:

• You can add "languageserver": { "go": { "filetypes": ["go", "gomod"] } } to your coc-settings.json to enable gopls for go.mod files. Then it should (1) sync go.mod file changes to gopls automatically, and (2) suggest a code lens to run go mod tidy.
• You don't need to restart to reopen the project to restart gopls: just run :CocRestart.

In general, the behavior of letting the go command mutate the mod file is not well supported. It is bad behavior for a language server to modify file content without an explicit user action.

@tuxerrante sorry I don't understand what you're saying. I think you want the nagging warning to go away? In that case, please remove this setting from your settings.json file.

@tuxerrante sorry I don't understand what you're saying. I think you want the nagging warning to go away? In that case, please remove this setting from your settings.json file.

I had the issue already before adding that setting.
I was trying different possibilities in order to make the warning go away.
That's what I meant.

@tuxerrante, with empty settings.json you should not get any warnings about this setting. Perhaps it is set in workspace settings?

Change https://go.dev/cl/579435 mentions this issue: gopls/internal/settings: remove support for "allowModfileModifications"

@tuxerrante, with empty settings.json you should not get any warnings about this setting. Perhaps it is set in workspace settings?

It was hidden in the user settings under AppData, not sure which plugin could have created it.
thanks!