Cursor call Amazon Q CLI automatically after I clicked on Skip button

Support Bug Reports
1

Recently, while Cursor is running terminal command and then I click on Skip button to skip this command, somehow, Cursor type q in the CLI to trigger my Amazon Q CLI and after that, they (Cursor and Q) start talking and fixing my issue magically?

NOTE that I don’t have any Cursor rules or mention Amazon Q

I don’t know why, can Cursor team explain that?

Here is the video when I clicked skip button (change speed to 0.5 to see better)

4 Likes
2

two AIs fixing my issues magically? Can you please tell me more about this? :sweat_smile:

3

I got some issues while running my expo app on iOS simulator, I asked Cursor and it used command line to check my machine configuration and … it talked to Q and they fixed my issues

1 Like
4

Suddenly running into this exact same problem. Tried even setting up some rules to avoid that, with no success.
Still looking for a fix.

1 Like
5

This is happening to me as well, and it’s quite weird and annoying.

I’m trying to work around it by setting up the following shell aliases:

# Avoid Amazon q
alias q='echo "q has been disabled via an alias"'
alias qq='~/.local/bin/q'

This way, if I skip or stop a command, it won’t invoke ‘q’ and will just echo the message above. To keep the q CLI available, I’ve remapped it to ‘qq’.

6

same here

and this conditional alias worked to bypass the issue for me!

# in your .bashrc or .zshrc
if [[ "$TERM_PROGRAM" == "vscode" ]] || [[ -n "$CURSOR_TRACE_ID" ]]; then
    alias q='echo "q command disabled in Cursor terminal"'
fi
7

Me too. This is how I avoid the q command in the Cursor.

~/Library/Application Support/Cursor/User/settings.json (osx)

"terminal.integrated.env.osx": { // <platform> : osx, linux, windows
    ...
    "PATH": "${env:HOME}/dummybin:${env:PATH}"
  },

echo "echo q" > ~/dummybin/q
chmod +x ~/dummybin/q
8

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.