Developers Complain About Claude's Verbose Coding Style

Multiple developers have recently criticized Claude's output quality in coding assistance, citing extreme verbosity and obscure semantics. They report that in tasks like simplifying UI buttons, Claude tends to output excessive explanatory filler, with generated code even including old text from before modifications and failure logs. Additionally, the model tends to over-describe what the code "doesn't do" during documentation, leading to confusing comments. In long sessions, Opus 5's output is riddled with terms like "load-bearing," assuming readers know the entire codebase, and is accused of having a "pseudo-intellectual" tendency.

Confirmed

• Claude's output is verbose in UI adjustments, with code mixed with old text and test logs
• The model tends to over-document non-functional behaviors, causing confusing comments
• Opus 5 overuses jargon in long sessions, with poor readability
• Claude Code's output is semantically contradictory and tends to use dense vocabulary
• Generated code comments are usually 3 to 4 lines long

Why It Matters

• Readability of AI coding assistants directly impacts development efficiency
• Overly verbose and obscure output may undermine user trust

2026-08-15 ~ 2026-08-17 · 5 related posts

• [source] Opus 5 Long Sessions Produce Unreadable Output; Dev Fixes with Output Style Rules — ukanwat · 2026-08-15
• Users note Claude Code tends to write excessively long comments — 4310sy · 2026-08-15
• Dev critique: Claude obsessively documents what code doesn't do — chrisalbon · 2026-08-16
• [source] Users complain about Claude Code's 'semantic nonsense' in outputs — DarkSkyKnight · 2026-08-16
• [source] Developer rants about Claude's verbose coding style in UI tweaks — RupFox · 2026-08-17