Live data from Hacker News

GPT-5.3-Codex

openai.com

161–170 of 634 posts

Re: GPT-5.3-Codex

#161
post #150

I think Anthropic rushed out the release before 10am this morning to avoid having to put in comparisons to GPT-5.3-codex! The new Opus 4.6 scores 65.4 on Terminal-Bench 2.0, up from 64.7 from GPT-5.2-codex. GPT-5.3-codex scores 77.3.

Did you look at the ARC AGI 2? Codex might be overfit for terminal bench

ARC AGI 2 has a training set that model providers can choose to train on, so really wouldn't recommend using it as a general measure of coding ability.

Re: GPT-5.3-Codex

#162

Earlier quoted context omitted.

Personally, I have Claude do the coding. Then 5.2-high do the reviewing.

Then I pass the review back to Claude Opus to implement it.

Just curious is this a manual process or you guys have automated these steps?

Re: GPT-5.3-Codex

#163

May AI not write the code for me. May I at least understand what it has "written". AI help is good but don't replace real programmers completely. I'm enough copy pasting code i don't understand. What if one day AI will fall down and there will be no real programmers to write the software. AI for help is good but I don't want AI to write whole files into my project. Then something may broke and I won't know what's bro…

> What if one day AI will fall down and there will be no real programmers to write the software.

What if you want to write something very complex now that most people don't understand? You keep offering more money until someone takes the time to learn it and accomplish it, or you give up.

I mean, there are still people that hammer out horseshoes over a hot fire. You can get anything you're willing to pay money for.

Re: GPT-5.3-Codex

#164

Something that caught my eye from the announcement: > GPT‑5.3‑Codex is our first model that was instrumental in creating itself. The Codex team used early versions to debug its own training I'm happy to see the Codex team moving to this kind of dogfooding. I think this was critical for Claude Code to achieve its momentum.

More importantly, this is the early steps of a model self improving itself. Do we still think we'll have soft take off?

I think the limiting factor is capital, not code. And I doubt GPTX is anymore competent at raising funds than the other, fleshy, snake oilers...

Re: GPT-5.3-Codex

#165

Earlier quoted context omitted.

'feel' is no more accurate not saying there's a better way but both suck

At the end of the day “feel” is what people rely on to pick which tool they use. I’d feel unscientific and broken? Sure maybe why not. But at the end of the day I’m going to choose what I see with my own two eyes over a number in a table. Benchmarks are a sometimes useful to. But we are in prime Goodharts Law Territory.

yeah, to be honest it probably doesn't matter too much. I think the major models are very close in capabilities

Re: GPT-5.3-Codex

#166
For those who cared:

GPT-5.3-Codex dominates terminal coding with a roughly 12% lead (Terminal-Bench 2.0), while Opus 4.6 retains the edge in general computer use by 8% (OSWorld).

Anyone knows the difference between OSWorld vs OSWorld Verified?

Re: GPT-5.3-Codex

#167

Earlier quoted context omitted.

I do not trust the AI benchmarks much, they often do not line up with my experience. That said ... I do think Codex 5.2 was the best coding model for more complex tasks, albeit quite slow. So very much looking forward to trying out 5.3.

Just some anecdata++ here but I found 5.2 to be really good at code review. So I can have something crunched by cheaper models, reviewed async by codex and then re-prompt with the findings from the review. It finds good things, doesn't flag nits (if prompted not to) and the overall flow is worth it for me. Speed loss doesn't impact this flow that much.

I don’t use OpenAI too much, but I follow a similar work flow. Use Opus for design/architecture work. Move it to Sonnet for implementation and build out. Then finally over to Gemini for review, QC and standards check. There is an absolute gain in using different models. Each has their own style and way of solving the problem just like a human team. It’s kind of awesome and crazy and a bit scary all at once.

Re: GPT-5.3-Codex

#168
post #54

Earlier quoted context omitted.

Yeah, these benchmarks are bogus. Every new model overfits to the latest overhyped benchmark. Someone should take this to a logical extreme and train a tiny model that scores better on a specific benchmark.

> Yeah, these benchmarks are bogus. It's not just over-fitting to leading benchmarks, there's also too many degrees of freedom in how a model is tested (harness, etc). Until there's standardized documentation enabling independent replication, it's all just benchmarketing .

For the current state of AI, the harness is unfortunately part of the secret sauce.

Re: GPT-5.3-Codex

#169

Something that caught my eye from the announcement: > GPT‑5.3‑Codex is our first model that was instrumental in creating itself. The Codex team used early versions to debug its own training I'm happy to see the Codex team moving to this kind of dogfooding. I think this was critical for Claude Code to achieve its momentum.

More importantly, this is the early steps of a model self improving itself. Do we still think we'll have soft take off?

> Do we still think we'll have soft take off?

There's still no evidence we'll have any take off. At least in the "Foom!" sense of LLMs independently improving themselves iteratively to substantial new levels being reliably sustained over many generations.

To be clear, I think LLMs are valuable and will continue to significantly improve. But self-sustaining runaway positive feedback loops delivering exponential improvements resulting in leaps of tangible, real-world utility is a substantially different hypothesis. All the impressive and rapid achievements in LLMs to date can still be true while major elements required for Foom-ish exponential take-off are still missing.

Re: GPT-5.3-Codex

#170
> Using the develop web game skill and preselected, generic follow-up prompts like "fix the bug" or "improve the game", GPT‑5.3-Codex iterated on the games autonomously over millions of tokens.

I wish they would share the full conversation, token counts and more. I'd like to have a better sense of how they normalize these comparisons across version. Is this a 3-prompt 10m token game? a 30-prompt 100m token game? Are both models using similar prompts/token counts?

I vibe coded a small factorio web clone [1] that got pretty far using the models from last summer. I'd love to compare against this.

[1] https://factory-gpt.vercel.app/

Post reply on HN