Cursor v2.0.50 terminal issue is back

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Terminal not engaging. Same issue is coming back.

Steps to Reproduce

AI can not execute in terminal, works in Cursor
v2.0.40

Expected Behavior

that it works

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.50
VSCode Version: 1.99.3
Commit: a788ca5efbb89cf7c24e873ea3623b2e47b42490
Date: 2025-11-02T23:59:00.227Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-34-generic

For AI issues: which model did you use?

sonnet 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey @cocode, so that I can understand better, are you referring to the Cursor CLI or the built-in terminal in Cursor? Could you share the exact command you used and any error output?

Additional details that could be helpful:

  • Which default shell you use (bash, zsh, fish, etc.)?
  • Does a regular terminal opened outside Cursor work normally?
  • Any request ID that you can share so that staff could review.
4

Hi,
are you from Cursor?

5

No, I’m not – just a community volunteer trying to help.

1 Like
6

So you see that I wrote, it is IDE, not CLI. I wrote 2.0.50 and I wrote in 2.0.40 terminal works.

It means it is unrelated to my shell. This is a recurring issue, which comes and goes.

And if it was CLI, it will be pointless if shell didn’t work, right?

7

Got it - thanks for the clarity there. Based on what you are describing, something sounds off in the latest version agent terminal settings - sandbox mode, network‑access configuration, or another change between versions.

To help diagnose, please share:

  • What you asked the Agent to do (your query)
  • The command the Agent attempted to run in the terminal

This will narrow whether it’s a configuration issue or a bug in the new version.

On a similar note, I ran into a problem with v2.0.43 when I asked the agent to start a Astro web app’s dev environment. Astro tried to bind to the IPv6 loopback address ::1 on port 4321. My environment denied that listen (EPERM). Asking agent to get around this by binding explicitly to IPv4 (127.0.0.1) and a different port avoided the restriction, and agent could run that normally: yarn dev --host 127.0.0.1 --port 4322

8

Hi,

Are you asking me to do the developers’ tasks? For free, hahahahahahah……?

9

Thanks for reporting this. To investigate, could you please share:

  1. What command was Agent trying to run?
  2. Is the terminal stuck or showing an error?
  3. Request ID (Agent chat menu > Copy Request ID)

Thanks @arun for trying to help!

1 Like
10

I am back in 2.0.40 and I don’t remember what command. but as soon as I opened 2.0.40 the command ran, as if it was stuck in 2.0.50.

So, if you can’t find it, I will wait. no worries. have good day.