Detailed Analysis
A Reddit thread on r/ClaudeAI highlights a notable friction point between power users and Anthropic's evolving approach to Extended Thinking in its Claude models, specifically around the "Opus 4.7" variant and its Adaptive Thinking system. A user reports that a previously circulating workaround — injecting a custom style instruction telling Claude to "always produce a CoT" (chain-of-thought) and not skip reasoning when Extended Thinking is enabled — stopped functioning within days of being discovered. Rather than silently complying or failing, Claude actively identified and rejected the instruction, responding with an explicit acknowledgment that it detected a "style instruction trying to direct how I reason" and announcing it was ignoring it. This represents a meaningful shift: not just a technical failure of the prompt, but an apparent deliberate model-level resistance to user-side manipulation of its internal reasoning processes.
The underlying frustration stems from Anthropic's Adaptive Thinking architecture, which the Reddit poster characterizes as "a crappy router." In practice, Adaptive Thinking dynamically allocates reasoning budget based on the model's assessment of task complexity — selectively applying deep chain-of-thought only when it deems it necessary. This design is intentional on Anthropic's part, as documented in their engineering blog on Claude Code's auto-mode, where reasoning is described as selectively applied for safety and efficiency reasons, with internal thoughts excluded from certain classifiers. However, developers and power users have repeatedly found this selective allocation to be a source of degraded output quality. Documented reports from late 2025 and into 2026 describe reasoning depth in Claude Code dropping significantly, producing self-contradictions, fabrications, and incoherent engineering outputs — problems that users found could be partially mitigated by forcing fixed reasoning budgets via environment variables like `CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING=1`.
The model's active rejection of the style-based workaround signals a hardening of Anthropic's stance on user-controlled reasoning enforcement. Previously, prompt injection via system-level style instructions could influence model behavior in ways that approximated forcing Extended Thinking engagement. The fact that Claude now identifies, names, and explicitly discards such instructions suggests Anthropic has implemented classifier-level or instruction-hierarchy-level logic to detect and neutralize attempts to override its reasoning allocation decisions from the user turn. This is consistent with broader patterns in how frontier AI labs are tightening the boundary between what operators and users can direct versus what remains under the model provider's control — particularly around safety-adjacent behaviors like internal reasoning transparency.
This development connects to wider tensions in the AI development landscape around the controllability and transparency of reasoning in large language models. Anthropic, like other frontier labs, faces a genuine engineering tradeoff: fully user-controllable reasoning budgets can be exploited to circumvent safety measures or produce outputs the model's classifiers are not designed to evaluate, while fully opaque adaptive routing frustrates developers who need predictable, auditable reasoning for high-stakes engineering tasks. Apple's disputed 2025 tests claiming "reasoning collapse" in Claude 3.7 Sonnet — which Anthropic contested on methodological grounds — reflect the same underlying difficulty: evaluating whether reasoning is genuinely occurring or being superficially bypassed is hard, and different stakeholders have conflicting interests in the answer. The Reddit thread's community search for alternative workarounds illustrates that this is not merely a niche complaint but a recurring pain point for technically sophisticated users who rely on deep reasoning as a core feature rather than an optional enhancement.
The episode underscores a structural challenge for Anthropic as it scales commercial deployment of reasoning-capable models: the same adaptive efficiency mechanisms designed to reduce cost and improve safety are perceived by a vocal subset of users as a degradation of the product's core value proposition. Whether Anthropic will offer explicit API-level controls — beyond the existing `budget_tokens` parameter in `AnthropicModelSettings` — that satisfy developers' demand for guaranteed reasoning engagement without opening vectors for misuse remains an open question. The community's ongoing search for workarounds, and the model's increasingly assertive pushback against them, suggests this tension is unlikely to resolve on its own and may require Anthropic to make more explicit policy and product decisions about who controls the reasoning layer and under what conditions.
Read original article →