Cursor Agent Not Using System Shell and Having Issues with AWS CLI

How To
1

Cursor agent seems to keep defaulting to its integrated but broken shell, regardless of my settings.json. For some reason this shell is unable to use the AWS CLI. I have tried all the other fixes/modifications to settings.json but to no avail. Anybody?

aws ecs describe-services --cluster mvp-default-cluster --services news-api-service --region ap-southeast-1 --query ‘services[0].taskDefinition’
head: |: No such file or directory
head: cat: No such file or directory

My settings.json

{
“window.commandCenter”: 1,
“[markdown]”: {
“diffEditor.ignoreTrimWhitespace”: true
},
“diffEditor.maxComputationTime”: 0,
“terminal.integrated.profiles.osx”: {

    "zsh": {
            "path": "/bin/zsh",
            "args": ["-l"]
            }
},
"terminal.integrated.shellIntegration.enabled": false,
"terminal.integrated.automationProfile.linux": {

},
"terminal.integrated.autoReplies": {
    
},
"terminal.integrated.automationProfile.osx": {

    "path": "/bin/zsh"
},
"terminal.integrated.env.osx": {

},
"terminal.integrated.env.windows": {},
"terminal.integrated.automationProfile.windows": {

},
"terminal.explorerKind": "external",
"terminal.integrated.defaultProfile.osx": "zsh"

}

3 Likes
2

This is very irritating

3

Yes it is… :pensive_face:

4

Very Annoying, it would be great to get it fixed

5

Still seeing it here as well - would love to hear if someone has a workaround.