Grok 4.7 just thinks too much
Originally published on LinkedIn
๐๐ฟ๐ผ๐ธ ๐ฐ.๐ณ ๐ท๐๐๐ ๐๐ต๐ถ๐ป๐ธ๐ ๐๐ผ๐ผ ๐บ๐๐ฐ๐ต I was looking forward to Grok 4.7 when announced in Cursor.
Recently Iโd settled into a workflow that was working really well:
๐๐ฟ๐ผ๐ธ ๐ฐ.๐ฒ ๐ณ๐ผ๐ฟ ๐๐ต๐ถ๐ป๐ธ๐ถ๐ป๐ด ๐ฎ๐ป๐ฑ ๐ฝ๐น๐ฎ๐ป๐ป๐ถ๐ป๐ด + ๐๐ผ๐บ๐ฝ๐ผ๐๐ฒ๐ฟ ๐ฎ.๐ฑ ๐ณ๐ผ๐ฟ ๐ฒ๐ ๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป. Switching off Fast Mode also put the pricing in a really nice place and fast enough. I'd pretty much moved completely away from Claude models.
Good reasoning, fast execution, decent quality, sensible cost. I already know the best frontier models just aren't needed for general software engineering and the balance was right. I had a great experience switching in 4.6 in to my workflow, so Grok 4.7 seemed like it would just be a free boost, seemingly offering the same sort of price with a better model.
I assumed it would be an easy switch. It wasnโt easy, 4.7 is too different to 4.6, it was just costly in time and money.
The problem is simple: ๐ถ๐ ๐ท๐๐๐ ๐๐ต๐ถ๐ป๐ธ๐ ๐๐ผ๐ผ ๐บ๐๐ฐ๐ต.
When Iโm building a decent-sized feature, I already do the thinking upfront. I work through the technical design, define the constraints, produce a plan with AI, then execute.
With 4.6, that worked brilliantly. With 4.7, it thought.. and thought.. and thought some more.
๐ง At one point it spent longer thinking about a feature than Grok 4.6 + Composer would have taken to plan and build the entire thing.
Meanwhile, the token usage kept climbing. Thatโs the bit I think gets missed when we talk about model pricing. A model can cost the same per token, but if it burns far more tokens getting to the answer, your ๐ฟ๐ฒ๐ฎ๐น ๐ฐ๐ผ๐๐ ๐ผ๐ณ ๐ด๐ฒ๐๐๐ถ๐ป๐ด ๐๐ผ๐ฟ๐ธ ๐ฑ๐ผ๐ป๐ฒ is much higher.
For day-to-day coding, that breaks the flow for me. Iโd much rather: โก Build quickly ๐ Test and iterate ๐ Pull in a bigger model afterwards for code review, cleanup and missed edge cases
That feels far more productive, iterative and agile, than throwing the biggest-thinking model at every task from the start.
The whole point of AI for me is to amplify the engineer. I make the architecture decisions, define the technical design and provide the context. Then I want the AI to do the grunt work and help me move faster.
Grok 4.6 gave me that balance coupled with the reliable work horse Composer 2.5 (which does miss bits if not guided with a good plan).
So far, 4.7 feels like it has pushed too far towards reasoning at the expense of execution. I'm not even sure the results were much better, 100% not worth the cost and time for me at least.
Maybe itโs great for huge, long-running tasks where youโre happy to let an agent disappear for hours or days and token costs aren't a concern for you, but thatโs not how I want to work.
๐ ๐๐ฎ๐ป๐ ๐๐ ๐๐ผ ๐บ๐ฎ๐ธ๐ฒ ๐ฑ๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐บ๐ฒ๐ป๐ ๐บ๐ผ๐ฟ๐ฒ ๐ฎ๐ด๐ถ๐น๐ฒ, ๐ป๐ผ๐ ๐น๐ฒ๐๐.
How is everyone else is finding Grok 4.7 in Cursor. Better results, or just more thinking? I've relegated it to too slow and expensive group of models for day to day coding.