Tesla We, Robot: Cybercab, Robovan, and Optimus

Tesla We, Robot Event Record

Tesla's October 2024 We, Robot event revealed Cybercab and Robovan and presented Optimus interactions in a controlled venue. The event did not place all three products into one operational state.

The maintained record should track each product independently and separate company forecasts from later filings, permits, production, and service.

flowchart TD
    A["We, Robot event"] --> B["Cybercab record"]
    A --> C["Robovan record"]
    A --> D["Optimus record"]
    B --> E["Prototype, safety, permit, production, service"]
    C --> F["Prototype, safety, permit, production, service"]
    D --> G["Task, control mode, production, deployment"]
    E --> H["Dated current state"]
    F --> H
    G --> H

State key

Movement in one column does not move every product.

What the event established

Tesla's official We, Robot page preserves the event and the company's framing.

Cybercab appeared as a purpose-built two-seat vehicle concept without conventional driver controls. Attendees experienced rides in a controlled event environment.

Robovan appeared as a larger concept for people or cargo. The event showed its design and proposed role.

Optimus units walked, served, spoke, and interacted with attendees. The visible behavior established that physical units could participate in the prepared environment. The event record alone did not disclose the control mode behind every motion, task, or voice.

Tesla also made forecasts about prices, cost per mile, production, capability, and dates. Those remain attributed forecasts.

Cybercab state

The 2024 reveal established the concept and controlled-event demonstration. It did not establish customer production, public driverless deployment, fleet safety, service economics, or operation across an unrestricted domain.

Tesla's 2025 Form 10-K states that the company launched a Robotaxi service using Model Y vehicles in June 2025 and expects Cybercab to join later.

Tesla's January 2026 company update lists Cybercab as tooling and presents later production plans. “Tooling” is a manufacturing state. It is not customer delivery, deployed fleet volume, permit, or safety finding.

The Cybercab record should not borrow evidence from a Model Y service without naming the difference in vehicle, hardware, controls, domain, operator, and date.

Robovan state

The event established reveal and a visible concept. It did not establish production, route service, passenger capacity under a certified configuration, cargo payload, accessibility, charging infrastructure, operating cost, or autonomous public operation.

Robovan should retain its own product record. A Cybercab manufacturing update does not update Robovan.

The next evidence would include a dated prototype specification, safety disclosure, testing authority, production filing, accessible boarding design, service domain, charging plan, fleet operator, and public terms.

Optimus state

The event showed physical robots interacting with people. The evidence statement should name the environment and avoid inferring internal control from human-like motion or conversation.

The E039 transcript records Dalton's uncertainty about reports of teleoperation. That is not enough to assert which event actions were remotely controlled. A publication needs a named reliable source and a precise distinction among speech, locomotion, manipulation, high-level instruction, remote assistance, direct teleoperation, and safety intervention.

Tesla's 2025 filing describes Optimus as a product the company is working to develop and commercialize. The January 2026 update lists an Optimus facility as construction and describes later production plans.

Those statements do not establish autonomous general-purpose work, production volume, customer delivery, task reliability, safety, or economics.

FSD Supervised is a separate consumer product

Tesla's current FSD Supervised support page says the feature requires an attentive driver and does not make the vehicle autonomous.

That driver-assistance product is not the same thing as a driverless Cybercab or a Robotaxi service. Software relationships do not erase differences in vehicle design, human role, operational domain, permits, and service operation.

NHTSA's automated-vehicle guide distinguishes Level 2 assistance from automated driving systems that perform the full dynamic driving task within a defined domain.

Permit and service evidence

A controlled ride at a private event is not public-road deployment.

California DMV's autonomous-vehicle permit resources separate testing with a safety driver, driverless testing, and deployment.

Every jurisdiction can use different authority and categories. The record should name the regulator, permit, vehicle, operator, domain, effective date, reporting obligation, and service terms.

A company filing that says a service launched establishes the company's disclosure. A full public record should also verify the actual customer access, geography, hours, responsible actor, remote assistance, fleet, fares, incidents, and regulator state.

What moves each record

Cybercab advances through product-specific tooling, production, safety, permits, service, and operating evidence.

Robovan advances through a product-specific prototype, specification, safety case, infrastructure, production, permits, and service.

Optimus advances through disclosed task and control-mode evidence, repeatability, environment variation, safety, production, deployment, and lifecycle support.

The event remains important because it established Tesla's intended direction. The maintained record becomes useful when it stops treating a memorable stage as permanent current status.

This record was developed with AI assistance from the immutable E039 transcript and linked Tesla, NHTSA, California DMV, product-state, and robotics records. Dalton Anderson remains the author. Continuous product, vehicle-safety, robotics, regulatory, current-source, and founder review are mandatory before publication. Publication is not authorized.