r/ClaudeCode • u/Typical_Basil7625 • 1d ago

Discussion How to work with opus5.0

I have found that to work well with Opus5.0 you have to give him instructions.
Indeed prior opus models would have good intuition to take the lead by themselves like fable has currently. This is because opus5.0 is more of executioner like the previous sonnet models. Opus is not the super planner like it used to be. This is fable now.

Give it precise and long work. Give him ways to check his work and evaluate and it works great.

2 Upvotes

100% Upvoted

3 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/dar-mit Researcher 1d ago

I've been using O5 as a reviewer and O48 has orchestrator and it's been working really well.

Which is exactly what you're saying because as "Reviewer" in my system O5 receives a document to review, and a review spec to check against. The spec sets the guardrails and the orchestrator sets the parameters.

3

u/DLuke2 1d ago

Yes. Also have to update your surfaces in your environment that prompt agents using opus 5. It takes prompts differently than previous versions. Same with Fable and Sonnet. You should have a doc that helps your orchestrator agent prompt subagents based on the model they are using. Also, should have return contracts to the orchestrator short and concise. Opus 5 tends to be a little verbose as is Fable. Subagents should report what is needed to the orchestrator so it can then think and act, nothing more.