Agent is waiting seconds instead of milliseconsd

tstcm
Thu, 30 Apr 2026 12:50:03 +0000
Bug Reports

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the middle of a browser QA testing process, the agent decided to wait 3000 seconds, then do some action, and then wait 5000 seconds. This makes me think there was a change in how agents decide the time they want to wait, i’ve never seen them wait for more than an hour for no reason. They probably wanted to wait milliseconds, not seconds

Steps to Reproduce

Go into a testing session for a feature for a frontend, that feature needs some time to load so the agent decides to wait. See if it mistakenly waits thousands of seconds instead of milliseconds

Expected Behavior

Waits a normal amount of time

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.5.17 (system setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Opus 4.6

For AI issues: add Request ID with privacy disabled

671f96e0-5058-482e-8ad3-a4b2def3b163

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 posts - 3 participants