Cursor latest "nightly" fails to run both plan and agent

Support Bug Reports
, ,
3

Hey, I see you’ve hit this again. It’s the same “Agent Execution Timed Out” error as last time, but now on nightly 2.7.0.

Since you’re on the nightly track, regressions like this can happen between builds. Here are a few things to try on 2.7.0:

  • Clear the workspace state again. Old state from 2.6.x can conflict with 2.7.0:

    • Fully close Cursor
    • Delete or rename: C:\Users\[your username]\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
    • Reopen Cursor. You’ll need to sign in again

  • Start without extensions: cursor --disable-extensions

    • If it works, turn them back on one by one to find which one is causing it

  • If neither helps, staying on 2.6.12 is a solid workaround until the next nightly build ships with a fix.

Let me know how it goes.

1 Like