Tool calling never finishes

Bug Reports
1

Describe the Bug

i ask for the agent to do something. it runs a tool. the tool outputs an error. the agent never notices. i have to either move to background, or i have to spend a request to talk to the agent and move it up in priority above the wasted task.

Steps to Reproduce

i ask for the agent to do something. it runs a tool. the tool outputs an error. the agent never notices.

Expected Behavior

notice that the tool failed and react to it appropriately

Screenshots / Screen Recordings

tool calling never finishes.png
tool calling never finishes.png535×850 29.2 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2
3

i can but that’s not a solution to have to constantly do that. anything with a certain amount of output seems to be a problem

image
image528×1165 43.1 KB

4

and still happens with latest powershell

image
image537×821 31.6 KB

6

as you can see it has nothing to do with the amount of response content so it’s not like a ‘more’ or shell interactivity required situation. looks like it’s just the ide chat not recognizing that the command has returned a result.

7

through a lot of discussion with claude 3.5 systematically trying varying commands with varying output formats and lengths, i figured out it was kubectl command and the PAGER env variable.

i set my environment variable PAGER to cat in windows user level environment variables. this let’s the entire output go out to the console regardless of length. I am not sure why it started to have this behavior out of the blue today but this seems to have fixed it. AND i’m not sure why cursor cannot see the (more) output.