# Agent's terminal commands fail with dump\_bash\_state not found

**URL:** <https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679>\
**Category:** Bug Reports\
**Created:** [September 16, 2025, 8:20pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679 "2025-09-16T20:20:10Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![grelaxus](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/grelaxus/32/34102_2.png) [@grelaxus](https://forum.cursor.com/u/grelaxus)\
**Post date:** [September 16, 2025, 8:20pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/1 "2025-09-16T20:20:10Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

When Cursor’s Agent runs terminal (agent’s terminal, not regular one), several problem occur

1. the current directory is not the project working dir, but the OS root (i.e. ‘/’)

2. most of commands fail with “–: dump\_bash\_state: command not found”. Many commands print also other errors:  
$ ps aux | grep -E “(npm|node|next)” | grep -v grep  
–: eval: line 1: unexpected EOF while looking for matching `)’  
–: eval: line 2: syntax error: unexpected end of file  
–: dump\_bash\_state: command not found

3. For some reason the terminal became read-only with this version: “Agent terminals are read-only”

If I run them in a regular cursor’s terminal session or in a separate terminal - they run fine. It happens only in the agent’s terminal session

### Steps to Reproduce

ask agent in the chat to run pwd command:  
USER: “run pwd command”  
AGENT:  
I’ll run the pwd command again to show the current working directory.  
$ pwd  
–: eval: line 1: unexpected EOF while looking for matching `)’  
–: eval: line 2: syntax error: unexpected end of file  
–: dump\_bash\_state: command not found

It looks like there was an issue with the shell. Let me try running the pwd command again:  
$ pwd  
/  
–: dump\_bash\_state: command not found

So, it ran the same command twice, and the second time it executed (also printed the dump\_bash\_state error

### Expected Behavior

1. current dir - project root, not OS root
2. no failures, no errors

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.23  
VSCode Version: 1.99.3  
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430  
Date: 2025-09-15T21:49:07.231Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Darwin x64 21.6.0

### For AI issues: which model did you use?

Auto, claude-4-sonet

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![jaismith](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jaismith](https://forum.cursor.com/u/jaismith)\
**Post date:** [September 17, 2025, 12:09am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/2 "2025-09-17T00:09:17Z")

</div>

Hi, thanks for reporting this issue! We’re looking into it. Would you mind sharing whether this is still occurring on the latest release? Also, are you seeing this when working in local workspaces on your Mac, or is this happening in a remote (ssh or container) workspace?

---

<div class="post-metadata">

**Author:** ![grelaxus](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/grelaxus/32/34102_2.png) [@grelaxus](https://forum.cursor.com/u/grelaxus)\
**Post date:** [September 17, 2025, 12:25am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/3 "2025-09-17T00:25:30Z")

</div>

Hi, Thanks for looking into it. I have 1.6.23 and when I press check for update it says “There are currently no updates available.” - so I’m assuming it’s the latest release?  
It’s in local workspace on my Mac, it’s neither remote nor container.

---

<div class="post-metadata">

**Author:** ![grelaxus](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/grelaxus/32/34102_2.png) [@grelaxus](https://forum.cursor.com/u/grelaxus)\
**Post date:** [September 17, 2025, 6:12am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/4 "2025-09-17T06:12:11Z")

</div>

Ok, the update just became available and I installed it (1.6.26) and can confirm, that the issue still persist in the latest release

```auto
$ pwd
--: eval: line 1: unexpected EOF while looking for matching `)'
--: eval: line 2: syntax error: unexpected end of file
--: dump_bash_state: command not found

```

Version: 1.6.26  
VSCode Version: 1.99.3  
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730  
Date: 2025-09-16T17:12:31.697Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Darwin x64 21.6.0

---

<div class="post-metadata">

**Author:** ![Kazopl](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kazopl/32/90359_2.png) [@Kazopl](https://forum.cursor.com/u/Kazopl)\
**Post date:** [September 17, 2025, 7:13am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/5 "2025-09-17T07:13:03Z")

</div>

It’s also happening in the Remote SSH workspaces

---

<div class="post-metadata">

**Author:** ![bateschen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bateschen/32/79920_2.png) [@bateschen](https://forum.cursor.com/u/bateschen)\
**Post date:** [September 17, 2025, 9:19am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/7 "2025-09-17T09:19:26Z")

</div>

i have same error .

版本: 1.6.23 (Universal)

提交: 1.99.3

日期: 9b5f3f4f2368631e3455d37672ca61b6dce85430

Electron: 2025-09-15T21:49:07.231Z (1 天前)

ElectronBuildId: 34.5.8

Chromium: undefined

Node.js: 132.0.6834.210

V8: 20.19.1

OS: 13.2.152.41-electron.0

---

<div class="post-metadata">

**Author:** ![Sangram\_Rout](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@Sangram\_Rout](https://forum.cursor.com/u/Sangram_Rout)\
**Post date:** [September 17, 2025, 12:20pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/8 "2025-09-17T12:20:30Z")

</div>

same here. Both on ssh as well as local container.

Version: 1.6.26 (Universal)  
VSCode Version: 1.99.3  
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730  
Date: 2025-09-16T17:12:31.697Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1

 ![Screenshot 2025-09-17 at 5.50.08 PM](https://us1.discourse-cdn.com/cursor1/original/3X/6/6/668847edd7a8f727cfb85f24d1bdb57ff82e40ce.png)

V8: 13.2.152.41-electron.0  
OS: Darwin arm64 24.6.0

---

<div class="post-metadata">

**Author:** ![Jav](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jav/32/80222_2.png) [@Jav](https://forum.cursor.com/u/Jav)\
**Post date:** [September 17, 2025, 12:23pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/10 "2025-09-17T12:23:57Z")

</div>

This has been reported yet. External terminal is not available anymore, they replaced it by agent terminals which are not capable of many things. Solution for now is downgrade to v1.5

---

<div class="post-metadata">

**Author:** ![Aliaksei\_Shybeka](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@Aliaksei\_Shybeka](https://forum.cursor.com/u/Aliaksei_Shybeka)\
**Post date:** [September 17, 2025, 12:58pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/11 "2025-09-17T12:58:41Z")

</div>

I have same problem! AND something wrong with my shell. my zsh is not loaded in this terminal

---

<div class="post-metadata">

**Author:** ![tecnomanu](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tecnomanu/32/67682_2.png) [@tecnomanu](https://forum.cursor.com/u/tecnomanu)\
**Post date:** [September 17, 2025, 1:13pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/12 "2025-09-17T13:13:45Z")

</div>

For now, if you want, can say to your agent that use this “wrapper” sign.  
/bin/zsh -c “….”

This command allow to your agent to run all terminal command from ZSH terminal, into you common terminal, can change this for another terminal if you preferrer.  
Say in the start of the request that he/her need to use this command because the IDE is stock, and voila! Your terminal is back again (i guess 😛 more or less )

I will pay attention for updates.

Bye!

---

<div class="post-metadata">

**Author:** ![Jav](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jav/32/80222_2.png) [@Jav](https://forum.cursor.com/u/Jav)\
**Post date:** [September 17, 2025, 1:39pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/13 "2025-09-17T13:39:47Z")

</div>

I tried many workarounds, some of them partially worked but the most important thing, inputs are not available anymore

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/f/9f1ee9c62a6964d096d80f054291abbb71d291da.png)

agent terminal is read only so you cannot interact with it anymore… Unless they rollback to external terminals i do not see how this should work..

---

<div class="post-metadata">

**Author:** ![jcurlier](https://avatars.discourse-cdn.com/v4/letter/j/278dde/32.png) [@jcurlier](https://forum.cursor.com/u/jcurlier)\
**Post date:** [September 18, 2025, 1:25pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/14 "2025-09-18T13:25:32Z")

</div>

Same here

---

<div class="post-metadata">

**Author:** ![andy-mirata](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@andy-mirata](https://forum.cursor.com/u/andy-mirata)\
**Post date:** [September 18, 2025, 8:52pm UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/15 "2025-09-18T20:52:35Z")

</div>

same here

Version: 1.6.27

VSCode Version: 1.99.3

Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0

Date: 2025-09-17T20:21:17.042Z (1 day ago)

Electron: 34.5.8

Chromium: 132.0.6834.210

Node.js: 20.19.1

V8: 13.2.152.41-electron.0

OS: Darwin arm64 23.6.0

---

<div class="post-metadata">

**Author:** ![slawekradzyminski](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/slawekradzyminski/32/9379_2.png) [@slawekradzyminski](https://forum.cursor.com/u/slawekradzyminski)\
**Post date:** [September 20, 2025, 7:22am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/16 "2025-09-20T07:22:50Z")

</div>

Fixed for me in 1.6.35

Thanks 🙂

---

<div class="post-metadata">

**Author:** ![user721](https://avatars.discourse-cdn.com/v4/letter/u/f475e1/32.png) [@user721](https://forum.cursor.com/u/user721)\
**Post date:** [September 26, 2025, 10:21am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/17 "2025-09-26T10:21:02Z")

</div>

My version is 1.6.45 (Universal)  
And I still have this problem.

–: eval: line 2754: syntax error near unexpected token `(’  
–: eval: line 2754: `del () ’  
–: line 1: dump\_bash\_state: command not found

---

<div class="post-metadata">

**Author:** ![magnet](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@magnet](https://forum.cursor.com/u/magnet)\
**Post date:** [October 6, 2025, 11:50am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/18 "2025-10-06T11:50:21Z")

</div>

Still have this issue with 1.7.33

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [October 28, 2025, 11:50am UTC](https://forum.cursor.com/t/agents-terminal-commands-fail-with-dump-bash-state-not-found/133679/19 "2025-10-28T11:50:35Z")

</div>

Closed on October 28, 2025, 11:50am UTC

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