Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Rivian built its own AI assistant not to compete with general chatbots, but to create a deep, proprietary integration layer for the car's operating system. This allows them to control which car functions are exposed, ensure safety, and maintain the flexibility to change underlying LLM providers.

Related Insights

Rivian's decision to forgo CarPlay is a long-term strategic bet on AI. The company believes that to deliver advanced, integrated AI features, it must control the entire digital experience, connecting vehicle state, driver history, and various apps鈥攁 task it argues is impossible when ceding control to an overlay like CarPlay.

Instead of a traditional app store, Rivian is developing an 'agentic framework' where services act as agents. The car's primary assistant orchestrates these agents to perform complex tasks (e.g., plan a trip with stops near restaurants, then add to a calendar), creating a more integrated experience than siloed apps.

Incumbent automakers evolved with 100+ separate computer modules, creating a complex system. Newcomers like Rivian and Tesla start with a centralized, "zonal" architecture. This clean-sheet design dramatically simplifies over-the-air updates, reduces costs, and enables more advanced, integrated AI features.

While SaaS tools like Intercom offer immediate convenience, building a custom AI chatbot provides complete control over the workflow, data, and user experience. For companies with some technical capability, this initial investment leads to significant long-term cost savings and a deeply integrated, proprietary solution.

Rivian's CEO explains that early autonomous systems, which were based on rigid rules-based "planners," have been superseded by end-to-end AI. This new approach uses a large "foundation model for driving" that can improve continuously with more data, breaking through the performance plateau of the older method.

Rivian's CEO argues that foregoing CarPlay allows for a more seamless, AI-driven experience where the car's OS has full knowledge of vehicle state. This is a strategic bet on creating a superior, proprietary ecosystem over offering third-party integration.

Waive integrates Vision-Language-Action models (VLAs) to create a conversational interface for the car. This allows users to talk to the AI chauffeur ("drive faster") and provides engineers with a powerful introspection tool to ask the system why it made a certain decision, demystifying its reasoning.

Rivian is adding powerful AI hardware to its cars for edge computing. The business case isn't just better performance; over the long run, processing AI requests locally reduces reliance on cloud servers, saving significant future costs on data connectivity and cloud-based inference.

To address the need for niche apps without adopting CarPlay, Rivian's vision involves its in-car assistant delegating tasks to the user's phone assistant (e.g., Google's Gemini). The phone assistant then controls the app, with output like audio streamed back to the car, preserving Rivian's integrated UI.

Rivian's rejection of CarPlay is a bet on the future of in-car interaction. They argue screen projection cannot support deep, 'agentic' AI integrations that orchestrate tasks across the car's OS, navigation, and personal apps. This deeper capability, they believe, will render CarPlay outdated.