So again used m3 with claude code and it both still consumes more and gets worse results
The output is not bad, and the most generous interpretation i can give it that its claude optimized, and m3 is not like claude, so i think it's more throughput and "feature" focused, as if you check terminal bench even fable falls below gpt 5.5 despite being better, but most of all m3 is not a viber, so perhaps claude works better in it, but it doesn't set m3 up for success.
Now you might rightfully say duh but their docs recommend using claude despite sucking, but they also made their own harness which I have not tried cause its not on linux, the overwhelmingly number 1 developer platform and easiest to release to, which is implies that those gui things are second rate at best noob traps, like all the others. I could understand their motivation cause you make a model, then people use it under suboptimal conditions, then report below its capability, but of course you reported above it on release day. Honestly for serious work you are not going to have a different harness for different models, unless its all you use which is again unlikely for serious work, so my point you just have to live with whatever self imposed penalties, and suggesting subpar options doesn't help.
I give the claude harness a 7/10, feels magic til you see the results.