Birbla

Anyone have solution to Opus verbosity in Claude Code?

Anyone have solution to Opus verbosity in Claude Code?

2 pointsby firemelt0 comments

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • ignore opus 5. 4.6 is legit, opus 5 is a random brat
    by penpendian
  • i currently use 4.8 on xhigh and it's tolerable
    by uncomplexity
  • "reply in fewest words. to the point" usually helps
    by penkovsky
  • You can add instructions in the CLAUDE.md/AGENTS.md file to modify output behavior like:

        # 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.
    While writing a document I got good mileage out of doing something like this for every paragraph:

        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'm not sure how many extra tokens it would consume to do this for every output. But it may be better than just asking for "TLDR pls"

    (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.)

    by Leftium
  • This is what you want: https://github.com/juliusbrussee/caveman
    by ApolloRising
  • I like:

    "Explain in 10 sentences or fewer."

    "Give me the gist of what you just said."

    "ELI5"

    by DantesKite
  • I've resorted to adding instructions like, "do not insert any comments unless they will be exceptionally useful in clarifying blocks of code for future developers."

    Adding it to AGENTS.md seems to do nothing.

    by seattle_spring
  • The 3 lines below help a bit. It still gets lost after the context fills up, but it mostly solves the verbosity issue,

    - 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

    by gojkoa

Explore Birbla archives

Anyone have solution to Opus verbosity in Claude Code? · Birbla