Chat stop in every terminal actions

[abkrim]

Describe the Bug

Terminal commands executed through the AI assistant get stuck in a hanging state and require manual cancellation to proceed. This behavior started occurring after a machine restart, despite having the same Cursor version (1.0.0) installed previously.

Steps to Reproduce

Steps to Reproduce

1. Start a conversation with AI assistant
2. Execute any terminal command (e.g., vendor/bin/pest tests/Unit/Helpers/GeneralHelperTest.php)
3. Command executes but hangs after producing output
4. Manual cancellation required to continue

Expected Behavior

Expected Behavior

• Commands should execute and return output automatically
• Chat conversation should continue without manual intervention
• Terminal output should be processed normally regardless of length

Actual Behavior

• Commands execute but hang indefinitely
• Output shows “Command was canceled by the user” when manually canceled
• Only way to continue the conversation is to manually cancel the terminal command
• This happens even with simple commands that previously worked fine

Steps to Reproduce

1. Start a conversation with AI assistant
2. Execute any terminal command (e.g., vendor/bin/pest tests/Unit/Helpers/GeneralHelperTest.php)
3. Command executes but hangs after producing output
4. Manual cancellation required to continue

Sample Command That Hangs

vendor/bin/pest tests/Unit/Helpers/GeneralHelperTest.php
# Output appears correctly but then hangs indefinitely

Impact

• Severely disrupts development workflow
• Makes terminal-based debugging and testing difficult
• Requires constant manual intervention

Timeline

• This morning: Everything worked perfectly with same configuration
• After machine restart: Problem started occurring
• Current: Consistent reproduction of the issue

Additional Notes

• Same behavior occurs with both short and long command outputs
• No changes made to project configuration, Cursor rules, or shell settings
• Issue is specific to Cursor terminal integration, direct terminal works fine
• Project has custom Cursor rules but these were working fine before restart

Workaround

Currently manually canceling each command, but this is highly disruptive to productivity.

Logs/Console Output

When manually canceling, the following appears:

Command was canceled by the user. ASK THE USER what they would like to do next.

The previous shell command ended, so on the next invocation of this tool, you will be reusing the shell.

On the next terminal tool call, the directory of the shell will already be /Users/abkrim/Sites/sitelight.

Expected Resolution

Commands should complete automatically without requiring manual intervention, returning to the previous working behavior.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Environment

• Cursor Version: 1.0.0
• OS: macOS 24.5.0 (Darwin)
• Shell: /bin/zsh
• Project: Laravel/PHP project

Additional Information

Cursor Configuration

Project Structure:
- .cursorignore present (excludes .env files)
- .cursor/rules/ directory with 5 rule files:
  - coding-conventions.mdc (157 lines)
  - shell-aliases.mdc (58 lines) 
  - git-conventions.mdc (86 lines)
  - project-overview.mdc (122 lines)
  - language-preferences.mdc (71 lines)

.cursorignore contents:
.env
.env.local
.env.development.local
.env.test.local
.env.production.local

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Kristijan]

+1 For me - I’m using zsh as default profile with oh-my-zsh + powerlevel10k
What i’ve noticed is that disabling powerlevel-10k or switching to bash resolves this issue
What happens particularly is that the terminal process HANGS and even Ctrl + C multiple times will not close it - even if I stop the execution blank terminal space remains

I’ve also tried “Moving terminal to background” then doing Ctrl + C - no luck, even the trash bin icon doesn’t work

Alternatively maybe a good option to consider for the future is separation of terminal environments for automatic terminals - e.g. we can use Bash for automatic in-chat terminal and use zsh for our cursor (vscode) integrated terminal
That option would be nice

[abkrim]

I’ve been using Cursor + Terminal + Zsh + oh-my-zsh + powerlevel10k for the past three months without a single issue—until today.

Yesterday, while working on a Python project, I ran into some issues with the chat functionality. Interestingly, everything worked fine in Cursor, but not in the terminal. The Cursor AI (Claude 4 agent) suggested using a virtual environment.

I was in a rush, so I don’t quite remember if I changed anything in my settings.

That was yesterday. Today, after rebooting my Mac for the first time in a long while—boom, the problem appeared.

[deanrie]

Hey, thanks for the report. We’ll investigate it.

[trianglegrrl]

+1 to the above reports for me and a co-worker, both zsh + oh-my-zsh + p10k users. This happened quite infrequently for us until last week, and now it’s consistent.

I can confirm that switching my default shell to bash is a workaround for this issue. bash is totally stock on my system, and zsh is customized with omz + p10k.

[sunilsbcs]

I am also encountering the precisely described ‘Chat stop in every terminal actions’ anomaly within Cursor, mirroring the behavior outlined in the forum post. The workflow disruption from requiring manual Resume after each shell command (cd, ls, execution of binaries) is critically impacting productivity. Despite comprehensive diagnostics including full reinstallations, environment isolation attempts, and Developer Tools log scrutiny, the intermittent AI suspension persists across diverse projects and shell types. This points towards a core integration or event-listening malfunction that evades conventional debugging.

[cxemnet]

I’ve also encountered a similar problem.

[mikiross]

Same problem for me with 1.0.0 on Mac. Also using ohmyzsh and p10k in my terminal.

Found that selecting Move to background instantly resolves the hang.