fix(hookify): resolve import errors when CLAUDE_PLUGIN_ROOT is not set #13452
+49
−38
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The hookify hooks relied on CLAUDE_PLUGIN_ROOT environment variable being set by Claude Code, but this wasn't always the case. This caused import errors like "No module named 'hookify'" on every tool use. Changes: - Add fallback to derive PLUGIN_ROOT from __file__ when env var is missing - Change imports from `hookify.core.*` to `core.*` for compatibility with the cache directory structure (hookify/0.1.0/ vs hookify/) - Always add PLUGIN_ROOT to sys.path (not conditional on env var existing) This fixes the "Hookify import error: No module named 'hookify'" that appeared in PostToolUse, PreToolUse, Stop, and UserPromptSubmit hooks. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
kmk142789
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
CLAUDE_PLUGIN_ROOTenvironment variable was not set__file__when env var is missinghookify.core.*tocore.*for cache directory compatibilityProblem
The hookify hooks displayed "Hookify import error: No module named 'hookify'" on every tool use (PreToolUse, PostToolUse, Stop, UserPromptSubmit). This happened because:
CLAUDE_PLUGIN_ROOTenv var would always be setfrom hookify.core.*) didn't work with the cache directory structure (hookify/0.1.0/instead ofhookify/)Solution
PLUGIN_ROOTfrom script location when env var is missingfrom core.*imports which work whenPLUGIN_ROOTis insys.pathTest plan
echo '{}' | python3 <script>{}(empty JSON) when no rules match🤖 Generated with Claude Code