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.