Everytime I set to claude Opus 4.6 it seems to run on GPT 5.1…. If I set to Opus 4.5 it seems to work, or any other model, but when I set to 4.6 it simply doesen’t seem to work… I have OTHER pickaxes that do seem to be working…
Hi Chris, I can look into this for you! Can you either reply here or email at info@pickaxeproject.com with the name of the Pickaxe and I can troubleshoot?
Yes, it’s the KAVIX v3.2
Thank you!
Chris
Appreciate the reports on Opus 4.6 routing. Weve logged this internally as PRD-470a1 so engineering can fix the model-selection bug that fell back to GPT-4.1. Ill update this thread when the fix shipsa1in the meantime you can temporarily switch affected Pickaxes back to Claude 3.5 Sonnet or GPT-4.1 if you need reliable routing today.
Update: the fix for PRD-470 just shipped. Root cause was that Claude Opus 4.6 supports a 200K token context window (we initially assumed 1M), so large prompts were silently falling back to GPT-5.1. We’ve corrected that. If you see it fall back again after a fresh run, let me know with the session ID and we’ll inspect immediately. We moved all affected Pickaxes back to Sonnet if they were over the 200K limit.
1 Like
that didn’t resolve the issue BTW.. still seems to be broken…
Hi @chrisbehnke! I just tried it out, and I seem to be able to use Claude 4.6 correctly now - mind DMing or emailing a session ID I can take a look at?
BTW this is STILL 100% broken… When ever I try and use Claude 4.6 I have multiple Pickaxes that revert to gpt 5.1
This is very frustrating
Here is another session to look at: c4c50759-4f03-49e8-baa0-5deb700b1ad7
!
Appreciate the new session ID — I’ve reopened this with Product as PRD-638 so engineering can trace why Opus 4.6 is still falling back to GPT-5.1. They’re digging through the routing logs right now and I’ll report back here once we have a fix or a manual workaround. If you catch another session ID or specific Pickaxe slug where this reproduces, send it my way so we can compare traces. Thanks for hanging in there.
Hi @chrisbehnke, thanks for following up! I spent some time looking into this today, and I see what you’re talking about - I bumped PRD-638 up to urgent. I appreciate your patience and I will reply here when I have an answer for you!
Hi @chrisbehnke, I’ve talked to our engineers and this should be fixed now - please let me know if you’re still having issues!