Agent mode not using default terminal on Windows

[pot2mayo]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On a Windows machine, cursor 1.7.39, when setting my user settings as below:

{
  "terminal.integrated.defaultProfile.windows": "Git Bash",
  "terminal.integrated.profiles.windows": {
    "Git Bash": {
      "path": "C:\\Program Files\\Git\\bin\\bash.exe",
      "args": ["--login"],
      "icon": "terminal-bash"
    }
  },
  "terminal.integrated.automationProfile.windows": {
    "path": "C:\\Program Files\\Git\\bin\\bash.exe",
    "args": ["--login"]
  }
}

my default terminal is git bash as expected when opening a new terminal window in Cursor, but the agent mode still use powershell.
How to make Agent mode use the default terminal?

I already check solutions in the forum such as below but it does not work.

Why the composer default shell is power shell?

That worked ! Thank you so much !!

How to set the composer shell path?

I want to specify the shell path for the composer agent. Where can I set it up?

Note: It’s a fresh install of my OS so I don’t have any old conflicting VS Code settings or anything. I only installed the latest version of Cursor.

Steps to Reproduce

• Set Git Bash as default terminal
• Open terminal and run echo $SHELL => shows that git bash is used
• Open the agent window in Agent mode, as it to run the same command => no output since it’s using powershell

Expected Behavior

The Agent should use the default terminal profile

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.39 (user setup)
VSCode Version: 1.99.3
Commit: a9c77ceae65b77ff772d6adfe05f24d8ebcb2790
Date: 2025-10-08T00:33:20.352Z
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

For AI issues: which model did you use?

Any model since the issue is from the IDE itself.

Does this stop you from using Cursor

Yes - Cursor is unusable

[pot2mayo]

UPDATE:

After checking this post, I tried to turn the “Legacy Terminal Tool” option ON

My Agent starts with the correct default terminal.

Good temp fix for now but it still looks like a bug to me that the default terminal is not used by the Agent without turning this option ON.