- Accepted the "LSP plugin recommendation" prompt for `gopls-lsp` — it re-prompted a second time in a later session despite prior acceptance, and no LSP functionality (go-to-definition, diagnostics) appeared after accepting either time. - `gopls` itself is already installed and on `PATH` (`~/.go/bin/gopls`, v0.18.1), so this looks like a Claude Code plugin-registration bug, not a missing binary. - Same "accept prompt → nothing happens, re-prompts later" pattern occurs with the Rust LSP plugin (`

LSP plugin install prompt accepted but plugin not installed/active (gopls-lsp, rust-analyzer-lsp)

Status Open

Maintainer reply None cached

Activity 2 comments · opened Jul 30, 2026

Accepted the "LSP plugin recommendation" prompt for gopls-lsp — it re-prompted a second time in a later session despite prior acceptance, and no LSP functionality (go-to-definition, diagnostics) appeared after accepting either time.
gopls itself is already installed and on PATH (~/.go/bin/gopls, v0.18.1), so this looks like a Claude Code plugin-registration bug, not a missing binary.
Same "accept prompt → nothing happens, re-prompts later" pattern occurs with the Rust LSP plugin (rust-analyzer-lsp).
For Rust, rust-analyzer is not installed on this machine (rustup reports error: unknown binary 'rust-analyzer' in toolchain 'stable-x86_64-unknown-linux-gnu') — so in that case the plugin may need to actually install/provision the language server itself rather than assuming it's present, which could be a second distinct failure mode worth checking.
Expected: accepting the prompt results in a working LSP integration for that language.
Actual: no visible effect either time; prompt reappears in later sessions.