I’m getting better at managing Claude, but I still see it often going down the rabbit hole where each time it tries to ship a fix, it adds two more small issues to the tracker, or an esoteric process update, etc. I know this is a common AI thing, and I’m learning to deal with it. But it’s hard! For example, Claude will throw together a quick hook or utility script for a specific purpose, but soon I find it wants to maintain and update that script and has long forgotten that it will likely. never be used again. I especially see it in the MD files - like, if I let Claude update it’s own process files for workflow, rules, etc it does the job but it also puts a bunch of junk history, narrative, and updates other documents with unnecessary guard rails. I’ve started to edit the md files myself and they are getting cleaner, and I notice how much smoother the workflow is. But for the code, that’s not so easy. Does anyone have tips to manage this? What I’ve learned: #1 Work on distinct tasks, in new sessions and start new sessions often #2 Literally ask claude a few questions about every ‘suggestion’ or ‘problem’ it finds, like. “is the rule/process/script you’re trying to fix even enforced or critical? would it be easier to just remove this?” Any other tips? claude is amazing but also unruly :) submitted by /u/ExpensiveSun257
Originally posted by u/ExpensiveSun257 on r/ClaudeCode