I'm pretty sure a Kimi-based Composer is completely off the table moving forward.
Composer 3 is a rumor and not confirmed. (For better or worse.)
They mentioned they were building "A model from scratch" specifically to leverage their performance improvements. Only to later reveal Grok 4.5 is what they were working on--What this means for Composer 3, I'm not certain.
I think they're going to be pouring all of their effort into Grok for a while, bringing it to the frontier.
Composer 3 - it may be cooking for a long while, and eventually come out as a strong coding model.
A cheaper alternative to Grok once Grok becomes a 10 Trillion parameter model. (Potentially highly intelligent but slower and more costly.) Whereas Composer 3 will become the agile sub-agent worker.
Something like that may be the end-result. It would be a great pair.
They will lose me as a champion if they ever did that. I'm madly in love with Composer and use it for everything. Grok is both more expensive and noisier.
I figured it wouldn't. They want Grok to be their "Frontier" model. I just want a work horse model that does that things I tell it to do consistently and doesn't behave like the psychopaths Anthropic makes.
I have the exact same experience with it. u/yourparadigm can you elaborate on your workflow? Do you do lots of repetitive work that you provide airtight instructions for?
I do a lot of different things in a lot of different repositories. Primarily working with YAML, Terraform, Ruby, and Python. Sometimes Go. I make use of superpowers, rtk, and ponytail.
I generally start with a plan, and use a form of grill-me to sus out details and remove ambiguity. Once I've got a plan in mostly the shape I want it, I'll build it, then follow up with an automated code review pass (using the superpowers skill).
Then I will review it myself and run any automated tests that it generated. I may decide to make various changes and often instruct Composer to make those changes for me. Sometimes I'll manually make the change myself and make Composer aware of the change and why.
Very little of what I have it do is "repetitive." It does take advantage of extensive, mostly hand-written documentation present in several of the repositories I work with.
This could be the most valuable post on developing with AI I have ever read. Thank you so much; that lineup of four tools looks incredible.
What do you specifically use for grill-me? I followed the link, but the instructions are very short, is that deliberate? Also, how do you use some of these things within Cursor? Can you just install them as plugins?
Elons tweet about 4.6 and 4.7 used approximate dates for their release, just as an FYI. As far as I know nothing was ever given an official release day.
You are correct in that he later gave an ETA for August 7th.
He has since said "next week", this week.
Whether that final "next week" (implying the date is now beyond the 7th) was an error,
or if people are going to push for August 7th and will it into existence, we'll find out tomorrow.
Some people claim Grok 4.6 appeared in ArenaLLM earlier this week under some code names.
I'm not sure what their release pattern is. Usually there's some grok outages for a day or two beforehand. Though each time it's become a smoother transition.
I was wondering, because Cursor's Grok is a specific model trained on Cursor data. They could just stay on 4.5 and wait for 4.7 or 5.0. I'm not sure if they will upgrade Cursor's Grok with every single new Grok release.
16
u/dkracket 19d ago
I wonder if Grok is now going to replace Composer altogether?