Describe the Bug
In the WSL extension environment, when a Node service is started using pnpm, clicking the terminal delete button does not properly terminate the running service process. The service process continues running in the background, and manual Ctrl+C is required to properly terminate the process. This behavior is inconsistent with expectations and creates inconvenience for the development experience.
Steps to Reproduce
Open Cursor in WSL environment
Start a Node service using pnpm in the terminal (e.g., pnpm dev or pnpm start)
Wait for the service to start successfully
Click the delete button (trash icon) in the top-right corner of the terminal
Observe the service process status
Expected Behavior
Expected Behavior:
When clicking the terminal delete button, it should properly terminate all processes running in that terminal, including the pnpm-started Node service, and completely clean up related resources.
Actual Behavior:
After clicking the delete button, the terminal interface is closed, but the pnpm-started Node service process continues running in the background, occupying ports and system resources.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
版本: 1.1.5 (user setup)
提交: 1.96.2
日期: ef5eeb47a684b4c217dfaf0463aa7ea952f8ab90
Electron: 2025-06-21T05:31:17.701Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0
Additional Information
This issue specifically occurs in the WSL extension environment
Related VSCode issue reference: Closing terminal while WSL nodejs is running keeps processes alive and may cause excessive CPU load · Issue #44408 · microsoft/vscode · GitHub
The problem affects development efficiency, requiring manual process termination which is cumbersome
May be related to WSL’s process management mechanism
Issue appears to be specific to pnpm, needs testing with other package managers
Does this stop you from using Cursor
No - Cursor works, but with this issue