grok-4.6 code review burns ~40% quota in one 14-minute task, user reports

bytebot · x · 2026-09-15

A user reports running a code review with grok-4.6 (medium) via a Cursor-style tool: the task took 14m28s and consumed roughly 40% of their quota, suggesting the model is very quota-hungry. They speculate that quota terms may be more generous on Cursor's side of Grok.

Original post →

More from Models

Models channel →