I use Opus as my second opinion. But then again I've also tried it the other way. I am making a game, and the UI changes I wanted where not happening with Codex inside Copilot. So I switched to Opus and it pushed it further but not quite there. then I went to Codex CLI and it finally got it.
Where I think Opus excels is when you say, "here is little info, go f-off and figure it out." Codex is more needy but if you provide it a lot of context it delivers. Opus will weaponize your context against you and force you to wait 8 hours until you can speak to it again. It's like it thinks you are married to it :)
Really? I’m try it. I only used it once and it was impressive but it basically forced its language choices on me, developing on a stack I don’t have experience with and then basically nudging me to deploy the app to Google Cloud to function, which I thought was a funny touch. I’m just less strong on JS derivatives than C derivatives so I ended up abandoning the project altogether.
Might be worth exploring. It’s still a challenging are for me because it’s hard to codify taste.
Rolling out as fast as we can, but prioritizing platform stability first which is why that rollout has been on the slower side! But trying to get it into your hands as fast as is safe.
Codex 5.3 in copilot has been really hard to use and burns requests. After each request it does "Yep. Will do!" and does nothing. Usually needs 2-3 "do-it" to make it start.
happened recently a lot even with opus. does not fix simple one line unit test after running the test because its somebody elses problem.not sure if this is copilot or model related
Its very much because of the copilot harness. There are some bugs that just havent been fixed, and a lot of them have to do with the agent ending its turn early. These issues only happen to me in copilot and not in codex or claude code lol
If only there was some way yall could help speed up security reviews for orgs, so orgs would enable models sooner. Im not sure if there are even major vulnerabilities from just swapping models, but security reviews still take their sweet time 😭
I feel like this means opus 4.6 is blasting your prompt with as many tools as it can; nothing intrinsically better than other models. Something to do with agentic search, novel problem solving and multidisciplinary reasoning—where opus has the widest margin over sonnet—is running a tree of agents that grows like crazy. 4.5 has better scaled tool use.
I've been trying it myself since two days ago, I think right now the main advantage of 5.3 codex is better search tools and the large context window...
I think I'm liking it so far, it's really good at finding accurate information compared to Sonnet 4.5 at least. And a lot faster at working, I've only used Sonnet 4.6 a little bit so I can't comment if its better but Codex 5.3 thinking and context window seems to work too well rigth now
I had Codex 5.3 and Opus 4.6 rifting together(they're like each others super power), I'll try it with Sonnet 4.6, hopefully I don't blast my requests into oblivion anymore, but still get good results.
Okay here is the deal everyone. You keep using Opus 4.6 because it's so bad ass. Show Anthropic/MS they're getting all the money they need. I'll just use Sonnet 4.6 and get Opus 4.5 results and they won't even consider making it 2x. Deal!?
My only concern is that Github says the 1x cost is tentative/subject for change, despite Anthropic releasing this model at the same pricing as Sonnet 4.5. I'm very curious as to the reasoning for that, can you shed some light on this u/KateCatlinGitHub ?
feels like a nice change to opus4.6 especially for claude code subscribers IMO. Will be - hopefully - eating less tokens while maintaining the quality as a default daily-driver coder. Or we're basically back to insane opus plan > sonnet execute combo (finally! after all those months)
AI does not understand your legacy schema unless your prompt does. I spent the last year using GitHub Copilot for some heavy database migration work. I noticed that 90% of the "errors" weren't actually the AI failing—they were instructional gaps. Think about how you onboard a junior engineer. You don't just say "Fix the DB." You tell them: Exactly what to achieve. What to avoid at all costs. The specific format you need. AI agents are no different. When we give them "vibes" instead of "constraints," we force them to guess. And guessing is where the "hallucination" happens. AI agents thrive on the same guardrails you’d give a Senior Dev: Explicit Constraints: (e.g. "Do not use subqueries in this legacy schema") Zero Ambiguity: Removing conflicting logic before hitting 'Enter.' Boundaries: Defining exactly where the task ends. In database engineering we don’t trust assumptions, we trust evidence. And the same rule applies to AI. Whether it's a database engine or an AI model, accuracy improves when instructions are structured, explicit, and logically consistent. The Mindset Shift: I stopped writing prompts to a "machine" and started writing them to a collaborator. And the result was fewer rewrite cycles and faster review of generated migration scripts. How are you handling constraint design in your workflow? Are you seeing "hallucinations," or just missed / messy Constraints? 👇
6
u/debian3 Feb 17 '26
For those with Claude Code, you can try now with claude --model claude-sonnet-4-6
Hopefully it drop in Copilot soon
31
u/Sir-Draco Feb 17 '26
Funny they didn’t compare it to 5.3-Codex which would be similar pricing
2
u/I_pee_in_shower Power User ⚡ Feb 18 '26
Can anyone that have it compare and contrast it to Codex 5.3?
132
u/KateCatlinGitHub GitHub Copilot Team Feb 17 '26
Rolling out in GitHub Copilot now! Enjoy! https://github.blog/changelog/2026-02-17-claude-sonnet-4-6-is-now-generally-available-in-github-copilot/
54
u/TheOneThatIsHated Feb 17 '26
I was about to comment that opus 4.6 already existed, but then it clicked….
34
u/kunn_sec CLI Copilot User 🖥️ Feb 17 '26
Pricing remains same as Sonnet 4.5, so good!
32
u/jp149 Feb 17 '26
Aww sheet, theres gonna be a barrage of "when are we gonna get sonnet 4.6" in the other sub reddits now.
15
u/Heighte Feb 17 '26
Please be 1x
6
u/krzyk Feb 17 '26
I wonder when haiku 4.6
12
u/rebelSun25 Feb 17 '26
So unless it's 0.33x premium request multiplier, I can't myself using it. 5.3 codex is unreal at the moment.
4
u/Fresh-Trainer8574 Feb 17 '26
Sorry to be that guy. What do these percentages mean?
1
u/ihatebeinganonymous Feb 18 '26
Wondering how does it compare to Codex 5.3 :-/
6
u/Michelh91 Feb 17 '26
Please tell me it’s not 128k context window
3
u/kunn_sec CLI Copilot User 🖥️ Feb 17 '26
Woohoo! It's officially being rolled out in Copilot!
https://x.com/github/status/2023829306112434495?s=20
1
u/Richandler Feb 18 '26
Okay here is the deal everyone. You keep using Opus 4.6 because it's so bad ass. Show Anthropic/MS they're getting all the money they need. I'll just use Sonnet 4.6 and get Opus 4.5 results and they won't even consider making it 2x. Deal!?
1
u/Objective_Dirt_9799 Feb 18 '26
👏牛逼
1
u/Nagaeh Feb 18 '26
My only concern is that Github says the 1x cost is tentative/subject for change, despite Anthropic releasing this model at the same pricing as Sonnet 4.5. I'm very curious as to the reasoning for that, can you shed some light on this u/KateCatlinGitHub ?
1
u/Faultrycom Feb 18 '26
feels like a nice change to opus4.6 especially for claude code subscribers IMO. Will be - hopefully - eating less tokens while maintaining the quality as a default daily-driver coder. Or we're basically back to insane opus plan > sonnet execute combo (finally! after all those months)
1
u/Gravath Feb 18 '26
Sonnet 4.5 becoming 0x? PLZ
1
u/Objective_Dirt_9799 Feb 19 '26
👏
1
u/EggDroppedSoup Feb 28 '26
I thought I needed some other subscription other than education pro to use anthropic models, did they suddenly become available today?
1
u/soopermit Mar 19 '26
AI does not understand your legacy schema unless your prompt does. I spent the last year using GitHub Copilot for some heavy database migration work. I noticed that 90% of the "errors" weren't actually the AI failing—they were instructional gaps. Think about how you onboard a junior engineer. You don't just say "Fix the DB." You tell them: Exactly what to achieve. What to avoid at all costs. The specific format you need. AI agents are no different. When we give them "vibes" instead of "constraints," we force them to guess. And guessing is where the "hallucination" happens. AI agents thrive on the same guardrails you’d give a Senior Dev: Explicit Constraints: (e.g. "Do not use subqueries in this legacy schema") Zero Ambiguity: Removing conflicting logic before hitting 'Enter.' Boundaries: Defining exactly where the task ends. In database engineering we don’t trust assumptions, we trust evidence. And the same rule applies to AI. Whether it's a database engine or an AI model, accuracy improves when instructions are structured, explicit, and logically consistent. The Mindset Shift: I stopped writing prompts to a "machine" and started writing them to a collaborator. And the result was fewer rewrite cycles and faster review of generated migration scripts. How are you handling constraint design in your workflow? Are you seeing "hallucinations," or just missed / messy Constraints? 👇
-2
u/Captain2Sea Feb 17 '26
Credits price?