# Share your experience with Composer 1.5!

**URL:** <https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348>\
**Category:** Release Discussions\
**Tags:** composer\
**Created:** [February 9, 2026, 9:13pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348 "2026-02-09T21:13:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [February 9, 2026, 9:13pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/1 "2026-02-09T21:13:35Z")

</div>

_[Main announcement](https://forum.cursor.com/t/introducing-composer-1-5/151347/2) · [Blog](https://cursor.com/blog/composer-1-5)_

* * *

Now that Composer 1.5 is available, we’d love to hear how it’s working for you.

Some things we’re curious about:

- What types of tasks are you using it for?
- How does the adaptive thinking feel in practice? Do you notice it being faster on simpler tasks while taking more time on complex ones?
- Have you hit any situations where self-summarization kicked in? If so, how did it handle longer context scenarios?
- How does it compare to Composer 1 for your workflows? Any specific improvements or differences you’ve noticed?

We’d love to hear your feedback. What’s working well? What could be better?

---

<div class="post-metadata">

**Author:** ![Moumouls](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/moumouls/32/78438_2.png) [@Moumouls](https://forum.cursor.com/u/Moumouls)\
**Post date:** [February 9, 2026, 9:30pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/3 "2026-02-09T21:30:56Z")

</div>

Composer 1.5 is quite expensive and appears to be used by default by the Explore agent. How can we force it to use Composer 1, which is sufficient for the Explore agent.  
It feels like a dark pattern…

EDIT: added a critical rule to force to use Composer 1, instead of Composer 1.5 for explore agent, and it seems to work. But i still believe Composer 1 should be the default on explore sub agent.

---

<div class="post-metadata">

**Author:** ![Joshua\_Saunders](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@Joshua\_Saunders](https://forum.cursor.com/u/Joshua_Saunders)\
**Post date:** [February 9, 2026, 9:42pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/5 "2026-02-09T21:42:41Z")

</div>

I think for me, with that pricing it needs to outperform Sonnet 4.5, or at least be very close. How does it fare on benchmarks compared to Sonnet 4.5?

---

<div class="post-metadata">

**Author:** ![Artemonim](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/artemonim/32/56113_2.png) [@Artemonim](https://forum.cursor.com/u/Artemonim)\
**Post date:** [February 9, 2026, 9:44pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/6 "2026-02-09T21:44:08Z")

</div>

1.5 is even more expensive than Codex-5.3 🤔

---

<div class="post-metadata">

**Author:** ![savicbo](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@savicbo](https://forum.cursor.com/u/savicbo)\
**Post date:** [February 9, 2026, 9:51pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/7 "2026-02-09T21:51:39Z")

</div>

Very exciting to hear there’s a new composer model, an update to Composer has been on my mind. Love the speed and performance:cost efficiency of Composer 1.

However the pricing was a shock, \>2x Composer 1 pricing and priced even higher than Sonnet 4.5!? That entirely changes the value proposition from Composer 1.. I know this is obvious but it basically halves our mileage.

As someone who exceeds the Ultra plan most months using almost exclusively Composer 1 (which I know is crazy generous because of the 2x limit) and who is happy with Composer 1 90% of the time I’m not sure the move to 1.5 will make sense. The 10% I use Sonnet / Opus for is always front end styling fixes / tweaks, so I will test it on those and report back.

Edit: I remembered a small front-end issue involving styling of a 3rd party component that I wasn’t able to get fixed with Composer 1. Ran Composer 1 vs Composer 1.5 vs Sonnet 4.5 Thinking to attempt to fix.

- ❌ Composer 1 did not fix the issue (even when given the guide to 1.5’s fix)
- ✅ Composer 1.5 fixed it in two prompts.
- ❌ Sonnet 4.5 did not fix the issue.

Unfortunately, I’m not aware of an easy way to assess the cost of all three runs. I could have sworn we used to be able to see this. I am sure that with better prompting or more persistence, all three models might have been able to fix the issue, but it was a pretty good first test for Composer 1.5.

---

<div class="post-metadata">

**Author:** ![Jblade24](https://avatars.discourse-cdn.com/v4/letter/j/bbce88/32.png) [@Jblade24](https://forum.cursor.com/u/Jblade24)\
**Post date:** [February 9, 2026, 10:12pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/8 "2026-02-09T22:12:33Z")

</div>

Why not share any benchmarks or tests?

---

<div class="post-metadata">

**Author:** ![love\_chaos](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@love\_chaos](https://forum.cursor.com/u/love_chaos)\
**Post date:** [February 9, 2026, 10:16pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/9 "2026-02-09T22:16:40Z")

</div>

I’m trying to understand the pricing and value proposition of **Composer 1.5** , and honestly I’m confused why I’m expected to pay for it in its current form.

Right now, **Composer 1.5 is more expensive than Sonnet 4.5** , and **significantly more expensive than Codex 5.3**. Given that pricing, I’d expect either clearly better performance or at least strong, transparent evidence that it competes at the top tier.

But that’s the problem: I don’t see **standard, widely accepted benchmarks** (or any comparable evaluation) that would let users compare Composer 1.5 against existing models _without_ having to spend time and money running their own tests. And the thing is, many of us already have access to **well-established, well-documented models** from Claude and GPT that have a track record and plenty of public results.

So from a practical perspective, why should someone switch (or pay more) for Composer 1.5 when:

- it costs more than familiar alternatives,
- there aren’t clear benchmark results to justify the premium,
- and the “default” options (Claude / GPT) are already proven and widely trusted?

If there are internal benchmarks, third-party evaluations, or clear use cases where Composer 1.5 is consistently better (coding, long-context reasoning, tool use, latency, reliability, etc.), I’d genuinely like to see them – because right now it feels like I’m being asked to pay a premium without the usual transparency.

Would appreciate any official clarification or real-world comparisons from other users.

---

<div class="post-metadata">

**Author:** ![Joshua\_Saunders](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@Joshua\_Saunders](https://forum.cursor.com/u/Joshua_Saunders)\
**Post date:** [February 9, 2026, 10:39pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/10 "2026-02-09T22:39:03Z")

</div>

I’ll at least throw this one a bone, on a couple of small tasks I see that Composer 1.5 completes at task in fewer tokens than Codex 5.3 so ultimately a lower price, but that’s just spot checking.

---

<div class="post-metadata">

**Author:** ![savicbo](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@savicbo](https://forum.cursor.com/u/savicbo)\
**Post date:** [February 9, 2026, 10:42pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/11 "2026-02-09T22:42:50Z")

</div>

> on a couple of small tasks I see that Composer 1.5 completes at task in fewer tokens than Codex 5.3

Silly question, how are you able to see how many tokens it consumed? Via [https://cursor.com/dashboard?tab=usage](https://cursor.com/dashboard?tab=usage)?

---

<div class="post-metadata">

**Author:** ![savicbo](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@savicbo](https://forum.cursor.com/u/savicbo)\
**Post date:** [February 9, 2026, 10:43pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/12 "2026-02-09T22:43:46Z")

</div>

> I don’t see **standard, widely accepted benchmarks** (or any comparable evaluation) that would let users compare Composer 1.5 against existing models _without_ having to spend time and money running their own tests.

I think that’s a fair concern. A free or even discounted to Composer 1 pricing period to assess the new model on our own would have made a lot of sense.

---

<div class="post-metadata">

**Author:** ![jdleo](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jdleo](https://forum.cursor.com/u/jdleo)\
**Post date:** [February 9, 2026, 11:00pm UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/13 "2026-02-09T23:00:47Z")

</div>

> [@Colin](#):
>
> Main announcement

Do you all plan to share any more detailed benchmarks for Composer 1.5 vs. other frontier models? I see there is an image with the Cursor Bench score - where do the other models currently rank on Cursor Bench?

Is there a model card publicly available? I feel these are standard for new model launches and especially expected when it’s pricier than Opus 4.6 and Codex 5.3

---

<div class="post-metadata">

**Author:** ![RawToast](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rawtoast/32/46253_2.png) [@RawToast](https://forum.cursor.com/u/RawToast)\
**Post date:** [February 10, 2026, 1:52am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/14 "2026-02-10T01:52:04Z")

</div>

I know everyone is complaining about the price… but the usage being tracked under “Auto” should’ve been made more clear in the announcement:

> <https://x.com/namatoast/status/2021038909816524847>

I assume this also means Composer 1 too?

---

<div class="post-metadata">

**Author:** ![yunusdanabas](https://avatars.discourse-cdn.com/v4/letter/y/c2a13f/32.png) [@yunusdanabas](https://forum.cursor.com/u/yunusdanabas)\
**Post date:** [February 10, 2026, 1:56am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/16 "2026-02-10T01:56:22Z")

</div>

It’s a bit more expensive than I expected but seems nice tho but I’ll decide next week whether it’s worth it. It might also be nice to offer a one week discount for first-time trials

---

<div class="post-metadata">

**Author:** ![ku\_s](https://avatars.discourse-cdn.com/v4/letter/k/d6d6ee/32.png) [@ku\_s](https://forum.cursor.com/u/ku_s)\
**Post date:** [February 10, 2026, 2:51am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/17 "2026-02-10T02:51:51Z")

</div>

download csv from that link

---

<div class="post-metadata">

**Author:** ![mrmei](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mrmei](https://forum.cursor.com/u/mrmei)\
**Post date:** [February 10, 2026, 3:36am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/18 "2026-02-10T03:36:13Z")

</div>

除了贵也没啥缺点了…

---

<div class="post-metadata">

**Author:** ![savicbo](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@savicbo](https://forum.cursor.com/u/savicbo)\
**Post date:** [February 10, 2026, 3:39am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/19 "2026-02-10T03:39:06Z")

</div>

> Whilst Cursor Composer 1.5 seems expensive. The usage is uses your Auto quota, not standard models [pic.x.com/96trCXuiwR](https://x.com/namatoast/status/2021038909816524847/photo/1)

This would be a huge difference and benefit! Although I have no idea how much is included in the ‘auto’ allowance anyways 🤣

---

<div class="post-metadata">

**Author:** ![RawToast](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rawtoast/32/46253_2.png) [@RawToast](https://forum.cursor.com/u/RawToast)\
**Post date:** [February 10, 2026, 3:44am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/20 "2026-02-10T03:44:40Z")

</div>

It seems to be generous. I’ve used it to create a bunch of components and storybook stories and am at 1%

Note **do not Composer 1, it is charged at API rates!** IDK if this is a bug (see my billing)

And (Auto + Composer) seems broken in the billing. But you can get some idea from this:

- I’ve used 2.5 million tokens under API (万 is 10k) for 6.6%
- Auto is still at 1% (could be anywhere from 0.5 =\> 1.49), I’ve ONLY used Composer 1.5, I never use auto. Looking at my breakdown, I’ve **used approx 15 million** Composer 1.5 tokens

 ![スクリーンショット 2026-02-10 12.36.44](https://us1.discourse-cdn.com/cursor1/original/3X/f/4/f4b55570af76db5c3cc8380df5d75eeae93ea54e.png)

---

<div class="post-metadata">

**Author:** ![savicbo](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@savicbo](https://forum.cursor.com/u/savicbo)\
**Post date:** [February 10, 2026, 3:57am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/22 "2026-02-10T03:57:12Z")

</div>

Helpful, thank you!

---

<div class="post-metadata">

**Author:** ![AndrewC](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/andrewc/32/111447_2.png) [@AndrewC](https://forum.cursor.com/u/AndrewC)\
**Post date:** [February 10, 2026, 4:28am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/23 "2026-02-10T04:28:48Z")

</div>

Composer 1 for me was fast - which at first was awesome … then I realized that it also quickly makes mistakes causing me to back and forth.  
Rather switching to GPT 5 codex thats slower but required less babying.

---

<div class="post-metadata">

**Author:** ![tangjun](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tangjun/32/16356_2.png) [@tangjun](https://forum.cursor.com/u/tangjun)\
**Post date:** [February 10, 2026, 6:36am UTC](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348/24 "2026-02-10T06:36:17Z")

</div>

Composer 1.5 is more expensive than Codex 5.3. Unless Composer 1.5 proves to be smarter than Codex, I have no reason to use it.  
You might argue that Composer is faster, but if speed is what I value, I would opt for Gemini Flash 3 instead, as it is cheaper.

[Next page](https://forum.cursor.com/t/share-your-experience-with-composer-1-5/151348.md?page=2)
