I have been using Claude Code more for longer coding sessions, and the cost side feels different once it is doing more than one small edit. A normal session can involve a lot of model work that is not all equally important: reading the repo structure searching through files summarizing existing code planning the change making the actual edit explaining the diff retrying after a failed approach writing tests or follow-up notes The final reasoning or risky code changes probably deserve the strongest model path. But some steps feel more like background work, especially repo scanning, summarizing, formatting, or checking whether a previous attempt worked. At low usage I would not bother separating anything. But once Claude Code becomes part of the daily workflow, sending every step through the same expensive path starts to feel hard to justify. How are people deciding which Claude Code tasks actually deserve the expensive model? submitted by /u/NebulaQyx
Originally posted by u/NebulaQyx on r/ClaudeCode