On 1 October 2026 Callstack made Apex generally available. It is a coding model for everyday agent work, with the stated strength in React Native and Next.js: features, failing builds, review, and tests, inside the editor you already use. The post is on Callstack’s blog. It is offered through the Apex API, with Vercel AI Gateway planned and commercial self-hosting for teams that want it on their own machines.
The base model moved. The first Apex sat on Gemma 4. This one sits on Qwen. Callstack’s claim is the data, the evaluations, and the deployment around that base, not a new architecture. Native iOS and Android models are the stated next step. They are also building tools so an agent can operate a mobile app and keep evidence of what the screen did.
Specialization is a serious entry in the race
A general model that can write Rust, SQL, and a React screen will still write a React Native screen that looks right and breaks on the device. I have spent four years in that stack. The failures are specific: navigation state, lists that drop frames, a style that works on iOS and not Android. A model aimed at that surface is allowed to be worse at everything else.
I would still read the diff. Specialization does not remove the need for a running app. The useful part of their roadmap is the tool that drives the simulator and saves what happened. A passing paragraph about a component is weaker than a screenshot of the screen the agent just opened.
How I would try it
- One real Next.js bug and one real React Native bug, not a greenfield demo.
- The same tasks on the general model you already pay for.
- Keep the winner only if the specialized model is cheaper or more often right on those tasks.
The model race is no longer one ladder. This month has a frontier agent, a small open coder, and a React specialist. Use the one whose narrowness matches the files in front of you.