When the model changes and nobody tells you: the transparency crisis in frontier AI

Frontier AI products have a trust problem, and it is not about capability. It is about disclosure. Claude Code GitHub issue #42796 crystallized something that power users across every major vendor have felt for months: the model you evaluated is not always the model you get next week, and nobody tells you what changed.

What issue #42796 actually documented

The issue is not a typical complaint thread. The author presented a longitudinal analysis across thousands of Claude Code sessions, examining thinking blocks, tool call patterns, and edit behavior over time. The core claim: after February 2026, Claude Code's performance on complex engineering work degraded in specific, observable ways.

The reported symptoms were operational, not subjective. The model appeared to ignore instructions more frequently, take premature action before fully researching the codebase, produce shallower edits, and lose coherence during long autonomous sessions. What made the issue notable was that it tracked measurable workflow characteristics — tool usage frequency, research-before-edit ratios, thinking block depth — rather than relying on vibes.

The thread gained traction precisely because it tried to connect perceived quality decline to behavioral changes in the system. The central frustration was not just "it feels worse" but "something measurably shifted, and Anthropic's release notes do not explain what."

Why this is not just one GitHub issue

Anthropic publishes release notes for Claude Code. So does OpenAI for its models and tools. But vendor changelogs typically describe UI features, new capabilities, and safety improvements. They rarely disclose the behavioral changes that matter most in production: shifts in reasoning depth, tool-use patterns, default effort allocation, or instruction adherence under load.

This creates a specific information asymmetry. Teams subscribe to a named product. The behavior changes underneath the same label. And users cannot determine whether they are seeing prompt sensitivity, a staged rollout difference, routing changes, safety retuning, context-budget adjustments, or genuine model regression. Every explanation is plausible, and none can be confirmed.

Why users assume the worst when vendors explain the least

The economic incentive hypothesis is straightforward. Frontier inference is expensive. Deeper reasoning, longer tool loops, and more careful code exploration consume more compute. When a product like Claude Code scales to heavy adoption under flat subscription pricing, there is structural pressure to optimize throughput and reduce average compute burn per session.

I want to be precise here: this is a plausible incentive, not a proven motive. Cost optimization, safety tuning, UX simplification, latency reduction, and rollout instability are all credible explanations for behavioral shifts. The problem is that without meaningful disclosure, users cannot distinguish any of these from deliberate capability reduction. Opacity turns an engineering question into a trust crisis.