‹ BackHN Continuity

Thread

Getting the most out of Opus 5.5 in Claude and Claude Code

232 points · 156 comments · saikatsg

  1. rdli · · focus · HN ↗
    It’s a really good model. Over the past few days, I give Opus some general directives to basically speed up our CI, and telling it I care both about billing minutes and wall clock time. I told it to create a plan after analyzing everything in our CI, run the plan by a Fable subagent, and then focus on low-risk, high-reward changes.

    9 hours later, I had 12 PRs ready to be merged, and the net result is CI time has dropped from ~10 minutes to ~4 minutes, and billing minutes have dropped around 60%. Less than an hour of my attention.

    1. Waterluvian · · focus · HN ↗
      Every time weird stuff happened this week it was because the model choice in VSCode got set back to “auto” and some other model was trying its best. 5.5 is what I just set it to. Even Fable feels worse for my use cases.
      1. AnotherGoodName · · focus · HN ↗
        Even Anthropic rates Fable lower than 5.5 on pretty much all benchmarks.

        "Why does Fable even exist" is a very very reasonable question right now.

        1. cromka · · focus · HN ↗
          I think of Fable as more knowledgeable, smart, erudite. Opus is a skilled technician.

          Benchmarks do not measure the first aspect.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.