Detailed Analysis
A Reddit post in r/Anthropic surfaces a recurring frustration among developers using Claude for extended, agentic coding sessions: the model's tendency to invent its own internal shorthand, labels, or terminology for files, processes, and code structures rather than consistently referencing them by their actual filenames or established naming conventions. The original poster, working with what they describe as "Opus 5" (and noting the same behavior in "Opus 4.8"), explains that even when explicitly instructed via a CLAUDE.md configuration file to use exact file names and structure-matching labels, the model reverts to inventing its own descriptive terms mid-task. This creates a practical problem: when an agent runs autonomously for an extended period—the poster cites an hour-long run—and generates several novel, self-invented terms to describe components of its own work, the developer is left trying to reverse-engineer what the model actually means, effectively requiring them to comb through the entire chain-of-thought or task log to decode the agent's internal vocabulary.
This complaint touches on a well-documented tension in large language model behavior: the gap between instruction-following at the surface level (system prompts, project-level configuration files) and the model's deeper, harder-to-override generative tendencies. CLAUDE.md files are Anthropic's recommended mechanism for giving Claude persistent, project-specific context and behavioral rules when operating in tools like Claude Code. The poster's experience suggests that even well-specified instructions in these files can be insufficient to fully constrain the model's tendency toward abstraction and self-generated labeling—behavior the poster characterizes as "hard trained," implying it may be a byproduct of how the model was fine-tuned to summarize, plan, or reason about complex tasks internally, rather than a simple oversight correctable through prompting alone.
The stakes here are significant for a specific and growing category of Claude users: developers running long, autonomous or semi-autonomous agentic coding sessions where the model executes multi-step tasks with minimal human supervision. As agentic workflows become a larger part of how Claude is used—particularly with tools like Claude Code and extended "agent runs" that touch large codebases—the clarity and traceability of the model's internal reasoning and labeling becomes a practical usability issue, not just a cosmetic one. If a model invents ad hoc terminology to describe its own intermediate work products, it directly undermines a developer's ability to audit, debug, or resume work efficiently, especially at scale. This is distinct from hallucination in the traditional sense (false facts) but represents a related failure mode: the model generating internally consistent but externally opaque abstractions that a human collaborator did not request and cannot easily map back to ground truth.
More broadly, this feedback reflects an emerging theme in the maturation of agentic AI tools: as models are trusted with longer, less-supervised task horizons, the demand for transparency, consistency, and predictability in their intermediate outputs grows sharper. Early complaints about LLMs focused heavily on factual accuracy and output quality; as usage shifts toward autonomous multi-step execution, new friction points emerge around process legibility—how well a human can follow, verify, and intervene in what the model is doing while it's doing it. This kind of grassroots, practitioner-level feedback, surfaced on community forums like Reddit rather than in formal benchmarks, is often an early signal of usability gaps that labs like Anthropic may need to address through both training adjustments (to reduce the tendency toward invented internal shorthand) and product features (such as more rigorous enforcement of naming conventions specified in configuration files, or tools to surface and standardize an agent's internal vocabulary in real time).
Read original article →