Noticed a shift in the newer model and want to sanity-check it against other people’s experience. It’s gotten much more question-heavy. Some of that is fine, real clarifying questions when a task is genuinely ambiguous. But two things are getting to me:
- It seems to seek out ambiguity on tasks that aren’t ambiguous. Simple, clearly-scoped jobs come back with a round of questions I didn’t expect. 2. Worse: on long tasks I’ll set it going, come back in the morning expecting it done, and find it asked “do you want me to proceed?” and then just… waited. So nothing got done overnight. The thing I asked for was the instruction - I didn’t need a permission check. Older models would just make a sensible assumption and blast through, and honestly they were right most of the time. The current behaviour slows me down a lot - some of these question/option blocks take 10+ minutes to read and decide on. Couple of questions for the group: • Are you seeing the same thing, especially the “asked permission instead of doing it” dead-end? • Has anyone found a config/instruction that reliably kills it? (I’m trying “proceed on your best assumption, flag any guesses inline, never ask whether to proceed unless you genuinely can’t continue” - curious if that works for others.) Not trying to start a conspiracy thread, just want to know if it’s a widespread issue or something about how I’m prompting. submitted by /u/djkenod
Originally posted by u/djkenod on r/ClaudeCode
You must log in or # to comment.