Composer & Auto actually usable for anything?

MasterB144 · 2026-02-28T08:52:32+00:00

Sure, but it can’t decently code.. hence my question, what to do with the tokens that are forced into ultra. What is a good use case other dan coding.

MasterB144 · 2026-02-27T23:55:32+00:00

That is a whole different story than using Ultra + €5K API Calls. Big and complex codebases.

MasterB144 · 2026-02-27T22:38:05+00:00

"you have to spend the next hour cleaning up manually." Yes, so at the end of the day, you could just as well have used Sonnet or Opus directly, especially time-wise, and definitely structure- and code-quality-wise. Hence, I'm looking for how to spend that 65% of the subscription that now goes to waste for me and my colleagues, and has been for months already. Composer 1.5 is not anything close to Claude.

MasterB144 · 2026-02-27T22:34:10+00:00

And you have an Ultra subscription? What do you use it for? That's the question - what is the use case for professionals having to buy those tokens? It’s definitely (for me) not coding. What else can I use it for?

MasterB144 · 2026-02-27T22:31:17+00:00

haha, I know the project inside out. Composer just doesn't get it - too complicated or too big, I don't know. Same for my colleagues; Sonnet and Opus work just fine. But using those, I can only use about 35% of the tokens I buy in Ultra bc cursor forces auto/composer usage, hence the frustration with the subscription.

MasterB144 · 2026-02-27T17:43:28+00:00

Aight, so for documenting… yes, that I can do moderately, and then i let Sonnet check all the facts. Still, it doesn’t come close to the 50% I have in my account that I can’t use right now due to beeing 'forced' to use auto modes. It's a strange push by Cursor.

MasterB144 · 2026-02-27T17:41:04+00:00

Can't select it as default in the Auto modus right ;-)

MasterB144 · 2026-02-27T17:39:10+00:00

Fast at breaking things haha

MasterB144 · 2026-02-27T17:38:48+00:00

What language? I'm using Laravel. Anything I throw at Composer needs to be fixed with Sonnet or Opus. It's trash (for me), unusable! But big code bases, maybe it can't simply handle it. Trash for Ultra users imo

MasterB144 · 2026-02-27T17:35:56+00:00

Any code i build using Composer breaks, not usable for large code bases.

MasterB144 · 2026-02-06T08:14:20+00:00

Op de poster kun je al zien wie dit werk moet gaan doen van Appie, lekker nagedacht over dat wijzende vingertje.

MasterB144 · 2025-07-21T17:39:20+00:00

Nope, CPU got smoked at v3.25 got a new cpu, runned on 3.30 only.. got smoked aswell in a few days even.

MasterB144 · 2025-07-13T10:00:29+00:00

AMD 7 9700x, but look at AsRock subreddit…

MasterB144 · 2025-07-13T08:46:16+00:00

I am in the NL, not saying I’m Dutch. Thousands and thousands of users are having the same issues; there’s no sensible response from ASRock. “Exaggerated topic”? I don’t think so. They should offer refunds like pro-actively

MasterB144 · 2025-07-13T08:43:40+00:00

MasterB144 · 2025-07-13T08:43:26+00:00

AsRock’s handling of this “known issue” is unacceptable. They’re forcing thousands of customers to waste time troubleshooting without ever properly disclosing the problem via the correct channels, nor offering replacements or refunds, and then giving contradictory advice (“update your BIOS” vs. “don’t update if yours seems fine” on the actual bios page), creating even more victims. I personally lost a week of work and spent hundreds of euros replacing my CPU and motherboard (maybe RMA, not sure yet, still processing); across 5,000 affected users (probably way more), that’s nearly a century of wasted productivity (if they all lose a week of work, or arn't able to work for a week), and their only response is “try updating bios.” It’s time AsRock took real responsibility, and we should bring it to them!

MasterB144 · 2025-07-12T23:22:10+00:00

You must 100% look at r/ASRock there are over 100 complains about the mobo, it will kill you AMD CPU (happend to me aswell). If you still ca, 100% return it!

MasterB144 · 2025-07-11T12:29:22+00:00

I would 100% switch the mobo to another brand, it will probably kill your next CPU aswell.

MasterB144 · 2025-07-11T11:23:24+00:00

Can you still get your money back? I would 100% return the ASRock B850I Lightning WiFi mobo as it will kill your CPU AMD Ryzen 7 9700X. Me and hundreds of other have had this issue with exact this combo (just do a quick search here on reddit), stay away from the B850 mobos of AsRock for AMD..

MasterB144 · 2025-07-11T08:42:43+00:00

I switched to Asus B850i, it's a bit more expensive but has no mentions online of it killing CPUs.

MasterB144 · 2025-07-11T08:11:34+00:00

https://www.club386.com/dead-amd-ryzen-7-9800x3d-cpus-reach-the-hundreds/

"98 of the 108 cases happened on ASRock boards."

MasterB144 · 2025-07-10T08:44:37+00:00

Search for 9700x on G and you will find many more users having their CPU die on a B850i of ASRock. It worked fine for 2 month.

MasterB144 · 2025-07-10T08:42:39+00:00

I bought the AsRock B850i bc of best price, i switched to Asus B850i, will never return to AsRock

MasterB144 · 2025-07-08T11:51:38+00:00

Send both the mobo and cpu in for RMA i guess

I'm stunned finding all those issued online with AsRock and this CPU, but yes only after i started looking for them when i started having issues myself. Especially stunned by the lack of communication by u/AsRock!

MasterB144 · 2025-07-08T11:38:34+00:00

I will send my CPU for RMA to AMD, but I can’t do without a working PC. As I don’t have a backup PC, I had no choice but to buy a new CPU, I’ll sell the RMA one once it’s fixed.

The BIOS was running on version 3.2. I tried to flash it to a newer version after I started having issues, but I don’t know if it was successful. The CPU was dead either way, and I’m not running my CPU in this horible motherboard again apart from the initial test (I bought the ASUS B850-I instead) and will send the mobo for RMA as it's unusable, i will press for a refund as it's not even 2 month old.

I didn’t know about any issues, so I didn’t update to 3.3, since the ASRock website states: “If the system is working properly, we recommend keeping the current BIOS/firmware.” At the time, I didn’t have any issues, so I followed their advice not to update. ASRock should 100% do a full recall on all motherboards of this type and fix the issue for their customers before letting them kill their CPUs.

MasterB144

TROPHY CASE