Ask HN: Anyone have solution to Opus verbosity in Claude Code? I find opus really talk much but speak nothing and usually I reply those verbosity with tldr pls and the text become readable. but I wonder if that would hiding some important info anyone have tips or better solution for this? |
- When responding to the user, respond in ASD-STE100 English. You can extend the dictionary if you need, but respect ASD-STE100 rules as much as you can.
- When writing comments, technical documentation and internal documents (roadmaps, plans, design references) use ASD-STE100 English. You can extend the dictionary if you need, but respect ASD-STE100 rules as much as you can.
- When writing plans: no timeline estimates, no complex code. unless specifically requested, no deployment sequence. use pseudo-code only for non-trivial operations where clarifying complexity is crucial
Adding it to AGENTS.md seems to do nothing.
I've resorted to having a final pass where comments are evaluated separately. This is much more successful than trying to get it to write good comments while writing the code.
"Explain in 10 sentences or fewer."
"Give me the gist of what you just said."
"ELI5"
# Response Style
Keep routine answers concise. Lead with the result, include material caveats and the next action, and omit introductions, repetition, generic reassurance, and optional background. Expand only when the task requires explanation.
Let's analyze this paragraph:
- List the main points.
- Can any points be removed? (Do any points need to be added?)
- Reword each point. Be as succinct and clear as possible.
(I've actually never used Claude Code. I've never had problems with verbosity in harnesses like OpenCode or T3-code. And recently I've been using Codex, not Claude models.)