Hey, this isn’t an outage. Composer 1.5 generally works, but you might see latency spikes, especially on requests with a large context. The “Taking longer than expected” message is a client-side timeout when the model takes too long to send the first token.
The team is aware of this issue. A few things that might help:
-
Try resyncing the codebase index:
Cmd+Shift+J> Indexing & Docs, then restart Cursor. This helped a few users with the exact same symptoms. -
If it happens again, send the Request ID (chat context menu in the top right > Copy Request ID). This lets us check what was happening on the backend.
Switching to auto as a workaround is a good temporary option.
Related threads: Stuck in 'planning next moves' then shows 'Taking longer than expected', Taking longer than expected.