Repository navigation
Conversation
added 4 commits
October 9, 2026 10:46
kostiantyn-pshenychnyi1
approved these changes
Oct 9, 2026
Owner
|
[AUTO_CLOSE_WARNING] ⏰ This pull request has had no activity for 7 days (last activity: 2026-10-09). It will be automatically closed no earlier than 2026-10-23 (UTC) (~6 more days). Any activity from anyone — a comment, a push, a review, reopening — restarts the countdown from that moment. This warning will be deleted automatically once that happens. |
Owner
|
[AUTO_CLOSE_NOTICE] 🔒 Closed automatically: no activity for 14 days (last activity: 2026-10-09). Nothing is lost — the branch is untouched. Reopen the PR to continue; housekeeping will give it a fresh 7/14-day cycle starting from the reopen moment. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Jira: https://jiraeu.epam.com/browse/EPMCDME-15769
Hooks written into an installed extension (
~/.codemie/claude-plugin/hooks/hooks.json) kept pointing at a removedcodemie, becauseBaseExtensionInstaller.install()returned early onalready_existsand never looked at the hooks again. Every Claude Code start then showed aSessionStarthook error and no CodeMie hooks ran.Changes
hook-command.ts: newhasStaleCodemieCommand/repairStaleHooksCommandTree. They match only a leading absolute codemie path (or the Windows quotednode.exe+codemie*.jspair, including paths with spaces) that is missing on disk. Barecodemie, relative paths and other programs are left alone.BaseExtensionInstaller: thealready_existsbranch now callsrepairStaleHooks. It readshooks.jsonand does anexistsSyncper command, and only callsresolveCodemieBinary()when something is stale. It writes only when the tree changed, skips quietly whenhooks.jsonis missing (Kimi), and never rewrites to a barecodemiefallback.resolveHookCommandis unchanged, so migration 006 andcodemie-code.plugin.tsbehave as before. This applies to every extension that goes throughBaseExtensionInstaller.Impact
Before: install at path A, remove A, install again gives
already_existsand hooks still point at A. After: hooks are rewritten to the currentcodemie; a path that still exists is untouched andhooks.jsonis not written.Checklist
--project unitand--project clipass; mutation check: removing the repair makes the new tests fail; replayed the reported case with the built CLI'sClaudePluginInstalleron a test HOME: hooks are repaired, a valid path is left untouched)