Without doubt, the MOST frustrating Cursor issue is STILL: zsh: command not found: q

Describe the Bug

Cursor Agent is STILL typing the letter ‘q’, causing this stupid terminal error.

However, the most frustrating part is that this hasn’t been resolved yet, despite multiple requests:

Come on team Cursor, this one can’t be too complex to resolve. It’s stalling all Agent-run terminal interactions.

Steps to Reproduce

Ask the agent to do literally anything that involves the terminal using zsh

Expected Behavior

The agent DOES NOT WRITE THE LETTER ‘q’

That’s it!

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
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.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2 Likes

Hey, the team are actively working on this issue at the moment, and we hope to have this resolved soon!

7 Likes

Thanks Dan! Good to hear.

Sorry about the rant…

2 Likes

Also, the problem is that my Windows operating system is not in English, and these symbols are always in the terminal And also often there is an eternal hang often

Not sure if that’s the same bug? Can you post a screenshot

This is compounded when the Amazon Q CLI is enabled, which then captures all following terminal requests (Using Amazon Q Developer on the command line - Amazon Q Developer).

1 Like

I found problem in oh-my-zsh theme:
(in .zshrc)
ZSH_THEME=“powerlevel10k/powerlevel10k”

Just replace with:
ZSH_THEME=“robbyrussell”

(maybe beed to update omz too)

I’ve just upgraded to version 1.2 (released July 3), and it looks like the bug is now resolved. Appreciate the great work—thank you!

1 Like

I still get the error… frustrating indeed. I think Claude thinks it’s simulating a manual EOF (End of File) via Ctrl+D But in PowerShell (windows), ^D isn’t a real keystroke — it’s just text (q^D), which throws a command-not-found error
I Tried giving it explicit instructions not to use q^D but it doesn’t care!

@danperks it’s back… v1.2.2 - please help!

image

Not sure if this helps—I’m still on v1.2.1. I found that if I turn off “Auto” for the agent and manually select Claude 4 Sonnet in Cursor, I can see the error. However, if I leave the agent setting on “Auto,” I don’t get any errors—it works fine.

v1.2.4 - even Grok 4 is introducing the unnecessary ‘q’ using ZSH.

@danperks @deanrie I thought this was resolved!

image

@danperks Any update on this? Some users are reporting it was resolved, some are reporting it was reintroduced?

Hi everyone here, the issue is being worked on by Cursor Team.

I think we also have a few duplicate posts on this so the efforts on communicating this everywhere becomes a bit more tricky.

here are similar cases

1 Like