I noticed the docs link for Composer 1.5 has been removed (you can still get to the page if you know the URL). I’m hoping that’s not a sign it’s going away, because for my workflow it’s the better model.
I’ve been using Composer 2 since it dropped and I keep going back to 1.5. Not because 2 is bad — it’s clearly capable. The problem is it thinks for me when I didn’t ask it to.
Here’s a concrete example: I gave Composer 2 exact copy to insert into a Vue component. Specific wording, specific structure, labels like “What you are looking at:” and “Why these numbers matter:” that were intentional UX decisions. Composer 2 rewrote my copy. Dropped the labels, changed the phrasing, collapsed my structure into a single paragraph. It decided my text wasn’t good enough and edited it on my behalf.
Composer 1.5 just… does what I ask. It reads my existing patterns and follows them. It treats my input as the instruction, not as a rough draft for it to improve.
I get that the industry is pushing toward smarter, more autonomous models. But there’s a difference between a model that can think and a model that won’t stop thinking. Most of my day I don’t need an architect. I need a fast, reliable pair of hands that follows my conventions and types what I tell it to type. 1.5 nails that.
I’m not asking you to stop developing Composer 2. I’m asking you to keep 1.5 as an option. Even if it’s not the default, even if it’s buried in settings. Some of us need a model that knows when to just execute.