Commands in Agent get auto-cancelled

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Running commands get auto-cancelled when changing tabs.

Steps to Reproduce

1.- Run a time-based command.
2.- While the Agent is waiting for the execution to finish, switch tabs.
3.- Go back to the original tab, and you’ll see the command cancelled/rejected.

Expected Behavior

The behavior of the command should continue in the background even after switching tabs, like how it was before.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.54
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin x64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I wasn’t able to repro this tab-switching cancellation on my end, but let’s try the Legacy Terminal Tool workaround that’s helped with other terminal issues:

Cursor Settings > Agents > Inline Editing & Terminal > Enable “Legacy Terminal Tool” > Restart Cursor

Same issue.

And if I may add extra information, based on this last attempt I just did (from the recording above), the cancellation/rejection doesn’t happen only in time-based commands, but in any ongoing/running command.

Thanks for trying the Legacy Terminal Tool workaround and confirming it didn’t help. Since this affects all ongoing commands when you switch tabs, it looks like a regression that needs engineering attention.

Could you please share:

  • Request ID: after a command gets cancelled, click the chat’s context menu (top right) > Copy Request ID
  • Console logs: Help > Toggle Developer Tools > Console tab — screenshot any errors that appear when the command cancels
  • Extensions test: does it still happen if you run cursor --disable-extensions from Terminal?

I’ll escalate this to the team with your findings.

There you go:

Request ID –> 37dd87d8-fc2f-4688-9f71-d48df18bc183

Screenshots of console with errors –>

Extensions test –> it does happen still.

Any updates in this one?

Hey, yes, the team is investigating this. Also try updating to the latest version if you haven’t already.
If the issue remains, please try the nightly build as well.

1 Like