Opus 5.5 and Sol 6 both just dropped. Here's a really simple thing to do after you switch. Check how the new model gets around your codebase. Each model finds its way around code differently. Some search first. Some read whole files. Some lean on your instructions file more than others. A repo that worked great with your last model can be wasting tokens on the next one. And that waste adds up. Every extra tool call fills up the agent's context and burns tokens you pay for. Say one common path takes 12 calls when it should take 3. If your team hits it 200 times a day, that's millions of tokens a day spent on searching. You don't have to guess where it's happening. Most coding agents save your past sessions right on your computer. Here's a prompt that's helped me keep my codebase efficient. It works in any coding agent. Copy and paste it inside your repo: --- Find where our past chat sessions for this repo are saved and read through them. If you can't find them, tell me where to look. 1. Find the files and folders agents visit most often. 2. For each one, count how many tool calls it usually took to get there, and roughly how many tokens that used. 3. Flag the paths where the agent searched, opened the wrong files, or backtracked before finding the right spot. 4. Rank the 5 most wasteful paths by total tokens burned. 5. Suggest the smallest edits to our agent instructions file (CLAUDE.md, AGENTS.md, or whatever this repo uses) that would send an agent straight there. Pointers, not paragraphs. Don't change any files yet. Show me the report first. Make the edits, and run it again. -- Thank me later 😉