Describe the Bug
Hi there, there’s a bug in git-bash that vscode users experience it manifests in cursor in two parts (1) the agent “miss-types” the first letter (due to malformed color command) and (2) as the foreground agent hanging, waiting for the shell command to complete that never will unless the user hits enter.
Since I’m a programmer myself, I’ve investigated this and I hope this report can shine light on this mysterious bug that hangs the foreground agents for a lot of windows users.
I would say this is the primary cause of problems for me right now, 10-30% of all terminal commands are failing this way. So most of the time a cursor foreground becomes stuck when I walk away and don’t provide manual intervention. It’s the #1 bug I’m hitting day to day.
THE PROBLEM:
VScode + git-bash => occasionally a malformed color command is being injected into the terminal.
The bug will manifest by the first character getting stripped off of the tool call. So for example: uv run python -m ci.compiler will be transformed into v run python -m ci.compiler (notice the missing u at the front of uv tool call). This results in the error message: v is not a program.
This does NOT happen for background agents working in the wsl workspace. Only on Windows with git-bash (as far as I can tell).
*Workarounds*: I update my cursorrules so that the AI will prepend the tool call with an extra space. This seems to work better than not.
However, this bug also then manifests in a different issue:
The closing color tag is also malformed!
This is the symptom:
The terminal of the foreground agent will appear hung, but then click on the most recent terminal thats current blocking the agent, so it has ui focus, then hit the enter key. A new line will be sent to the terminal and this will, as far as I can guess, allow the color mode of git-bash to be terminated thus completing the shell command, thus releasing control back to the agent. The agent will immediately resume operation.
My research produced the following links that goes into more detail about this issue:
Steps to Reproduce
You can replicate in vscode or cursor.
You need to set settings.json up so that it calls into the git-bash shell, like this:
{
"terminal.integrated.defaultProfile.windows": "Git Bash",
"terminal.integrated.shellIntegration.enabled": false,
"terminal.integrated.profiles.windows": {
"Command Prompt": {
"path": "C:\\Windows\\System32\\cmd.exe"
},
"Git Bash": { // <---- THIS !!!!!
"path": "C:\\Program Files\\Git\\bin\\bash.exe",
"args": ["--cd=."]
}
},
"files.eol": "\n", // Unix
"files.autoDetectEol": false, // Prevent VS Code from auto-detecting and changing EOL
"files.insertFinalNewline": true, // Ensure files end with a newline
"files.trimFinalNewlines": true, // Remove extra newlines at the end
"editor.tabSize": 4,
"editor.insertSpaces": true,
"editor.detectIndentation": true,
"editor.formatOnSave": false,
// Debugger defaults - ensure C++ debugger is used for C++ files
"debug.defaultDebuggerType": "cppdbg",
"debug.toolBarLocation": "docked",
"debug.console.fontSize": 14,
"debug.console.lineHeight": 19,
// Prevent Python debugger from interfering with C++ files
"python.defaultInterpreterPath": "uv",
"python.debugger": "debugpy",
}
Expected Behavior
The foreground agent doesn’t get stuck.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.3.8 (user setup)
VSCode Version: 1.99.3
Commit: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Date: 2025-07-31T21:46:17.109Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
