Skip to content

v0.1.1 — critical hook packaging fix

Choose a tag to compare

@iamgagan iamgagan released this 16 Apr 19:28

Critical bug fix

v0.1.0 shipped with non-functional hooks. The plugin manifest used the wrong format and location, so Claude Code's hook loader never registered any of the three hooks (UserPromptSubmit, PreToolUse, Stop). They never fired in any user's environment.

v0.1.1 fixes the packaging. Hooks now register correctly via hooks/hooks.json in the standard Claude Code format used by other working plugins (Warp, superpowers, etc.).

What's now verified

Hook Fires?
UserPromptSubmit (signal-detector) ✅ Yes — verified via SDK probe (24 entries written to _signals.md) and claude -p smoke test (8 hits)
Stop (synthesis) ❌ Still broken — separate stdin parsing bug, fix in v0.1.2
PreToolUse (think-first) ❌ Still broken — separate stdin parsing bug, fix in v0.1.2

Benchmark (n=3 per task × mode, 18 runs total)

Task Baseline Plugin Δ
01-fizzbuzz 27.8±1.4s 16.6±2.1s -40%
02-bug-fix-surgical 17.8±2.2s 14.7±0.7s -18%
03-refactor-restraint 25.6±3.1s 26.9±8.8s +5% (noise)

100% pass rate in both modes. Diff sizes byte-identical across modes (code-quality claims still unsupported by data).

See BENCHMARK.md for full caveats and methodology.

Upgrade

If you installed v0.1.0:

claude plugins update claude-mind

This is mandatory — v0.1.0's hooks are non-functional.

Roadmap

  • v0.1.2: fix Stop and PreToolUse hooks (stdin JSON parsing)
  • v0.2 benchmark: n≥10 per cell; bigger tasks; component-level evals