Not every task needs the same model. Some jobs want raw reasoning power; others just need speed. The /model command lets you switch without leaving your session or losing your place.
The basics
Run /model on its own to see and pick from the choices, or name one directly:
/model opus
/model sonnet
/model haiku
The change takes effect right away and stays until you switch again. Your conversation carries over, so you can change brains partway through a task.
Which one when
Think of it as a trade between depth and speed.
- opus — the heaviest thinker. Use it for tricky architecture, gnarly bugs, and work where getting it right matters more than getting it fast.
- sonnet — a strong middle ground for everyday coding.
- haiku — the quickest. Good for simple, repetitive edits or quick questions where you don't need deep reasoning.
A practical rhythm
A common pattern is to plan on a strong model, then drop down for the grunt work. Start on opus to design the approach, switch to a lighter model for the many small edits that follow, then come back up if you hit something hard again.
Because the switch is instant and keeps your context, there's no cost to experimenting. If replies feel slow for a simple job, drop to haiku. If Claude keeps missing something subtle, bump up to opus. Matching the model to the moment is one of the easiest wins in Claude Code.
Comments
Be the first to comment.