7 ms·
So true. The breaking point for me was when it was constantly saying to wrap up because we'd done enough work for the day, but we had barely even done anything.
by superdisk 1mo ago
So true. The breaking point for me was when it was constantly saying to wrap up because we'd done enough work for the day, but we had barely even done anything. Or constantly estimating that the next steps would take X number of weeks, and then knock it out in a single prompt. I demanded in no uncertain terms to stop giving pointless bogus estimates or telling me to stop working, and it just wouldn't. I also had a project I wanted to let it cook on overnight (a codebase port from Java to C++) and laid out a set of hard and fast rules that it could absolutely not break at any cost. Then I woke up the next day and it had broken all the rules and was just taking shortcuts left and right, and then lying to my face about it, even when I could point to concrete examples.
I cancelled the sub instantly and went to Codex and it's never let me down.
- jorl17 1mo agoThis!! I like to work weird hours of the night and Opus consistently likes to "wrap up" and say "it's been a long night" or "it's late" and "we've made great progress" It's infuriating, just do the work!
- nonethewiser 1mo agoThat is very strange. I havent seen that. It sounds like something leaking from its system prompt or something that its not handling well. Anthropic trying to prevent it from running longer or something.
- ethin 1mo agoI definitely have. It's like something in the system prompt has "keep the well-being of the human in mind" and of course the date and time, but something makes the model take that way way too literally.
- flutas 1mo agoPersonally I think it's due to context length. Whenever context gets towards the max length is when I've noticed it.
- ethin 1mo agoIt's done that to me even at the beginning of conversations. I usually end up telling it what time of day it is, but if I even do that at all it starts nannying me.