Composer 2 is actually sick

Ideas Feedback
,
1

Wow, so here I am again. And this time, it’s not to complain about Cursor (yes, I’m experiencing a bug where I had to disable extensions because I was getting crashes and 100% CPU usage when agents do anything), but to praise COMPOSER 2.

I brought a UX-UI overhaul markdown plan for a relatively humongous codebase to Composer 2 (not Composer 2 fast), and it’s been chugging along with this task. The model has been stopping after each phase and microphase of work and getting feedback. Works well with Skills.

I’m not sure how the model behaves without a well-thought out markdown plan, but let me tell you – it’s been doing some amazing work with one.

Kudos!!! And the amount of usage you’re allowed with this model is amazing. You folks should try it out, but just know what you’re trying to do – and USE PLANS! They’re not hard to have AI create for you.

3

Hey, thanks for the feedback, it’s always great to hear when things click.

About the crashes and 100% CPU when agents run, we’ve seen similar reports from a few users. If you get a chance, it’d be really helpful if you could open a separate bug report with:

  • Your Cursor version and OS
  • Which extensions were causing the issue, if you narrowed it down
  • Steps to reproduce, if possible

That way the team can investigate it properly. Glad the disable extensions workaround is keeping you unblocked for now.