Bug Description
⏺ 4 scanners running, all at 0% CPU.
✻ Crunched for 1m 21s
When it says crunched, what exactly does that mean? Because it just stops. It's stopped doing all its work. I don't even get what is going on. I've got to go and follow up again constantly. You guys have. completely broken the way Opus works it used to seamlessly carry on pretty easily and be intelligent and now it's a constant pain in the ass
but you're all releasing all these new gimmicks and features and functions and you're not even focusing on what's going on and the complaints that are coming in How about you just fix what you broke? This goes on and on and on. This has happened so many times times before where you start adding so many new gimmicks so quickly and you've ruined how Opus actually works to the average user everybody I know is struggling at the moment because of some changes that you've made and it just keeps breaking code rather than actually working I don't know if different users are on different servers or what you're doing but you're messing around with something that really affects our job
it's not finished, it's got a task list to do, does 1 job, stops constantly It's done, it's so lazy
Environment Info
- Platform: darwin
- Terminal: tmux
- Version: 2.1.7
- Feedback ID: edc83981-90f8-47f1-8084-6cf69a048512
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.1.7 (expected in multi-process scenarios)\n at ALR (/$bunfs/root/claude:3168:2157)\n at eFA (/$bunfs/root/claude:3168:1268)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-14T03:24:46.654Z"}]
Bug Description
⏺ 4 scanners running, all at 0% CPU.
✻ Crunched for 1m 21s
When it says crunched, what exactly does that mean? Because it just stops. It's stopped doing all its work. I don't even get what is going on. I've got to go and follow up again constantly. You guys have. completely broken the way Opus works it used to seamlessly carry on pretty easily and be intelligent and now it's a constant pain in the ass
but you're all releasing all these new gimmicks and features and functions and you're not even focusing on what's going on and the complaints that are coming in How about you just fix what you broke? This goes on and on and on. This has happened so many times times before where you start adding so many new gimmicks so quickly and you've ruined how Opus actually works to the average user everybody I know is struggling at the moment because of some changes that you've made and it just keeps breaking code rather than actually working I don't know if different users are on different servers or what you're doing but you're messing around with something that really affects our job
it's not finished, it's got a task list to do, does 1 job, stops constantly It's done, it's so lazy
Environment Info
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.1.7 (expected in multi-process scenarios)\n at ALR (/$bunfs/root/claude:3168:2157)\n at eFA (/$bunfs/root/claude:3168:1268)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-14T03:24:46.654Z"}]