Agent unable to execute chained commands

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since a recent release (c. 3 weeks ago), whenever my agent tries to run a command line command containing && to chain commands, it complains it gets no output. It can run the command separately, and get the output - it can also use flags (e.g. make -C) which change the working directory. However, it will always default to using cd /the/path && the_thing causing it to continually retry the same command until I explictly tell it to not use &&.

Has anyone else experienced this, or have any idea what the cause is?

Steps to Reproduce

Ask the agent to run a command for a given project (e.g. make test). It will always run cd /path/to/the/project && make test and fail to see output.

Expected Behavior

It should be able to run the commands and see the output.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (Universal)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

Sonnet 4.5, Composer 1, Auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. This looks related to the new terminal implementation in Cursor 2.0, which has some known issues with running commands on macOS.

To start, please try enabling the Legacy Terminal Tool:

  • Open Cursor Settings Cmd+Shift+J
  • Go to the Agents tab → Inline Editing & Terminal
  • Enable “Legacy Terminal Tool”
  • Press Cmd+Shift+P → run “Terminal: Kill All Terminals”
  • Fully restart Cursor
  • Test the Agent with chained commands again

If that doesn’t fix it, could you please share:

  • Your shell config files (~/.zshrc or ~/.zshenv) if they contain a custom PATH or shell switching commands
  • A screenshot of the Agent’s terminal output showing the “no output” error

The team is aware of terminal command execution issues in 2.0 and is working on fixes for 2.1. Let me know if enabling the Legacy Terminal Tool helps.

3

That fix works great, thank you so much!