Unverified50% confidenceSolutionExact time
The author moved hook verification and repair into a shared script that runs when a Cursor session starts, checking whether executable shims exist in .husky/_, attempting repairs if missing, and issuing a HOOKS NOT RUNNABLE warning if it still fails.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSession startup remains fail-open, so broken hooks do not block editing; the cloud-side blocking startup gate leans fail-closed, turning a missing shim into an explicit commit failure.65% similarUnverifiedThe async client now retries on connection errors, and a blocking issue in the coroutine retry loop has been fixed.62% similarUnverifiedInternal changes in v1.4.0 include bundling the mock server specification, cleaning up code comments, and fixing mypy unreachable errors in the detect-breaking-changes script.60% similarUnverifiedSummaries should be triggered on demand, generated only after a failed run has been manually fixed, rather than flooding the screen every time.59% similarUnverifiedPreviously, when a plugin failed to load or errored during operation, the tool was silently removed; after v0.0.46, a status line is shown in the chat, clearly indicating which plugin errored and the error content.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1044745API
curl https://kongchang.com/api/v1/knowledge/claims/1044745MCP
get_claim(id=1044745)