2.1.47 tool calls failing

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

All of a sudden, after updating, tool calls keep failing and the agent has to start running everything in the background. It keeps trying foreground, which always fails, and then switches to background. Again and again.
Can we please also get detailed changelogs for the seemingly daily updates? Then we could actually roll back to a version that works when these changes break things.

Steps to Reproduce

  1. Update to 2.1.47
  2. Try to get agent to run a command that worked yesterday (e.g., make all) that hasn’t been changed at all since
  3. Agent keeps complaining
    “The output seems to have been cut off. Let me try running the test again and capturing more output.”
    “Output is being truncated. Let me try saving to a file.”
    “The output is being cut off. Exit code 0 means success though. Let me try again with a verbose flag or different approach.”
    “The terminal file doesn’t exist yet. Let me try running the tests directly.”

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47 (system setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. It looks like a regression in 2.1.47 on Windows. Please help with diagnostics:

  • Which terminal profile is selected in Cursor: PowerShell, Command Prompt, Git Bash, WSL, etc.? Try changing it: Ctrl+Shift+P → Terminal: Select Default Profile. Docs: Tools | Cursor Docs
  • Does make all run manually in the built-in Cursor terminal without the agent, and in a separate system terminal?
  • Does it happen in other projects or only in one repo?
  • Are any terminal extensions enabled? Try launching Cursor without extensions: cursor --disable-extensions
  • A screenshot or short video of the foreground → background loop
  • Logs from Help → Toggle Developer Tools → Console during the error
  • Request IDs from problematic chat messages: chat menu → Copy Request ID

I’ll pass the request for detailed changelogs and an easy version rollback to the team. Please let me know if switching the terminal profile or running without extensions helps.

Hi Dean - Thanks for your message. Here’s some additional information:

So things are working well on 2.1.42 and I’ll plan to stick on that until the issue is resolved.

Thanks for your help!

I can verify that this is still an issue in 2.1.48 and 2.1.49.

1 Like

Still the same issue in 2.1.50… I’m burning mass tokens for nothing, can you do something about that plz ?

Thanks for information, back to .42 i guess

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