typescript-lsp plugin: stuck in broken state — UI shows Disabled, can't enable or uninstall

Resolved 💬 4 comments Opened Mar 21, 2026 by lakshmithota92 Closed Apr 18, 2026

Bug Report

Summary

The typescript-lsp@claude-plugins-official plugin is stuck in a broken state where:

  • The plugin UI always shows Status: Disabled
  • Attempting to enable it returns: Failed to enable: Plugin "typescript-lsp@claude-plugins-official" is already enabled at project scope
  • Attempting to uninstall also fails silently
  • After /reload-plugins, the output consistently shows 0 plugin LSP servers — the LSP never loads

Steps to Reproduce

  1. Install typescript-lsp plugin via /plugin
  2. Run /reload-plugins — observe 0 plugin LSP servers
  3. Open /plugin menu — Status shows "Disabled"
  4. Click "Enable plugin" — error: "already enabled at project scope"
  5. Click "Uninstall" — no effect, plugin remains

Expected Behavior

  • Plugin status should reflect actual state
  • Enable/Disable/Uninstall actions should work
  • After enabling, /reload-plugins should show 1 plugin LSP server

Actual Behavior

  • UI state is permanently out of sync with settings.json
  • settings.json correctly has "typescript-lsp@claude-plugins-official": true
  • Despite this, LSP never registers and UI shows Disabled
  • No actionable error shown in the Errors tab

Environment

  • Platform: macOS (darwin 25.3.0)
  • Shell: zsh
  • Project type: Next.js / TypeScript (tsconfig.json present at project root)
  • Plugin scope: project

Additional Notes

Manually editing settings.json to set the value to false had no effect — the plugin manager re-enabled it on next interaction. The plugin appears completely unmanageable once installed.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗