claude-code - 💡(How to fix) Fix Feature: expose loaded plugin versions in running session [1 comments, 2 participants]

This was discovered alongside a bug where /reload-plugins does not actually reload hooks (filed separately). Even once that bug is fixed, the lack of version visibility makes plugin management error-prone. Users managing plugins that enforce correctness constraints need deterministic, evidence-based confirmation that the right version is loaded.

TL;DR

Implement a new command, such as /plugin status or /plugin list --verbose, to display loaded plugin versions and other relevant information for verification.

Guidance

• To address the issue, consider adding a command that provides detailed plugin information, including loaded version, available version, and component breakdown.
• The proposed solution suggests displaying plugin name, loaded version, available version, component breakdown, and any load errors or warnings.
• The new command should provide a clear status indicator, such as "OK" or "UPDATE AVAILABLE", to help users identify potential version mismatches.
• The implementation should ensure that the command works correctly alongside the fix for the separate bug where /reload-plugins does not reload hooks.

Example

/plugin status

or

/plugin list --verbose

could be used to display the proposed output, such as:

standard-tooling-marketplace/standard-tooling
  Loaded:    1.4.12
  Available: 1.4.12
  Components: 6 skills, 10 hooks, 2 commands
  Status: OK

Notes

The implementation details of the new command are not specified, and the exact output format may vary. However, the core idea of providing a way to verify loaded plugin versions and other relevant information remains the same.

Recommendation

Apply workaround: Implement the proposed /plugin status or /plugin list --verbose command to provide users with the necessary information to verify loaded plugin versions. This will help mitigate the issue until a more comprehensive solution is available.