# Cursor on Windows, terminal tasks dont always react on command completed **URL:** \ **Category:** Bug Reports\ **Tags:** java\ **Created:** [September 4, 2025, 5:59am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570 "2025-09-04T05:59:13Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![DarkDeny](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/darkdeny/32/78788_2.png) [@DarkDeny](https://forum.cursor.com/u/DarkDeny)\ **Post date:** [September 4, 2025, 5:59am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/1 "2025-09-04T05:59:13Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug I noticed this behavior quite often. I am giving Cursor some tasks, it runs terminal commands but it waits for terminal command to complete even when it is done long time ago ### Steps to Reproduce My thoughts on this are: 1. have a windows machine 2. give cursor tasks that require running terminal commands (e.g. switch git branches, update master after PR was merged, etc) ### Expected Behavior Cursor always correctly detects that terminal command completed and goes on with his tasks ### Screenshots / Screen Recordings ![cursor-terminal-waiting.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/d/ad99d3195589edcf82aea0b4b7f12d853defe750.png) ### Operating System Windows 10/11 ### Current Cursor Version (Menu → About Cursor → Copy) Version: 1.5.9 (user setup) VSCode Version: 1.99.3 Commit: de327274300c6f38ec9f4240d11e82c3b0660b20 Date: 2025-08-30T21:02:27.236Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.26100 ---
**Author:** ![mwjt42](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mwjt42/32/7270_2.png) [@mwjt42](https://forum.cursor.com/u/mwjt42)\ **Post date:** [September 4, 2025, 6:17am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/2 "2025-09-04T06:17:35Z")
This has been broken since before v1. @andrewh tells us it’ll be fixed in the imminent 1.6 release ---
**Author:** ![bsf\_yassine](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bsf_yassine/32/80072_2.png) [@bsf\_yassine](https://forum.cursor.com/u/bsf_yassine)\ **Post date:** [September 4, 2025, 12:14pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/3 "2025-09-04T12:14:16Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Cursor when it try to lunch a command in terminal or in the focus , it is in progress for infinite time , and does not lunch the command . sometimes it lunch the command but when it finish , it does not detect that it finish . i am obliged to stop it and say to the prompt that the command finish . ### Steps to Reproduce it happen randomely. ### Expected Behavior that the commands is executed instantly . that Cursor detect when a command execution is finished ### Screenshots / Screen Recordings ![cursor_error.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/1/a1b3ba5bbe12e68e0354a6fc6cffdabcbdab58d1.png) ### Operating System Windows 10/11 ### Current Cursor Version (Menu → About Cursor → Copy) Version: 1.5.9 (user setup) VSCode Version: 1.99.3 Commit: de327274300c6f38ec9f4240d11e82c3b0660b20 Date: 2025-08-30T21:02:27.236Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.22631 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\ **Post date:** [September 4, 2025, 1:32pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/4 "2025-09-04T13:32:52Z")
@bsf_yassine thank you for the bug report. I sent it to the team for review. We have a new version 1.6 coming soon that fixes that issue. ---
**Author:** ![f00z](https://avatars.discourse-cdn.com/v4/letter/f/dec6dc/32.png) [@f00z](https://forum.cursor.com/u/f00z)\ **Post date:** [September 4, 2025, 2:40pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/5 "2025-09-04T14:40:39Z")
This happens to me on powershell/pwsh a lot and if i click on the terminal and just hit ‘enter’ to make the prompt show up again, it resumes, but then the agent doesn’t get the output from the terminal (it thinks the command returned nothing) ---
**Author:** ![bio71](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bio71/32/48415_2.png) [@bio71](https://forum.cursor.com/u/bio71)\ **Post date:** [September 4, 2025, 2:50pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/6 "2025-09-04T14:50:37Z")
I’ve always had this kind of problem on Windows 11. Only with the 1.4.5 release the problem completely disappeared. Now it’s frankly unusable and I’m considering switching to other solutions like Claude Code! ---
**Author:** ![DarkDeny](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/darkdeny/32/78788_2.png) [@DarkDeny](https://forum.cursor.com/u/DarkDeny)\ **Post date:** [September 4, 2025, 3:14pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/7 "2025-09-04T15:14:27Z")
When 1.6 is expected? ---
**Author:** ![lemonsevens](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lemonsevens/32/3594_2.png) [@lemonsevens](https://forum.cursor.com/u/lemonsevens)\ **Post date:** [September 4, 2025, 3:50pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/8 "2025-09-04T15:50:32Z")
Cursor has had this problem forever… lots of people have reported it (including myself). Super frustrating and ruins the Cursor Agent experience. Must be an incredibly difficult problem. ---
**Author:** ![FinDevAI](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/findevai/32/89390_2.png) [@FinDevAI](https://forum.cursor.com/u/FinDevAI)\ **Post date:** [September 4, 2025, 4:48pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/9 "2025-09-04T16:48:39Z")
Yup, its time to fix this one, but now some models are immune to this bug, but not all. Ergonomically this is a sub optimal situation. ---
**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\ **Post date:** [September 5, 2025, 8:45am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/10 "2025-09-05T08:45:43Z")
We have reworked this part and it will be launched in 1.6 which is now in testing phase but should be out as beta soon. ---
**Author:** ![bsf\_yassine](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bsf_yassine/32/80072_2.png) [@bsf\_yassine](https://forum.cursor.com/u/bsf_yassine)\ **Post date:** [September 18, 2025, 9:42am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/11 "2025-09-18T09:42:19Z")
> [@condor](#): > > ave reworked this part and it will be launched in 1.6 which is now in testing phase but I just tested the last version 1.6 ![cursor-2](https://us1.discourse-cdn.com/cursor1/original/3X/0/5/05326e684a656386a4dde0822facf789639432e2.png) Version: 1.6.27 (user setup) VSCode Version: 1.99.3 Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0 Date: 2025-09-17T20:21:17.042Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.22631 i still have the issue as you can see in the screenshot. the command is executed , but cursor still waiting for it finish like is not aware that is finished already . The last version seems introduced another regression , the button that allow to copy from terminal to chat is missing , and when i try to the “Cltr +C” to copy it interprete is as “interupt command” and not copy . i am very struggling with this terminal part . ---
**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\ **Post date:** [September 18, 2025, 1:16pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/12 "2025-09-18T13:16:12Z")
While some users have seen improvements we are still seeing some edge cases with terminals and continue to work on it. > Note: CTRL C means in many terminals interrupt command, not copy. It is not something we changed. I will let the team know about the copy button. ---
**Author:** ![Murgur](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@Murgur](https://forum.cursor.com/u/Murgur)\ **Post date:** [September 18, 2025, 2:57pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/13 "2025-09-18T14:57:38Z")
Please add an automatic mode that forces the AI to run all terminal commands in the background. In many cases, terminal output isn’t needed. This could be implemented as part of the custom mode. For the mode “waiting” state, simply make it send Enter up to 5 times at different intervals. This works in 99% of cases to resolve terminal hangs after commands in both Linux and PowerShell. To avoid accidental triggers, keep this feature as a separate terminal option rather than the default. Many users would appreciate it. ---
**Author:** ![FinDevAI](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/findevai/32/89390_2.png) [@FinDevAI](https://forum.cursor.com/u/FinDevAI)\ **Post date:** [September 19, 2025, 1:32am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/14 "2025-09-19T01:32:12Z")
after highlighing a section of text in terminal I used to be able to Ctrl-C to copy it. Now the Ctrl-C is an interrupt in that context ---
**Author:** ![jmi](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@jmi](https://forum.cursor.com/u/jmi)\ **Post date:** [September 22, 2025, 2:19pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/15 "2025-09-22T14:19:29Z")
Just came here to +1 this. I have the exact same issue on Windows 11 for my git commands. Terminal hangs indefinitely after successfully executing. Version 1.6.42. ---
**Author:** ![Kenza](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@Kenza](https://forum.cursor.com/u/Kenza)\ **Post date:** [September 28, 2025, 10:30pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/16 "2025-09-28T22:30:25Z")
### Describe the Bug Regardless of the command, Cursor gets stuck waiting in terminal. Even if the command finished and returned the correct exit codes. It hangs on: - cd directory/ - npm tests - pip installs - docker builds - git commands Windows 11, this has been happening for the past \>5 released versions. ### Steps to Reproduce Install Cursor IDE on Windows 11. Ask it to complete any task that would require a command line call → It gets stuck ### Expected Behavior … Don’t get ■■■■? ### Operating System Windows 10/11 ### Current Cursor Version (Menu → About Cursor → Copy) Version: 1.7.11 (user setup) VSCode Version: 1.99.3 Commit: 867f14c797c14c23a187097ea179bc97d215a7c0 Date: 2025-09-26T16:55:04.318Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.26100 ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![zhanpengGuan](https://avatars.discourse-cdn.com/v4/letter/z/5f8ce5/32.png) [@zhanpengGuan](https://forum.cursor.com/u/zhanpengGuan)\ **Post date:** [October 5, 2025, 8:40am UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/17 "2025-10-05T08:40:51Z")
![image](https://us1.discourse-cdn.com/cursor1/optimized/3X/a/f/af593b383f52452f58d264df536c001e909f10ac_2_690x39.png)you can chose it when using it, which will enable cltr+c works ---
**Author:** ![tjmcdonough](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@tjmcdonough](https://forum.cursor.com/u/tjmcdonough)\ **Post date:** [October 16, 2025, 1:13pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/18 "2025-10-16T13:13:43Z")
Add this to our User or Org settings JSON ```json "terminal.integrated.shellIntegration.enabled": true, "terminal.integrated.commandsToSkipShell": [], "terminal.integrated.sendKeybindingsToShell": false ``` ---
**Author:** ![FinDevAI](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/findevai/32/89390_2.png) [@FinDevAI](https://forum.cursor.com/u/FinDevAI)\ **Post date:** [October 16, 2025, 4:25pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/19 "2025-10-16T16:25:44Z")
This failure to complete terminal command has come back with 1.7.46 andthe previous version too. What is causing it this time is when there is an error in the syntax of the command and the command fails, then the terminal hangs and does not exit unless I cancel it. Version: 1.7.46 (user setup) VSCode Version: 1.99.3 Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580 Date: 2025-10-14T01:21:46.830Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows\_NT x64 10.0.26100 ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [November 7, 2025, 4:26pm UTC](https://forum.cursor.com/t/cursor-on-windows-terminal-tasks-dont-always-react-on-command-completed/132570/20 "2025-11-07T16:26:18Z")
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.