›_ Claude Code Issues
Claude Code Issues / #13568

[Bug] Hookify plugin: incorrect sys.path configuration breaks module imports

Resolved 💬 5 comments Opened Dec 10, 2025 by mrekh Closed Mar 25, 2026

Bug Description
Hookify plugin has an issue

  ⎿  PreToolUse:Task says: Hookify import error: No module named 'hookify'
  ⎿  PostToolUse:Task says: Hookify import error: No module named 'hookify'
  ⎿  PreToolUse:Task says: Hookify import error: No module named 'hookify'
  ⎿  PostToolUse:Task says: Hookify import error: No module named 'hookify'

The hookify plugin has a bug in its Python import path logic. Here's what's happening:

The Problem:

  1. The plugin is installed at .../hookify/0.1.0/
  2. The hooks set PLUGIN_ROOT = /Users/******/.claude/plugins/cache/claude-code-plugins/hookify/0.1.0
  3. They add parent_dir (.../hookify) to sys.path
  4. Then try to import from hookify.core.config_loader
  5. This fails because inside the hookify/ directory, there's only 0.1.0/, not a proper Python package structure

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.0.64
  • Feedback ID: 9b01a8eb-4187-4489-8394-7de92e7775a6

View original on GitHub ↗

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