I've been working with MCP tools development since Qwen 2.5, improving and understanding how to speak better with the models and reduce time to resolution at the minimum. I'm pretty happy with the evolution of local models since, and the craft made mcps I use allowed me to improve a lot the time to resolution using local models, being Qwen 3.8 27b my current daily driver for personal projects. Even though it's good, it's just too slow for developing to the company I work, so they signed up for Claude. I was pretty happy until the last few weeks. Now I can't seem to enable thinking view (that was perfect so i could see when it was drifting too much of the problem), Opus 5.5 couldn't even input the local env password yesterday because it was "a hard limit for it", and today Opus 5 was absolutely bad. A simple "debug this stuff" now is spending 60/70 tool calls, ignoring all my MCPs, and not spitting out why the decisions are being made. Almost look like they are turning Opus 5 dumb so they can gather usage for their "new" model. I really few like the can kill your business knowledge at any time with their decisions and can't wait to put my hands on a expensive rig and be done for good with these private companies. At least locally I can tune my harness and that will behave the same until I decide otherwise.   submitted by   /u/Muritavo [link]   [comments]