Detailed Analysis
A developer posting to the r/ClaudeAI community describes a marked degradation in the perceived speed of AI-assisted coding workflows with Claude between summer 2025 and the present, with planning phases now consuming 20 to 50 minutes and discrete implementation steps taking 5 to 10 minutes — timescales that contrast sharply with the rapid iteration cycles the developer recalls from roughly a year prior. The user reports having already undertaken extensive workflow optimization, including stripping down claude.md files, tightening system prompts, eliminating MCP integrations in favor of CLI tools, and actively maintaining a clean, agent-friendly codebase. Despite these measures, latency persists across model tiers, appearing even when using Sonnet rather than the extended-thinking Opus configurations (xhigh, max) the developer frequently employs.
Several compounding factors likely explain the experience, even absent model regressions. Extended thinking modes — explicitly referenced as xhigh and max — are architecturally designed to trade speed for reasoning depth, and their broader adoption in the intervening year means that what once felt like a fast model is now being used in a fundamentally different inference configuration. Additionally, codebases naturally accumulate complexity over time; tasks that were fresh and modular in summer 2025 may now require Claude to navigate substantially larger context windows, more interdependent files, and more nuanced architectural constraints — all of which increase token load and deliberation time independent of any change in model throughput. The developer's own diligence in keeping the codebase "agent-friendly" may have slowed the accumulation of this drag, but likely has not eliminated it.
The complaint also reflects a broader pattern emerging in the AI development community as the initial productivity euphoria of agentic coding tools gives way to the realities of long-horizon software maintenance. Early interactions with AI coding assistants tend to involve greenfield work — creating new files, scaffolding features, generating boilerplate — tasks that are inherently fast and low-ambiguity. As projects mature, AI assistants are increasingly asked to reason about side effects, preserve invariants, and plan across larger state spaces, which is structurally slower work regardless of model speed. The perception of slowness is thus partly a function of task mix evolution rather than pure capability regression.
From a product and research perspective, the post surfaces a genuine tension in the current generation of AI coding tools: the push toward more reliable, plan-before-act behavior — which has been a deliberate design direction for frontier models including Claude — necessarily increases latency in exchange for coherence and correctness. Anthropic's extended thinking features and multi-step planning modes are direct expressions of this tradeoff. The developer's question about whether to "simplify relentlessly or accept slow speed" maps precisely onto a design choice the field has not yet resolved: whether to optimize AI coding assistants for throughput and interactivity, or for depth and reliability. The experience described suggests that for developers whose primary value came from rapid iteration, the current trajectory of frontier model development may be moving in a direction that prioritizes the latter.
Read original article →