---
title: "Discussion on \"Claude Opus 5 Honest Review: \nIs It Worth Switching From Opus 4.8?\" | Hashnode"
description: "Discussion on \"Claude Opus 5 Honest Review: \nIs It Worth Switching From Opus 4.8?\". What it's good at, where it's confidently wrong, and the settings I'd change before you switch from Opus 4.8.can u"
url: "https://hashnode.com/posts/claude-opus-5-honest-review-is-it-worth-switching-from-opus-4-8/6a69ee475164f278edca1a04"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Claude Opus 5 Honest Review: Is It Worth Switching From Opus 4.8?](https://honestaireview.hashnode.dev/claude-opus-5-honest-review-is-it-worth-switching-from-opus-4-8?utm_source=hashnode&utm_medium=feed)

What it's good at, where it's confidently wrong, and the settings I'd change before you switch from Opus 4.8.can u

Jul 29 · 9 min read · honestaireview.hashnode.dev  
Read the article

-   [#claude](https://hashnode.com/tag/claude)
-   [#claude-code](https://hashnode.com/tag/claude-code)
-   [#claudeai](https://hashnode.com/tag/claudeai)
-   [#claudeopus5](https://hashnode.com/tag/claudeopus5)
-   [#claude-ai](https://hashnode.com/tag/claude-ai)

## Written by

[Aditi Gupta](https://hashnode.com/@adi084)

@adi084 · Bengaluru, India

  
[View profile](https://hashnode.com/@adi084)

Founder , Builder & Techie

I explore AI tools, test what actually works, and share honest reviews, practical settings, and lessons from my experiments. https://www.youtube.com/@GoVenture-Live

## Responses 1

Markdown supported · ⌘↵ to post

[Skillselion](https://hashnode.com/@skillselion)

[Aug 19](https://hashnode.com/posts/claude-opus-5-honest-review-is-it-worth-switching-from-opus-4-8/6a69ee475164f278edca1a04/comment/6a856b1d52d3e2956ccde478)

Deleting the "double-check your answer" lines is the tip I would act on first. Those prompts were written for models that under-verified; on a model that already self-verifies they read as an instruction to keep going, which is where a chunk of the over-engineering you describe comes from. Same experience on subagent sprawl: capping how many it may spawn changed our bill more than any effort-level setting did. One place I would soften the verdict: 55.2% vs 61.1% recall makes it sound unfit for code review, but a precision-heavy reviewer works well as the second voice in an ensemble where a cheaper high-recall pass goes first. As the only safety net, agreed, no.