Detailed Analysis
A Reddit post in r/Anthropic captures a common frustration among Claude Code users: excessive verbosity that persists despite explicit instructions to stop. The original poster describes repeatedly editing both project-level and global CLAUDE.md configuration files—writing instructions in all caps, providing negative examples, and rephrasing requests multiple ways—only to have the model continue producing lengthy, unsolicited commentary. The user frames this as a token-wasting problem, since verbose responses consume context window and API costs unnecessarily, and asks whether there's a setting, command, or update they're missing to enforce terser output.
This complaint reflects a broader tension in how large language models like Claude interpret and prioritize system-level instructions versus their trained defaults toward explanatory, thorough responses. Claude models, like most instruction-tuned LLMs, are trained with reinforcement learning from human feedback (RLHF) that often rewards helpfulness signals such as showing reasoning, explaining choices, and offering context—behaviors that can manifest as "chattiness" even when a user explicitly requests brevity. The CLAUDE.md file mechanism in Claude Code is designed precisely to let users set persistent behavioral guardrails, but as this post illustrates, adherence to such instructions isn't always reliable, particularly for stylistic preferences like conciseness versus substantive content restrictions. This gap between instruction-following for content versus tone represents a known limitation across coding assistants, not unique to Claude.
The frustration also speaks to a practical pain point for developers using AI coding assistants in production workflows: token economy. When using Claude Code via API access rather than a flat-rate subscription, every unnecessary sentence of explanation translates into real cost, and verbose outputs can also clutter terminal-based workflows where developers want quick, actionable answers rather than narrative explanations. This is especially salient for power users running Claude Code in agentic loops or automated pipelines, where excess text can slow down iteration cycles or require additional parsing.
More broadly, this thread is emblematic of a recurring theme in AI assistant communities: the gap between what users configure and what models actually do, and the demand for more deterministic, fine-grained controls over model behavior rather than relying on natural-language instructions that models may weight inconsistently. Anthropic and competitors like OpenAI and Google have increasingly introduced explicit verbosity or "thinking token" controls, system-level flags, and structured output modes to address exactly this kind of complaint. The popularity of such threads suggests continued demand for Claude Code to expose more explicit, reliable settings (rather than prompt-based workarounds) for controlling response length and style, and highlights that instruction-following fidelity—especially for stylistic constraints—remains an active area where user expectations outpace current model behavior.
Read original article →