A California judge has forced General Motors’ (GM) self-driving unit Cruise to increase its settlement offer to the maximum amount, after one of the company’s robotaxis pinned and seriously injured a pedestrian in October.
On October 2, a driverless Cruise vehicle dragged and pinned a pedestrian in San Francisco, and the company’s license to operate self-driving cars was immediately revoked by the California Department of Motor Vehicles (DMV). The DMV later said that Cruise “misrepresented” and “omitted” crucial details about its response to the accident, and the California Public Utilities Commission (CPUC) in December ordered the company to appear before a judge this month.
During the hearing, which was held on Tuesday, California Administrative Law Judge (ALJ) Robert Mason III suggested that Cruise revise its $75,000 settlement offer to the maximum penalty of $112,500, after calling the company’s proposed amount “low,” and even suggesting the company was seeking a “discount.”
While Judge Mason III said he appreciated Cruise attempting to take “corrective action” in its crash response procedures, he added that the company should “take a hint” following his multiple questions about the offer amount, suggesting directly that Cruise change its settlement offer to the full penalty.
“Point taken, your Honor,” responded Craig Glidden, Cruise President and Chief Administrative Officer. “We immediately revise our offer to the amount requested.”
Waymo could face new legal barriers in its expansion to Los Angeles
The hearing discussed findings from an investigation conducted by the law firm Quinn Emanuel, which Cruise hired, including that internet connectivity hampered the company’s sharing of video footage from the accident with regulators in meetings that followed.
In response to the motion for approval to settle at $75,000, the commission can adopt, adopt with revisions, or reject Cruise’s filing. Following the hearing, the next step is for Judge Mason to write a proposed decision on the case for the commissioner’s consideration, with the general timeframe falling within about 60 days, as a CPUC spokesperson clarified to Teslarati.
Cruise said it was eager to resolve the case and move past the incident, adding that it wanted to continue to “advance the mission of bringing driverless cars that are safer to the public and also greater accessibility to the public to the market.”
However, Mason didn’t make it sound like the commission was eager to set the case aside:
“While the commission does fall on the side of getting its cases resolved, I don’t know that this is one of those protracted pieces of litigation that we’re usually most anxious to put aside and then move forward with the regulatory process,” Mason added.
In the original motion, filed on January 30, Cruise outlines the key requirements it would have to follow as part of the settlement:
1. Cruise will adopt voluntarily several new data reporting enhancements that will provide additional data to the Commission concerning California collisions and AVs operating in California under a deployment permit that enter a minimal risk condition (“MRC”) state and result in conditions described in Attachment A;
2. Cruise will provide the Commission with Cruise’s responses to the permit reinstatement questions from the California Department of Motor Vehicles (“DMV”) at the same time Cruise provides those responses to the DMV;
3. Cruise will make a payment of $75,000 to the State General Fund within ten (10) days of the Commission’s approval of the Settlement Agreement without modification; and
4. Upon the Commission’s approval of the Settlement Agreement, the OSC proceeding will be closed.
“We are committed to working in partnership with the CPUC, other regulators and government agencies to improve transportation safety in support of a shared goal –– providing better, safer and more accessible transportation to the public in our communities,” a Cruise spokesperson wrote in an email to Teslarati. “Over the past several months, we have taken important steps to improve our leadership, processes and culture, and we are committed to resolving matters to the Commission’s satisfaction as we work to restore regulatory and public trust.”
Cruise also noted that the accident, which occurred after the pedestrian had already been hit by a human driver, was partially caused by the driverless ride-hailing vehicle falsely identifying the situation as a side-impact collision rather than a frontal collision, causing the Minimal Risk Condition (MRC) response that forces the vehicle to pull over.
In addition, Cruise said it is currently expecting a new Chief Safety Officer in the “not too distant future,” after two co-founders resigned immediately following the accident, and after the company fired nine executives and laid off nearly a quarter of its staff on the same day in December.
GM recently announced plans to cut spending on Cruise in half this year, though it said it also hoped to “refocus and relaunch” the company’s operations. GM CEO Mary Barra highlighted significant changes at Cruise, which the company began implementing following the Quinn Emanuel investigation.
“At Cruise, we are committed to earning back the trust of regulators and the public through our commitments and our actions,” Barra said following GM’s 2023 earnings call.
You can see the full January 30 filing from Cruise below, including the findings from the Quinn Emanuel investigation, which Cruise made public last month.
What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send your tips to us at tips@teslarati.com.
Elon Musk
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”
Tesla CEO Elon Musk announces major update with texting and driving on FSD
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.
The Process
Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.
I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.
Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.
I also limited the testing to no more than one minute per attempt.
I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.
The Results
Low Congestion Area
I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:
In full: the Low Congestion Area pic.twitter.com/6DqlBnekPn
— TESLARATI (@Teslarati) December 4, 2025
Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.
I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.
Medium Congestion Area
This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.
I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.
There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:
In full: the Medium Congestion Area pic.twitter.com/gnhIfBVe6Q
— TESLARATI (@Teslarati) December 4, 2025
Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.
High Congestion Area
I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.
As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.
This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:
In full: the High Congestion Area pic.twitter.com/K9rIn4ROvm
— TESLARATI (@Teslarati) December 4, 2025
Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.
My True Thoughts
Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.
The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.
Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.
I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.
Check out our full test below:
Elon Musk
Tesla CEO Elon Musk announces major update with texting and driving on FSD
“Depending on context of surrounding traffic, yes,” Musk said in regards to FSD v14.2.1 allowing texting and driving.
Tesla CEO Elon Musk has announced a major update with texting and driving capabilities on Full Self-Driving v14.2.1, the company’s latest version of the FSD suite.
Tesla Full Self-Driving, even in its most mature and capable versions, is still a Level 2 autonomous driving suite, meaning it requires attention from the vehicle operator.
You cannot sleep, and you should not take attention away from driving; ultimately, you are still solely responsible for what happens with the car.
The vehicles utilize a cabin-facing camera to enable attention monitoring, and if you take your eyes off the road for too long, you will be admonished and advised to pay attention. After five strikes, FSD and Autopilot will be disabled.
However, Musk announced at the Annual Shareholder Meeting in early November that the company would look at the statistics, but it aimed to allow people to text and drive “within the next month or two.”
He said:
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
Does anyone think v14.3 will enable this? pic.twitter.com/N2yn0SK70M
— TESLARATI (@Teslarati) November 23, 2025
Today, Musk confirmed that the current version of Full Self-Driving, which is FSD v14.2.1, does allow for texting and driving “depending on context of surrounding traffic.”
Depending on context of surrounding traffic, yes
— Elon Musk (@elonmusk) December 4, 2025
There are some legitimate questions with this capability, especially as laws in all 50 U.S. states specifically prohibit texting and driving. It will be interesting to see the legality of it, because if a police officer sees you texting, they won’t know that you’re on Full Self-Driving, and you’ll likely be pulled over.
Some states prohibit drivers from even holding a phone when the car is in motion.
It is certainly a move toward unsupervised Full Self-Driving operation, but it is worth noting that Musk’s words state it will only allow the vehicle operator to do it depending on the context of surrounding traffic.
He did not outline any specific conditions that FSD would allow a driver to text and drive.
News
Tesla Semi just got a huge vote of confidence from 300-truck fleet
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
The Tesla Semi is moving closer to broader fleet adoption, with Keller Logistics Group wrapping up a key pre-production planning session with the electric vehicle maker’s team this week.
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
Keller’s pre-production Tesla Semi sessions
Keller Logistics Group, a family-owned carrier with over 300 tractors and 1,000 trailers operating in the Midwest and Southeast, completed the session to assess the Tesla Semi’s fit for its operations. The company’s routes typically span 500-600 miles per day, positioning it as an ideal tester for the Semi’s day cab configuration in standard logistics scenarios.
Details remain under mutual NDA, but the meeting reportedly focused on matching the truck to yard, shuttle and regional applications while scrutinizing economics like infrastructure, maintenance and incentives.
What Keller’s executives are saying
CEO Bryan Keller described the approach as methodical. “For us, staying ahead isn’t a headline, it’s a habit. From electrification and yard automation to digital visibility and warehouse technology, our teams are continually pressure-testing what’s next. The Tesla Semi discussion is one more way we evaluate new tools against our standards for safety, uptime, and customer ROI. We don’t chase trends, we pressure-test what works,” Keller said.
Benjamin Pierce, Chief Strategy Officer, echoed these sentiments. “Electrification and next-generation powertrains are part of a much broader transformation. Whether it’s proprietary yard systems like YardLink™, solar and renewable logistics solutions, or real-time vehicle intelligence, Keller’s approach stays the same, test it, prove it, and deploy it only when it strengthens service and total cost for our customers,” Pierce said.
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Tesla CEO Elon Musk announces major update with texting and driving on FSD
