Overengineered Answer, Zero Results. Kimi 2.6 Couldn’t Solve a Simple Bug

I just tried the Kimi 2.6 model that people keep hyping, just to fix a super simple bug in my Laravel project, a slider button issue using Swiper.js.

And wow… what a waste of time.
The response? Long, messy, going in circles, explaining things I didn’t even ask. It took forever just to get to something that looked like a solution. Then it started modifying my code like it knew what it was doing… and in the end? The bug wasn’t even fixed.

So yeah, not “a bit dumb”, this felt straight up dumb.

I’m using VS Code with Cline, and I literally joined this forum just to say this because I’m honestly annoyed. Spent all that time waiting, reading through that overcomplicated answer, and still ended up with nothing.

The most ridiculous part?
After going through all that nonsense, the real fix on my side was just… just a small JavaScript tweak. That’s it. No complicated refactor, no weird logic, just one simple line. And the AI didn’t even come close to suggesting it.

Here’s what actually fixed it (not even best practice, but at least it works):

     setTimeout(() => {

         document.querySelector('.swiper-button-next').addEventListener('click', () => {

            swiper.slideNext();

        });

        document.querySelector('.swiper-button-prev').addEventListener('click', () => {

            swiper.slidePrev();

        });           

        }, 1000);

Here’s what I got after wasting my time with Kimi 2.6 :
Click here to see the attachment.