Composer 2 It's trash!

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I’m having serious problems with Composer 2 that didn’t occur in previous versions: loss of context, loss of modified source code, unsuccessful implementations with a high error rate, as well as basic Python syntax problems.

I’ve lost a significant portion of my AI credits having to fix problems generated by the AI ​​itself, which is clearly not ready for use.

I really like the cursor, but something clearly needs to be done urgently with Composer 2, which has been a terrible experience and has harmed my projects more than helped them.

Steps to Reproduce

Just by using composer 2 in more complex projects. The times that the context is lost and implementations are made out of the dev instructions it’s really alarming.

Expected Behavior

Enable downgrande to composer 1.5 again.

Operating System

Windows 10/11

Version Information

Version: 2.6.22 (system setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
5

Hey, thanks for the feedback. We hear you. Composer 2 is still actively being improved, and reports like yours help us understand where the gaps are.

A couple of things:

  1. If you’re hitting specific cases where context is lost or code is broken, it’d really help if you could share some Request IDs (top-right menu in chat > Copy Request ID). That lets us investigate what went wrong on the backend.

  2. In the meantime, you can still pick other models, like Claude 4.6 Sonnet or Opus, from the model picker if Composer 2 isn’t working well for your project.

  3. We also have an official feedback thread just for Composer 2 experiences. It’d be great if you could add your detailed feedback there too: Share your experience with Composer 2!

The team is aware of various quality concerns around Composer 2, and your report helps with prioritization. Let me know if you can share those Request IDs. That’s the most actionable thing right now.

6

A post was merged into an existing topic: Share your experience with Composer 2!