Plugin system has no dependency management — runtime dependencies are undeclared and unverified

Status Closed — not planned
Maintainer reply None cached
Activity 2 comments · opened Apr 27, 2026 · closed May 30, 2026

Problem

Claude Code's plugin system has no mechanism for plugins to declare runtime dependencies (e.g., Python, Node.js, external binaries). As a result:

  1. Plugins install silently even when required runtimes are missing
  2. Failures only surface at runtime, with cryptic OS-level error messages
  3. There is no indication of which plugin caused the failure or how to fix it
  4. Plugin marketplace descriptions do not document requirements

Expected behavior

  • Plugin manifests should support a requires (or equivalent) field to declare runtime dependencies
  • Claude Code should verify declared dependencies at install/enable time and warn the user if any are unmet

Example

The hookify plugin (from claude-plugins-official) runs scripts via python3. On a machine without Python installed, the plugin fails silently at runtime with a generic OS error — with no mention of Python, no mention of hookify, and no guidance on how to resolve it.

View original on GitHub ↗

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