Hey, thanks for the report. In the screenshot, I can see that Composer-1 is stuck in an infinite loop with the same thinking process “Reviewing the relevant files to understand the current implementation” - this indicates a problem with thinking logic or context management.
Create a new Composer session (+ button) - this often fixes the problem
Cancel the current prompt (Cancel/Stop button)
Try a different model (GPT-5 Codex, Claude Opus) - if it works, the problem is specific to Composer-1
Check DevTools (Help > Toggle Developer Tools) for errors
This isn’t a common issue with Composer-1, but it sometimes happens with certain context combinations. If the problem happens again, create a new chat and see if it reproduces.
Thanks for the quick reply. Dev tools (console) screenshot below. This error displays once I click stop. I tried opening up multiple chats, all the same with Composer-1. Other models work fine.
Just tried again and Composer-1 seems to be working… at least for the moment. Any ideas on what happened? It burned through some credits from looping, ugh.
I also had this issue yesterday. It was happening with chats in plan mode, and I ended up testing it with the following simple prompt:
Please create an example plan. Focus it on the <my_main_project_name> project. Make it have 3 steps. Come up with an improvement for the way that URLs are handled for navigating through the app.
Here’s the response I got:
Exploring the current navigation/routing setup in <my_main_project_name> to understand how URLs are handled.
</think>
Reviewing the current routing setup to understand how URLs are handled.
</think>
Reviewing the current routing setup to understand how URLs are handled.
</think>
Reviewing the current routing setup to understand how URLs are handled.
</think>
Reviewing the current routing setup to understand how URLs are handled.
</think>
And that last part repeated over and over until I stopped the chat. I switched to Sonnet and didn’t have the issue
Today after updating Cursor, the Composer model seems to be working normally again.
Like @emdizzle I’d like to know what happened, has the issue been completely resolved or is it an intermittent failure, and if credits can be refunded for those chats.
@deanrie Is there any update on if this issue has been resolved?
I haven’t had the issue happen again, but that’s mostly because I haven’t been using Composer very much anymore in my regular work, as this issue has lost my confidence in it. And I’m not inclined to test my prompts against multiple models to look for patterns and troubleshoot these issues because it wastes my tokens.
