This issue has been tracked in several places recently, with very vague responses. This week, without any update, foreground commands suddenly started timing out. My team uses various scripts that can run for more than 10 minutes, sometimes 30 minutes or more.
This completely broke our productivity, because our agents could no longer self-correct or run our tests.
As an emergency workaround, I worked on forcing the use of “run in background,” but the agents then overused sleep and tail to check test results. This is far from optimal, and the AI loop becomes very fragile.
I also had to do reverse engineering and prompt engineering to force the agent to use a while loop and wait for an exit code. But suddenly, 24 hours later, without any Cursor update, the format of background terminals changed and once again broke our feedback loop.
Then we noticed that foreground commands no longer seem to time out again (once more, without any update to the Cursor app on our side).
We no longer understand what is happening. Our team uses Ultra plans, and we are faced with software that changes critical behaviors without any warning.
Is it possible to get a detailed explanation? Codex, OpenCode, and Claude Code do not seem to have this type of issue, which makes us consider switching systems, even though we really like Cursor.
All of this is very worrying, and in a company context it is simply not acceptable to have this kind of instability on our side for a 200$/month/user tool