Agent runs in system shell instead of configured default terminal profile

Ideas Feature Requests
1

Feature request for product/service

Terminal

Problem
When Cursor Agent runs shell commands, it uses the system default shell (e.g. /bin/zsh) and ignores the user’s terminal.integrated.defaultProfile setting in settings.json.

Impact
If my dev environment (PATH, nvm, etc.) is configured in another shell (e.g. fish), the Agent runs in the system shell and doesn’t see those tools, causing command not found for node, pnpm, etc.

Expected behavior
The shell used by the Agent should respect terminal.integrated.defaultProfile, or there could be a dedicated setting (e.g. cursor.agent.shell) to choose which shell the Agent uses.

Workaround
I had to duplicate PATH setup in my system default shell’s config (e.g. ~/.zshrc), which is fragile when I switch node versions in my main shell.

3

Same issue here. My default terminal is Git Bash (terminal.integrated.defaultProfile.windows) and it works for me — I use it in the integrated terminal for all my work. The agent does not use the same shell; in my setup it tries WSL (and fails, since I only have Docker Desktop, no Ubuntu) or uses PowerShell. I work on Windows with Git Bash by choice and need the agent to use the same shell. Please treat as the same request: agent should use the configured default terminal profile.