What on earth are you guys doing with Grok 4.7!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Is the rumor about Grok 4.7 severely draining tokens actually real?
I’ve burned through two Cursor Ultra plans only to end up with an utterly disappointing result, with nowhere to even vent my frustration.
Every single task takes over 60 minutes just to locate where the issue is, deep-“thinking” across every file in the project. It drains my Ultra tokens at a dizzying speed, yet ultimately fails to fix even a basic queue bug in my code.
It’s truly a shame that patient people like me are forced to look for a place just to pour out everything we’ve had to endure.

English Nuances Used:

Steps to Reproduce

Every single task takes over 60 minutes just to locate where the issue is, deep-“thinking” across every file in the project. It drains my Ultra tokens at a dizzying speed, yet ultimately fails to fix even a basic queue bug in my code.

Operating System

Windows 10/11

Version Information

Version: 3.20.21 (system setup)
VS Code Extension API: 1.128.0
Commit: f09fca384ceca23f7bf21f9c23655b162641d740
Date: 2026-09-13T19:02:51.781Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26300

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 posts were merged into an existing topic: Share your Thoughts on Grok 4.7