[Bug] Model generates excessive comment verbosity after planning phases
Open 💬 0 comments Opened Jun 17, 2026 by smbpunt
Bug Description
Following large planning phases, the model carries the planning rationale straight into the code as comments. It explains every design decision over multiple lines — the why we chose this, the trade-offs, the rejected alternatives — instead of staying factual and concise. The result is sometimes more comment than code.
Expected behavior
comments should be brief and factual, explaining only what isn't obvious from the code itself. The detailed reasoning behind planning decisions belongs in the conversation, the commit message, or the MR description — not inline in the source. Match the comment density of the surrounding code rather than narrating the whole decision tree.
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.1.178
- Feedback ID: e5ebb606-16a5-4700-be8d-d09be039f0b9
Errors
[]