Kimi's 5-Hour Context Window Accused of Quota Bug: Progress Jumps Without Action
evilsocket · x · 2026-08-12
A developer reported a billing or logic bug in Kimi's 5-hour long-context window. After a task was interrupted due to hitting the 5-hour quota, attempting to resume the task caused the progress and quota consumption to inexplicably jump to 10.4% instantly, without any tool calls, file reads, or model thinking taking place.
More from Models
- Users Accuse Anthropic of Cooked Evals, Claiming Real API Performance Lags — GabGarrett · 2026-08-12
- Encrypted Chain-of-Thought in Proprietary LLMs Can Be Extracted via Weaker Sibling Models — Simon Willison · 2026-08-12
- GPT vs Claude: Which Model Better Understands Your Intent? — nickbaumann_ · 2026-08-12
- Expert Warns AI Watermarks Could Increase Code Entropy, Harming Coding Agents — wightmanr · 2026-08-12
- e/acc's Beff Jezos flags a 'vibe shift' as more users daily drive Grok — beffjezos · 2026-08-12
- Kimi K3 Distillation Controversy: Authors Admit No Proof, Likely Data Contamination — bookwormengr · 2026-08-12