Users Blame Grok's Context Churn for Exploding Usage Limits

Users accuse Grok's bot of severe context bloat: once context exceeds a threshold, per-turn full-context reads cause usage to spike, with token accounting suggesting quotas deplete faster after a subscription merger despite identical usage.

2026-10-21 ~ 2026-10-22 · 3 related posts

• Grok Users Hit by Context Bloat: Quota 'Evaporates Exponentially' Past a Threshold — alexcovo_eth · 2026-10-21
• Context churn: why Grok bot usage tanks once context passes 25-30% of the window — alexcovo_eth · 2026-10-22
• 1.2B tokens before and after: user says Grok merged plan effectively got stingier — HandsomeHank_ · 2026-10-22