claude-code - 💡(How to fix) Fix Disabled plugin still appears in available skills and can be invoked [1 comments, 2 participants]

TL;DR

The issue can be resolved by ensuring that user-level settings are properly prioritized over project-level settings when loading plugins.

Guidance

• Review the plugin loading logic to verify that user-level settings from ~/.claude/settings.json are correctly applied and take precedence over project-level settings.
• Check for any potential caching issues that might cause outdated settings to be used, ensuring that changes to ~/.claude/settings.json are promptly reflected in the application.
• Investigate the system reminder generation process to ensure it respects the enabled/disabled state of plugins as defined in user settings.
• Consider adding a validation step before invoking a skill to check its enabled state, preventing disabled skills from being executed.

Example

No specific code example can be provided without more context on the plugin loading and system reminder generation logic. However, the fix might involve modifying the logic that loads plugins to prioritize user settings, similar to:

// Pseudo-code, actual implementation depends on the application's programming language and framework
if (userSettings.enabledPlugins[pluginName] === false) {
  // Skip loading or invoking the plugin
}

Notes

The solution assumes that the issue lies in the application's logic for handling user-level settings and plugin enablement. Without access to the specific codebase or more detailed information about the application's architecture, the guidance provided is based on general principles of settings precedence and plugin management.

Recommendation

Apply a workaround by manually removing or commenting out the disabled plugin from any project-level settings files until the root cause is identified and fixed, ensuring that user-level settings are respected. This approach allows for immediate mitigation of the issue while a more permanent solution is developed.