Cursor

Partial Detection chain currently bash-unfriendly Windows Difficulty Medium

The IDE side has a workaround (Legacy Terminal Tool); the Agent CLI currently hard-codes PowerShell and cannot be configured.

settings.json · IDE workaround (enable the legacy terminal tool)

{
  "terminal.integrated.useWslProfiles": false
}

Steps

IDE agent: turn on the Legacy Terminal Tool setting; pair it with the useWslProfiles:false above so it does not fall into WSL
Agent CLI: not configurable for now (detectShellType() unconditionally prefers PowerShell on Windows) — reported upstream, waiting for it to expose a shell path

echo "SHELL=$SHELL"; uname -s — observe which shell it actually falls back to

Turn off Legacy Terminal Tool / delete the useWslProfiles setting

Until upstream fixes it, CLI-side commands run with PowerShell syntax — not a bash syntax error
Cursor is VS Code lineage, but both of its products bypass the family-shared probe — agents.md lists it separately, outside the family group

Chinese edition of this page: /agents/cursor/