I actually use sonnet 4.6 for my day to day coding too. It consumes much less token and good enough. Opus is just too token consuming for it to be useful to me.

▲

ricardonunez 4 hours ago | parent | next [-]

I am in the same position. Do you think they are going to remove it and deprecate it as some point?

▲

bazhand 8 hours ago | parent | prev [-]

Have you tried '/model opusplan' I've had strong results mixing opus for planning with sonnet implementing.

▲

a_c 8 hours ago | parent | next [-]

I haven't. Thanks for the heads up will give it a try! I use opus to comment on code design quite often though. It became a pattern that I made a skill for me to ask for second opinions https://news.ycombinator.com/item?id=48733092 Would love to hear your feedback if you don't mind!

▲

vtail 8 hours ago | parent | prev [-]

Fascinating! How did you learn about this?

▲

bazhand 7 hours ago | parent [-]

It was something that was used for token efficiency. Most of the settings and use cases are quite poorly communicated but asking Claude to review the latest release changelog (https://github.com/anthropics/claude-code/blob/main/CHANGELO...) is quite useful. Combined with @"claude-code-guide (agent)" to read it's own docs for settings/configs is super helpful.

The quite useful tool is to use /opusplan along with /codex:rescue (https://github.com/openai/codex-plugin-cc) means you get quite a strongly reviewed plan using native claude + codex without having to implement the mostly useless trust-me-bro plugins and other bs.

	▲	addozhang 4 hours ago \| parent [-]
		That's really a great way for the agent to understand itself.