sessionStart plugin hook produces no output on Windows — superpowers plugin (Cursor 2.5.22)

[Mohammad_Aosaf]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The superpowers plugin (v4.3.0) registers a sessionStart hook via .cursor-plugin/plugin.json → hooks/hooks.json. The hook log shows the script is invoked but produces (no output), meaning Cursor either fails to execute the .sh script or discards its stdout.
Running the exact same script manually with Git Bash produces valid JSON output as expected:
{ “additional_context”: “…”, “hookSpecificOutput”: { “hookEventName”: “SessionStart”, “additionalContext”: “…” }}
Hook log shows:
{ “conversation_id”: “…”, “hook_event_name”: “sessionStart”, “cursor_version”: “2.5.22”, …}(no output)

Steps to Reproduce

Install the superpowers plugin via /add-plugin superpowers
Ensure bash is available on PATH (Git Bash at C:\Program Files\Git\bin\bash.exe)
Start a new agent session
Observe hook log — shows (no output) despite the script being valid

Expected Behavior

The sessionStart hook should execute the plugin’s session-start.sh script and inject the returned additional_context JSON into the session.

Operating System

Windows 10/11

Version Information

Current Cursor Version
2.5.22

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

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:

1. Use PowerShell-based hooks on Windows. Wrap the logic in a .ps1 script, or call PowerShell explicitly in the hook command. Full guide here: Hooks in Windows

2. Use WSL. Run Cursor through WSL, where .sh scripts 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.