Hey, this is a known Windows issue. Cursor’s hooks launcher internally uses PowerShell to initialize hooks, which can break .sh scripts even if Bash is in PATH. The script runs fine when you execute it directly in Git Bash, but Cursor can’t run it correctly because the shells don’t match.
A couple workarounds:
-
Use PowerShell-based hooks on Windows. Wrap the logic in a
.ps1script, or call PowerShell explicitly in the hook command. Full guide here: Hooks in Windows -
Use WSL. Run Cursor through WSL, where
.shscripts run natively.
Since the superpowers plugin ships its hooks as .sh files, this is something the plugin author should handle for Windows compatibility, for example by providing a .ps1 alternative or a cross-platform wrapper.
The team is aware of the broader hooks issue on Windows. Your report helps us prioritize it.
Let me know if you want help setting up the PowerShell workaround.