When Cursor attempts to run terminal commands, the terminal becomes corrupted and unusable until Cursor is restarted. The issue appears more frequently after performing many operations (suggesting possible state accumulation or resource leak). The issue is intermittent - restarting Cursor and retrying the same command often works.
Error Messages:
–: eval: line 1: unexpected EOF while looking for matching `)’
–: eval: line 2: syntax error: unexpected end of file
–: dump_bash_state: command not found
Steps to Reproduce
I can’t directly reproduce this. I need to grind cursors agent in order to get to a point where terminal gets corrupted
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: GNU bash 3.2.57(1)-release (arm64-apple-darwin25)
Note: This is a pretty old version of bash (2007). macOS ships with this ancient version due to licensing (GPLv3 avoidance). Consider using a newer bash via Homebrew if you need modern features.
PATH Analysis
Your PATH is clean — no directories with parentheses detected. Here’s what’s in it:
Interesting point from both of you: the issue doesn’t show up right away, it starts after the IDE has been running for a while. That helps narrow down what might be causing it.
@bubblegumsoldier, thanks for the screenshot and for finding a workaround with .bash_profile. It’s especially helpful to know that even with an empty config, the issue still comes back over time.
I’ll pass this info to the team. For now, the only reliable workaround is restarting Cursor when the terminal starts acting up.
anyone on this thread using pytest or uv?
i noticed that usually it works until i run unit tests.
then shortly but not always immediately after it breaks