[BUG]Terminal Command Execution Issue in Cursor v0.43.5

Terminal Command Execution Issue in Cursor v0.43.5

Issue Description

After updating to Cursor v0.43.5, I’ve encountered a significant usability issue with the terminal command execution feature.

Current Behavior:

  • When executing a generated command using the “Run” button
  • Cursor creates a new terminal window for each command execution
  • Instead of using the currently active terminal

** Movie is here. **

Expected Behavior:

  • Commands should execute in the currently active/focused terminal
  • No new terminal windows should be created unnecessarily

Impact

This behavior significantly disrupts the workflow and reduces productivity, especially when:

  • Running multiple commands in sequence
  • Monitoring output across different terminals

Environment

  • Cursor Version: 0.43.5
  • Feature: Terminal command execution via “Run” button

Priority Request

This issue severely impacts the core functionality of terminal usage in Cursor. A fix would greatly improve the user experience for developers working with multiple terminal instances.

Could you please investigate and prioritize this issue? Thank you for your attention to this matter.

#bug #terminal #usability

4 Likes

Same problem. Hope my answer is move this issue up.

3 Likes

Yep, I’m forced to copy instead of hitting “run” – very annoying

3 Likes

Why no one addresses this? It’s very annoying.

Find a workaround that works for me.
cursor

RULES FOR AI:
USO DE LA TERMINAL:
Solicitar usando ```bash
Usar comandos de Powershell como Get-ChildItem

Thanks for finding this workaround, super helpful for us to fix bugs like this!
I’ve reported it internally and hopefully will get this solved in a future update.

1 Like

So, when you’ll going to fix this issue? It is really annoying . Then you run python code in venv, and it tries to execute installation of packages, but it install to the root directory instead of the local project. Im rolled back to stable version, but it seems that it is automatically updating to the latest version.

@Pasajeromoronmoreno could you please provide universal workaround for this issue? As i see yours is case specific.