The context is the following: I have my own skill collection, which is able to go through an elaborate review process for a given diff (usually the plan and the implementation was done before and is still in the same context window) without me having to prompt/intercept. Sometimes the review process takes a bit more effort because there are a lot of findings to be processed by the main agent. If that happens, the main agent tends to skip additional reviews or re-run of reviews that I’ve instructed it to do via skills, even with stronger phrasings like “never skip a step/phase”. The reasons and rationalizations it gives are something like “the session was long”, “a prior phase was thorough enough”, or it tries to “save context”. But it’s just at ~76% context left. So yeah, before 1M context window, it would’ve definitely surpassed the 200k context window. In general, I tend to stay below 300k context window, but Claude still “panics” and tries to get done with the work as fast as possible. I just wonder if it’s possible to give it instructions that it’s okay to just do the work, to take its time, and not worry about prior exhaustiveness. If it’s not possible because that’s just how Opus 4.6 works right now and we might have to wait for an update, I’m okay with that. But maybe someone else found a “magic prompt” to put in CLAUDE.md or wherever? Curious to know about your observations. submitted by /u/Caibot
Originally posted by u/Caibot on r/ClaudeCode