Earlier quoted context omitted.
There is extra cost for >272K: > For models with a 1.05M context window (GPT-5.4 and GPT-5.4 pro), prompts with >272K input tokens are priced at 2x input and 1.5x output for the full session for standard, batch, and flex. Taken from https://developers.openai.com/api/docs/models/gpt-5.4
Anthropic literally don't allow you to use the 1M context anymore on Sonnet and Opus 4.6 without it being billed as extra usage immediately. I had 4.5 1M before that so they definitely made it worse. OpenAI at least gives you the option of using your plan for it. Even if it uses it up more quickly.
GPT-5.4
571–580 of 868 posts
Re: GPT-5.4
#572Re: GPT-5.4
#573So let me get this straight, OpenAi previously had an issue with LOTS of different models snd versions being available. Then they solved this by introducing GPT-5 which was more like a router that put all these models under the hood so you only had to prompt to GPT-5, and it would route to the best suitable model. This worked great I assume and made the ui for the user comprehensible. But now, they are starting to in…
Re: GPT-5.4
#574Earlier quoted context omitted.
https://static0.anpoimages.com/wordpress/wp-content/uploads/...
Reminds of Unity features
Similar story with the whole networking stack. I haven’t used Unity in years now after it being my main work environment for years, but the sour taste it left in my mouth by moving everything that worked in the engine into plugins that barely worked will forever remain there.
Im sure its partly skill issue
Re: GPT-5.4
#575The marquee feature is obviously the 1M context window, compared to the ~200k other models support with maybe an extra cost for generations beyond >200k tokens. Per the pricing page, there is no additional cost for tokens beyond 200k: https://openai.com/api/pricing/ Also per pricing, GPT-5.4 ($2.50/M input, $15/M output) is much cheaper than Opus 4.6 ($5/M input, $25/M output) and Opus has a penalty for its beta >200…
Yeah, long context vs compaction is always an interesting tradeoff. More information isn't always better for LLMs, as each token adds distraction, cost, and latency. There's no single optimum for all use cases. For Codex, we're making 1M context experimentally available, but we're not making it the default experience for everyone, as from our testing we think that shorter context plus compaction works best for most p…
Re: GPT-5.4
#576Earlier quoted context omitted.
This sounds made up. Much like “prompt engineering” Let’s hear an actual example
OK, so a while back I set up a workflow to do language tagging. There were 6-8 stages in the pipeline where it would go out to an LLM and come back. Each one has its own prompt that has to be tweaked to get it to give decent results. I was only doing it for a smallish batch (150 short conversations) and only for private use; but I definitely wouldn't switch models without doing another informal round of quality asses…
Re: GPT-5.4
#577Earlier quoted context omitted.
That's been my experience as well switching from Opus to Codex. Reasoning takes longer but answers are precise. Claude is sloppy in comparison.
Weird, I have had the opposite experience. Codex is good at doing precisely what I tell it to do, Opus suggests well thought out plans even if it needs to push back to do it.
Re: GPT-5.4
#578Earlier quoted context omitted.
That's been my experience as well switching from Opus to Codex. Reasoning takes longer but answers are precise. Claude is sloppy in comparison.
codex has been really good so far and the fast mode is cherry on top! and the very generous limits is another cherry on top
Re: GPT-5.4
#579Re: GPT-5.4
#580Earlier quoted context omitted.
My own experience is that I get far far more usage (and better quality code, too) from codex. I downgrade my Claude Max to Claude Pro (the $20 plan) and now using codex with Pro plan exclusively for everything.
Codex announced at 5.3 launch that until April all usage limits are upped so take that into account