Composer 1.5 Performance Issue

Support Bug Reports
, ,
1

The Composer 1.5 model performance in Cloud Agents is extremely slow. It’s been running for over 30 minutes on a simple task.

3

Hey, thanks for the report. This is a known performance issue with Composer 1.5, and the team is aware and tracking it.

To help with debugging, can you share a couple of things:

  • The Request ID from the problematic Cloud Agent session (in Cloud Agents you can find it via the chat menu, then Copy Request ID)
  • What was the task? Rough repo size, and what exactly were you asking it to do?
  • Did the task eventually finish, or did it stay stuck?

In the meantime, if you need results right now, try running the same task with a different model (Claude 4.6 Sonnet, for example) as a workaround.

Let me know how it goes.

4

There is more to this problem, I’ve noticed a stark difference changing, unintentionally, from opus to composer 1.5. A simple request caused the model to repeatedly loop through the task, use 3.5M tokens and still return tens of lines of unnecessary, unrequested edits including removing or adding blank lines and altering comments. switching back to opus solved the issue in a few seconds. And even more bizarre, clicking the undo button on each individual edit caused the line to be pasted back into the document multiple times.

c91cfa1a-b239-4f07-bfef-894546bc2782

a12201f6-aac8-4989-81fc-70526e1ff405

5

Same. I’ve seen loops, and too much thinking. Please bring back composer 1 :confused:

6

@DanSt - thanks for the Request ID and the detailed write-up. The 3,5M-token looping and the unnecessary edits are exactly the kind of signal that helps the team track down the root cause. I’ve passed those IDs along.

@Kristian_Gerardsson - the loops issue and excessive thinking are on our radar. The team is aware and is tracking it.

For now, the recommendation is the same. If you need results right now, switch to a different model. Claude 4.6 Sonnet or Opus work well as a workaround. Once we have updates on Composer 1.5 stability, we’ll post them here.

@Nick_Loeper - if this is still happening, please share the Request ID from that session. It’ll help with the investigation.

7

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.