
In this article (4)
GM in-vehicle AI as vehicle software platform analysis
Key Takeaways
- Watch whether automakers connect AI to vehicle data, not just voice prompts.
- Treat in car AI as a permissions and tooling problem before a model selection problem.
- Expect regulation and model testing to matter more as assistants touch vehicle context.
CNBC reports GM plans its own in cabin AI later this year, and the real story is the software stack under the cupholders.
Your car used to communicate through sacred dashboard runes: check engine, tire pressure, and the tiny oil can that looks like Aladdin got into maintenance. Now General Motors wants the cabin to talk back with something more useful than a Bluetooth menu designed by a committee of haunted printers. According to CNBC, GM plans to launch its own in-vehicle artificial intelligence system later this year. The interesting part is not that a car company wants an assistant. The interesting part is that the assistant may stop being a dashboard feature and start becoming part of the vehicle software platform itself.
What GM Is Actually Planning
CNBC reports that General Motors plans to launch a proprietary in-vehicle AI system later this year, built to be better tailored for GM customers. The same CNBC report says the planned GM assistant is expected to be more integrated with the vehicle than the company’s recently launched Google Gemini assistant. GM is also working with an unnamed large language model provider, according to CNBC, with potential capabilities including predictive maintenance, vehicle telemetry, and other auto focused features. That is the difference between asking a chatbot where the wiper controls are and asking a vehicle system why the left rear tire is auditioning for a sad trombone. The technical lesson is straightforward, if not easy: useful car AI depends less on chatbot sparkle and more on trusted access to vehicle context. Telemetry, diagnostics, service signals, and infotainment state are the data plumbing. The model is the talkative raccoon in the HVAC ducts, but the permissions layer decides whether it can merely explain a warning light or help route you toward service. That is where automakers want control, because whoever owns the in cabin software layer owns the relationship after the sale.
Gemini Was the On Ramp
CNBC notes that GM began rolling out Google’s Gemini in eligible model year 2022 and newer Cadillac, Chevrolet, Buick, and GMC vehicles in the U.S. earlier this year with Google Built-in. That matters because GM is not asking drivers to leap from knobs and menus straight into sentient dashboard poetry. It is introducing conversational interaction first, then aiming for a more vehicle specific layer. Baby steps, but the baby has CAN bus access, so maybe put the snacks away. An earlier CNBC report also placed Google AI inside a broader set of GM vehicle software initiatives targeted by 2028, including new in-vehicle tech and a driver assistance system described as allowing hands free and eyes off driving while still letting the driver take control. I am leaving the chip analysis to Theo, because nothing ruins a clean software column like suddenly arguing about TOPS in a parking lot. But at the platform level, the pattern is clear: the cabin is becoming a software surface that updates, personalizes, and connects to vehicle functions. The AI assistant is not the destination. It is the interface layer with better jokes and, ideally, fewer hallucinated service intervals.
Why This Is Harder Than Putting ChatGPT in a Cupholder
The research community has been circling this problem for a while. The arXiv paper titled Integrating Generative Artificial Intelligence in Intelligent Vehicle Systems frames generative AI as something to be embedded inside intelligent vehicle systems, not merely slapped onto infotainment like a decorative spoiler. That distinction matters because cars are safety constrained, sensor rich, latency sensitive environments. A browser tab can be wrong and annoy you. A vehicle assistant being wrong near maintenance, navigation, or controls needs stronger guardrails than vibes and a shrug emoji. For builders, the useful architecture looks less like one giant model pretending to be your mechanic and more like a routed system. The assistant should interpret intent, call approved tools, retrieve vehicle specific documentation, inspect telemetry only with proper permission, and refuse tasks outside its lane. This is classic applied AI, not model astrology. If your demo cannot explain what data it used and what action it is allowed to take, congratulations, you have built a very confident parrot in a dashboard.
Regulation Will Ride Shotgun
Axios reports that Europe and the United Kingdom are fine tuning approaches to AI model testing while a deadline looms for the U.S. government to set its own AI rules. Axios also notes that U.S. allies have been grappling with similar AI safety questions for years. In vehicles, that policy conversation gets practical fast. Model testing is not abstract when the assistant may interpret telemetry, maintenance signals, or driver requests inside a moving machine. GM’s launch window gives the industry something concrete to watch: how much integration automakers expose at first, how they explain data use to drivers, and how clearly they separate advice from action. Readers building products in this space should pay attention to the boring bits, especially permissions, logs, fallbacks, and human handoff. The assistant that wins will not be the one with the sassiest voice. It will be the one that knows when to stop talking and let the car be a car.