[Bug] Opus 4.6 model performance degradation and effort configuration not persisting correctly

Resolved 💬 5 comments Opened Mar 24, 2026 by Islomov49 Closed Apr 25, 2026

Bug Description
Really sorry to say that, but it seems you guys starting optimize costs and cutting edges. Opus 4.6 become to much stupped. Why you guys create effort config if effort it self always needed max. I put max it says max set, but status bar shows its medium. and Opus 4.6 it self become dumb. It feels like sonnet 3.5 or something like that. You guys gonna crash your business. First 2-3 weeks opus were working perfect. but now it works to baaaadd. Hell no its not related to context size. it was becoming dumb, when it was 200K context. maybe you have as previus problems with routing, machines or something, I dont know. but really sad that I'm leaving claude code :(

Environment Info

  • Platform: darwin
  • Terminal: pycharm
  • Version: 2.1.81
  • Feedback ID: 63263d8a-5112-42ca-9a7b-bc7604c77514

Errors

[]

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗