On May 28, 2026 BYD announced the Xuánjí A3, described as China’s first 4nm smart driving chip, at its “Dare To” intelligence strategy event. The in‑house SoC delivers over 2,100 TOPS with three chips, supports L3–L4 automated driving, and is already in mass production for BYD vehicles.
This article aggregates reporting from 1 news source. The TL;DR is AI-generated from original reporting. Race to AGI's analysis provides editorial context on implications for AGI development.
BYD’s Xuánjí A3 is less about headline FLOPS and more about where intelligence lives in the car. A 4nm, 2,100‑TOPS in‑vehicle chip designed for L3–L4 driving pushes more of the autonomy stack to the edge, reducing dependence on cloud inference and giving Chinese OEMs a domestically controlled alternative to Nvidia and Qualcomm. ([ithome.com](https://www.ithome.com/0/956/808.htm)) Combined with BYD’s vertically integrated battery and power electronics business, this moves it closer to being a full‑stack “intelligent mobility” company rather than a carmaker gluing third‑party chips into vehicles.
In the AGI context, smart‑driving chips matter because they are a proving ground for embodied, safety‑critical AI at scale. If BYD can ship millions of vehicles running high‑capacity perception and planning models on‑device, it will generate vast amounts of real‑world trajectory data—fuel for future foundation models that blend language, vision and control. It also tightens the feedback loop between semiconductor process nodes and AI capabilities: as carmakers like BYD and Tesla push automotive chips to 4nm and below, they create another demand vector for advanced fabs beyond cloud GPUs.
Strategically, this is a shot across the bow of Western AI‑chip suppliers and a signal to Chinese policymakers that industrial policy around domestic AI hardware is bearing fruit. For the global race, it reinforces a trend: advanced AI compute is no longer just something hyperscalers hoard in data centers; it’s increasingly embedded in fleets of robots and vehicles whose upgrade cycles and safety regimes look very different from web services.


