Live data from Hacker News

GPT‑5.3‑Codex‑Spark

openai.com

11–20 of 415 posts

Re: GPT‑5.3‑Codex‑Spark

#15
post #10

This is interesting for offloading "tiered" workloads / priority queue with coding agents. If 60% of the work is "edit this file with this content", or "refactor according to this abstraction" then low latency - high token inference seems like a needed improvement. Recently someone made a Claude plugin to offload low-priority work to the Anthropic Batch API [1]. Also I expect both Nvidia and Google to deploy custom s…

I built something similar using an MCP that allows claude to "outsource" development to GLM 4.7 on Cerebras (or a different model, but GLM is what I use). The tool allows Claude to set the system prompt, instructions, specify the output file to write to and crucially allows it to list which additional files (or subsections of files) should be included as context for the prompt.

Ive had great success with it, and it rapidly speeds up development time at fairly minimal cost.

Re: GPT‑5.3‑Codex‑Spark

#16
post #4

In my opinion, they solved the wrong problem. The main issue I have with Codex is that the best model is insanely slow, except at nights and weekends when Silicon Valley goes to bed. I don't want a faster, smaller model (already have that with GLM and MiniMax). I want a faster, better model (at least as fast as Opus). When they partnered with Cerebras, I kind of had a gut feeling that they wouldn't be able to use the…

> In my opinion, they solved the wrong problem. The main issue I have with Codex is that the best model is insanely slow, except at nights and weekends when Silicon Valley goes to bed. I don't want a faster, smaller model (already have that with GLM and MiniMax). I want a faster, better model (at least as fast as Opus).

It's entirely possible that this is the first step and that they will also do faster better models, too.

Re: GPT‑5.3‑Codex‑Spark

#17
It'll be nice when there's smarter routing between models, or easier routing, so some things get sent to the fast model, some get sent to the cheap model, some get sent to the smart model, etc.

Re: GPT‑5.3‑Codex‑Spark

#18
post #4

In my opinion, they solved the wrong problem. The main issue I have with Codex is that the best model is insanely slow, except at nights and weekends when Silicon Valley goes to bed. I don't want a faster, smaller model (already have that with GLM and MiniMax). I want a faster, better model (at least as fast as Opus). When they partnered with Cerebras, I kind of had a gut feeling that they wouldn't be able to use the…

> In my opinion, they solved the wrong problem. The main issue I have with Codex is that the best model is insanely slow, except at nights and weekends when Silicon Valley goes to bed. I don't want a faster, smaller model (already have that with GLM and MiniMax). I want a faster, better model (at least as fast as Opus). It's entirely possible that this is the first step and that they will also do faster better models…

I doubt it; there's a limit on model size that can be supported by Cerebras tech. GPT-5.3 is supposedly +1T parameters...

Re: GPT‑5.3‑Codex‑Spark

#20
The search for speed is vain. Often Claude Code Opus 4.6, on hard enough problems, can do the impression of acting fast without really making progresses because of lack of focus on what matters. Then you spin the much slower GPT 5.3-Codex and it fixes everything in 3 minutes of doing the right thing.
Post reply on HN