I’m experiencing an issue with Composer 2 where it continuously reverts and reapplies code changes in a loop. This happens without any clear trigger and is frustrating because it wastes tokens unnecessarily.
Steps to Reproduce
Not entirely consistent, but it occurs during normal usage while editing files.
Expected Behavior
Code changes should remain stable after being applied.
Hey, thanks for the report and the Request ID. We were able to confirm the issue in the logs.
This is a known pattern where the model doesn’t realize its edits were already applied, so it keeps trying to apply them again in a loop. We’ve seen similar behavior with other models too: Agent stuck in editing loop
I’ve passed this to the team. There isn’t a specific ETA yet, but your report with the Request ID helps us prioritize it.
As a workaround, if the loop starts, stop the agent manually and try switching to another model (Claude Sonnet 4.6 or Auto) for that task. Starting a new chat instead of continuing the current one can also help.
I’ve noticed this happens more frequently when there are staged changes.
When the working changes are already staged, the agent seems even more likely to get stuck in the edit loop and repeatedly reapply the same edits.
Hey, thanks for the extra info, that’s a helpful signal.
If you notice any more patterns like specific file types, diff size, or which tools are in the chain right before the loop, drop them here, especially with the Request ID. I don’t have anything new to share on the ETA yet, but once there’s an update I’ll reply in the thread.
As a workaround if you hit it again, stop the agent, commit or unstage your current changes, then restart the task in a new chat, or switch to Claude Sonnet 4.6 / Auto for that step.
Hey @tobe500, just checking in on this one. Are you still getting stuck in the apply and revert loop with Composer 2, or has it stopped on a newer version?
If it’s still happening, could you share a fresh Request ID from a recent case? Ideally one where you also had staged changes, since you mentioned that pattern in #8. Anything else you’ve noticed, like specific file types, big diffs, or what tools you ran right before the loop starts, would help too.
If it’s gone, just let me know and I’ll close this out.