A lot of people are posting about how Opus 5 likes to easily give up on its task, making some benign excuse. The fix is to use /goal. I’d highly recommend first to ask it to write a plan for your request. Then say: /goal implement the plan, for anything you can’t make a call on make a best guess and implement that and raise it as a note when done so that I can review it. If you get to 90% context run a compact and then resume. A note that if you are planning a large feature you might even want to use /goal for the plan too so it doesn’t give up halfway through planning. If you read the official docs, the way /goal works is it spins up a cheap evaluation prompt to a lower model which reviews the context. It will keep working on the problem until the goal is achieved. I had it work nicely just before, Opus gave some bs about its context getting large and ended its turn. The /goal watcher saw that and resumed work. submitted by /u/gibbocool
Originally posted by u/gibbocool on r/ClaudeCode
