Where does the bug appear (feature/product)? Cursor IDE Describe the Bug Cursor considers actions in the terminal as a disruptive error if the console runs for longer than 10 minutes. Steps to Reproduce Ask the agent to run a terminal with “Hello World” and a 20-minute delay. Receive an error. E…

Related: Tool call ended/ User aborted request Tool call ended before result was received, 2025 Oct Tool call ended before result was received both Gemini 2.5 & Claude 3.7 Tool call ended before result was received (Again)

Hey @Artemonim ! Typically, these kinds of commands should be sent to the background, where they can run longer than any timeout. [Screenshot 2025-12-29 at 15.32.26] Is this happening in your case? Do you have a Request ID with privacy mode disabled that you can share?

On the contrary, I prohibit Agent from running background commands, as they don’t block its operation and Agent cannot access the results of their execution. I would even like a separate option to disable this functionality. I use local CI in my projects (the concept can be seen in the abandoned Ag…

Thanks @Artemonim . I think the goal is to fix this: [image] Artemonim: Agent cannot access the results of their execution. Rather than infinitely increase the timeout.

The question is also that the Agent must wait for this terminal to be executed. If the terminal process takes 20 minutes, will Agent wait for it? By the way, the OpenAI Codex has an interesting implementation: you can simply warn the agent to launch the terminal with a 20-minute timeout, and then i…

Would the ideal scenario be that your agent is completely blocked for those 20 minutes, or that you can continue working? I’m thinking about something like a subagent who goes and runs the long-running terminal and reports back. [image] Artemonim: and then it will know that the terminal can run…

[image] Colin: Would the ideal scenario be that your agent is completely blocked for those 20 minutes Yes, I expect the Agent to launch the terminal and wait for the terminal to finish its work. If the terminal can hang indefinitely, then that’s a flaw in the script running in the terminal, …

[image] Colin: We do have a fix on the way (might already be merged) to distinguish between terminal timeouts and “user abort”, which you ran into. If I understand correctly, after this update, the Agent was able to set the terminal timeout — thank you so much! That solved the problem. UPD: …

[image] Artemonim: That solved the problem. UPD: That isn’t -_- Request ID: 9aefa9f9-5485-47ce-b5bf-ae8bf8efbf4f You’re gonna need to give me a bit more to go off of. :slight_smile: What happened?

Agent was interrupted after working in the console for a long time

Support Bug Reports

Artemonim (Artemonim) December 27, 2025, 5:36pm 2

Tool call ended/ User aborted request
Tool call ended before result was received, 2025 Oct
Tool call ended before result was received both Gemini 2.5 & Claude 3.7
Tool call ended before result was received (Again)

Topic		Replies	Views
Timeout setting on terminal/shell Agent tool Bug Reports terminal	6	599	February 8, 2026
Agents being stopped and falsely attributed to me Bug Reports terminal	9	107	January 23, 2026
Composer agent sending interrupts (^C) for long runs Bug Reports	4	279	February 6, 2025
Why do agents request sleep terminal commands Discussions terminal	4	177	March 22, 2026
Cursor cannot handle terminals properly, W11, WSL2 Bug Reports	3	432	July 11, 2025

Agent was interrupted after working in the console for a long time

Related topics