Waiting time after command runs, is this normal?

Hi, i have been using cursor since “composer” was a view and not a model lol, and i have a question for the community and the devs, everytime any model tries to run a command (that is on the allow list) i have a 2 to 3 second delay before it actually runs, but after the command ends it ALWAYS take between 10 to 12 seconds to mark it as Correct/Confirm which is weird.

I first thought this was a common issue with Code Agents but after trying codex (cli and app), claude code and antigravity, they dont have this delay, why? do other people also experience this?

1 Like

From what I’ve observed, is this correct?

  1. Before a command actually runs → there is a delay of about 2–3 seconds

  2. After the command finishes running → there is a longer delay of about 10–20 seconds before the model starts responding / the answer appears

Questions:

  • Is my understanding correct?

  • Does this happen with all models or only some of them?

  • Did you check this in the Network tab?

  • Are you using VPN / company proxy / any special network setup?

Yes thats correct, it happens with all models, in all networks, one important distiction is the wait point AFTER the command its only while the agent still thinks the command is running, in this specific state:


If i press “Cancel” there after i already see the command output it doesnt take those 10 to 20 seconds, but i have to be in the chat clicking cancel every command so simple things do go from 5s to 1 minute actually, it happens with all commands after i press run. You can see it here, this command run 8s ago, and its still waiting for the command response:

I have tried in 3 different laptops, several different networks, i dont use any VPN or proxy so i just thought it was a general Cursor thing honestly, but it doesnt happend in codex or claude code.

I see — sounds like a Windows-specific issue. Are you running Cursor natively in Windows (without WSL)?

My recommendation: file a bug report on the Cursor Community Forum → Bug Reports section

Attach whatever details/screenshots you have, and include:
• Request ID
• Models used
• Cursor version
• OS (Windows / Mac / etc.)

This helps the Cursor team track and reproduce it more easily — especially since it seems Windows-related and technical.

I’m on Windows + WSL and can’t reproduce it myself, sorry I can’t help further. Hope the team picks it up via your Request ID!

Also, make sure you’re not in privacy mode when testing/reproducing.

Good luck!

Its native Windows yeah, last version on Cursor and windows, no problem, will file a bug report then, thanks for the help!

Linking for completeness. :folded_hands:

2 Likes