[Bug] Claude 4.7 Opus degraded reasoning in issue triage tasks
Resolved 💬 1 comment Opened May 13, 2026 by moonbox3 Closed Jun 12, 2026
Bug Description
I feel like opus 4.7 these days is really struggling. What normal would kick off as its own investigation, when I asked it to triage a GitHub issue, turned into a first response of the model parroting back the issue directly to me. I then had to hand hold it, all the way until the end result which in previous weeks, would have happened without me having to direct the model so much. This doesn't feel like normal behavior (I use CC + Opus 4.7 every single day).
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.140
- Feedback ID: 628487c2-e47b-403e-9ead-a007655c2fad
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/e/.local/share/claude/versions/2.1.140 (expected in multi-process scenarios)\n at g16 (/$bunfs/root/src/entrypoints/cli.js:2672:2257)\n at RLH (/$bunfs/root/src/entrypoints/cli.js:2672:1337)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-13T02:11:18.148Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:51:6192)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-13T02:28:11.047Z"}]This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗