Claude AI Spends 81 Minutes on 'Real Thinking' – User Report Spikes Around Major Updates

A Reddit user reports that Claude AI recently spent 1 hour and 21 minutes of "real thinking" time on a simple task, producing a good result. The user speculates a recurring pattern: performance seems to spike for the first 1–2 hours after a major update or new feature release, then returns to baseline.
Key Observations
- Last month, the same user created a research thread that successfully scanned 5,113 sources (linked in original post).
- Since then, they have been unable to replicate that level of performance—subsequent attempts scan at most 100–200 sources and yield average results.
- The user hypothesizes that early adopters of new features occasionally get a "mythos-like" boost in reasoning capabilities, which later normalizes.
This anecdotal evidence suggests Claude's "real thinking" mode may be subject to backend variability, possibly due to model caching, allocation of compute resources, or gradual rollout of updates. Developers relying on Claude AI for deep research tasks may need to account for this inconsistency, treating early-access features as a best-effort spike rather than a guaranteed capability.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude Code v2.1.128: OTEL isolation, MCP fixes, plugin .zip support, and 20+ bug fixes
Claude Code v2.1.128 stops subprocesses from inheriting OTEL_* env vars, adds .zip plugin support, fixes MCP reconnection flooding, and fixes parallel shell tool cancellation.

OpenClaw Hosts Its First AMA: Insights into AI Coding Agents
OpenClaw, a prominent figure in AI coding agents, hosted its first AMA on Reddit. The discussion shed light on its impacts, future plans, and challenges.

Qwen3-30B-A3B vs Qwen3.5-35B-A3B Performance Comparison on RTX 5090
A head-to-head benchmark of Qwen3-30B-A3B and Qwen3.5-35B-A3B on an RTX 5090 shows the 30B model is 35% faster in generation, while the 3.5 model handles long context better with flat token scaling versus the 30B's 21% degradation.

Vibe Coding vs. Production Reality: The Undiscussed Liabilities
Reddit user External_Bobcat8183 highlights the gap between fast PoCs with vibe coding and real production issues: auth, secrets, GDPR, rate limiting, multi-tenancy.