While this isn’t exactly a feature most users will see often, Tesla has added some features that should help technicians know more about a vehicle’s history. Best of all, while Service History is aimed at technicians, it’s also accessible by any Tesla owner.
So, grab your wrench, and let’s take a detailed look at Tesla’s new Service History.
Service History
Service History is a new feature in Tesla’s Service Mode that tracks all the maintenance a vehicle has received. Technicians are prompted to use Tesla’s Correction Codes, which define the repair that took place and then provide an optional timestamp for the repair being completed. In short, it’s a way to keep track of repairs and services within the vehicle. This should make it easier for technicians to solve issues by being aware of the vehicle’s history.
Service History is accessible directly on the main panel of Service Mode. While Tesla already has internal tools to access a vehicle’s history, the real benefit will be when the vehicle is serviced by different technicians. For example, a local tech could now be services that Tesla serviced performed and vice-versa.
Service history is also permanent and stays with the vehicle. Once entries are added, they cannot be edited or removed, so there’s no tampering with a vehicle’s service history.
You can see the new Service History option on the bottom right.
Not a Tesla App
These timestamped history logs are permanently saved to your vehicle and are accessible by Tesla and anyone else who can put their car into Service Mode. If you want to take a peek and are on 2024.38 or higher, you can follow our Guide on Service Mode here.
Entering a Service Item
When entering a new Service History entry, you’re given a few options, including a Correction Code. Tesla maintains a list of Correction Codes for pretty much everything under the sun, from a full-out swap of the battery pack or one of the motors to things as simple as replacing the wiper blades or adding windshield washer fluid.
Technicians servicing Tesla vehicles will have the option to indicate whether they’re a first-party doing the work (Tesla Service), a qualified third-party independent repairer, or an unknown—like the vehicle owner themselves.
The pop-up that displays when you open Service History.
Not a Tesla App
If you’d like to add an entry yourself, you can give it a try, as it’s pretty straightforward. You can select a Correction Code for something you’d normally DIY, like adding washer fluid. You can then select a timestamp, which is optional, and then select what type of repairer you are - first party, qualified third party, or other.
Expanding Service History
Tesla’s new Service History is a really interesting idea. It puts third-party technicians and vehicle owners on equal ground, with everyone having access to a vehicle’s history. It’s also going to be useful for owners to keep track of simple tasks like tire rotations, wiper blade replacements, low-voltage battery replacements, and more.
Service History also helps solve the issue of Tesla not being able to effectively track vehicle services done by qualified third-party repair shops, who often won’t push the vehicle correction codes via Toolbox 3.
Instead, this allows even unfamiliar repair technicians an easy-to-see and easy-to-use solution to log and diagnose potential issues quickly.
We’d love for Tesla to make Service History even more accessible, potentially moving it out of Service Mode, which only a small percentage of owners will ever go into.
It’d be useful if Tesla moved certain options into the main Controls > Service area, allowing vehicle owners to add simple things like adding windshield wiper fluid. For more complex changes, Tesla could ask owners to enter Service Mode, and remind them that all entries are permanent and can not be changed or removed, even by Tesla.
Subscribe
Subscribe to our newsletter to stay up to date on the latest Tesla news, upcoming features and software updates.
Tesla has always embraced whimsy in its software, packing it with playful Easter eggs and surprises. From transforming the on-screen car into James Bond’s submarine to the ever-entertaining Emissions Testing Mode and the fan-favorite Rainbow Road, these hidden features have become a signature part of Tesla’s software.
Of course, launching a new product like Robotaxi wouldn’t be complete without a fun little easter egg of its own. The end-of-ride screen in the Robotaxi app presents a familiar option “Leave a tip.”
For anyone pleased with their Robotaxi ride, they may be tempted to leave a tip. However, tapping the button presents our favorite hedgehog instead of a payment screen.
The app displays a message, alongside the familiar Tesla hedgehog, that simply states “Just kidding.”
While it's a fun prank, it’s also a nod to what Tesla really wants to do. They want to reinforce the economic advantage of an autonomous Robotaxi Network. Without a driver, there is simply no need to tip. The gesture is playful, but it’s a reminder of what Tesla’s real aim is here.
Over the last few days, we’ve seen some exceptionally smooth performance from the latest version of FSD on Tesla’s Robotaxi Network pilot. However, the entire purpose of an early access program with Safety Monitors is to identify and learn from edge cases.
This week, the public saw the first recorded instance of a Safety Monitor intervention, providing a first look at how they’re expected to stop the vehicle.
The event involved a complex, low-speed interaction with a reversing UPS truck. The Safety Monitor intervened to stop the Robotaxi immediately, potentially avoiding a collision with the delivery truck. Let’s break down this textbook case of real-world unpredictability.
The Intervention [VIDEO]
In a video from a ride in Austin, a Robotaxi is preparing to pull over to its destination on the right side of the road, with its turn signal active. Ahead, a UPS truck comes to a stop. As the Model Y begins turning into the spot, the UPS truck, seemingly without signaling, starts to reverse. At this point, the Safety Monitor stepped in and pressed the In Lane Stop button on the main display, bringing the Robotaxi to an immediate halt.
This is precisely why Tesla has employed Safety Monitors in this initial pilot. They are there to proactively manage ambiguous situations where the intentions of other drivers are unclear. The system worked as designed, but it raises a key question: What would FSD have done on its own? It’s not clear whether the vehicle saw the truck backing up, or what it would do when it finally detected it. It’s also unclear whether the UPS driver recognized that the Robotaxi was pulling into the same spot at the exact same time.
It’s possible this wouldn’t result in a collision at all, but the Safety Monitor did the right thing by stepping in to prevent a potential collision, even one at low speed. Any collision just a few days after the Robotaxi Network launch could result in complications for Tesla.
Who Would Be At Fault?
This scenario is a classic edge case. It involves unclear right-of-way and unpredictable human behavior. Even for human drivers, the right-of-way here is complicated. While a reversing vehicle often bears responsibility, a forward-moving vehicle must also take precautions to avoid a collision. This legal and practical gray area is what makes these scenarios so challenging for AI to navigate.
Would the Robotaxi have continued, assuming the reversing truck would stop?
Or would it have identified the potential conflict and used its own ability to stop and reverse?
Without the intervention, it’s impossible to say for sure. However, crucial context comes from a different clip involving, surprisingly, another UPS delivery truck.
A Tale of Two Trucks
In a separate video posted on X, another Robotaxi encounters a remarkably similar situation. In that instance, as another UPS delivery truck obstructs the path forward, the Robotaxi comes to a stop to let its two passengers out just a few feet from their destination.
Once they depart, the Robotaxi successfully reverses and performs a three-point turn to extricate itself from a tight spot. That was all done without human intervention, by correctly identifying the situation.
This second clip is vital because it proves that the Robotaxi's FSD build has the underlying logic and capability to handle these scenarios. It can, and does, use reverse to safely navigate complex situations.
Far from being a failure, this first intervention should be seen as a success for Tesla’s safety methodology. It shows the safety system is working, allowing monitors to mitigate ambiguous events proactively.
More importantly, this incident provides Tesla’s FSD team with an invaluable real-world data point.
By comparing the intervened ride with the successful autonomous one, Tesla’s engineers can fine-tune FSD’s decision-making, which will likely have a positive impact on its edge case handling in the near future.
This is the purpose of a public pilot — to find the final edge cases and build a more robust system, one unpredictable reversing truck at a time.
![First Recorded Tesla Robotaxi Intervention: UPS Truck Encounter [VIDEO]](https://www.notateslaapp.com/img/containers/article_images/2025/robotaxi_model_y.jpg/3036d8b53214c2d071c978c42911e451/robotaxi_model_y.jpg)
![First Look at Tesla's Robotaxi App and Its Features [PHOTOS]](https://www.notateslaapp.com/img/containers/article_images/tesla-app/robotaxi-app/robotaxi-app-tips.webp/e643a61975bf712d18dc9aa9a48fdb01/robotaxi-app-tips.jpg)
![Tesla’s New Camera Cleaning Feature and the Future of Cleaning Robotaxis [VIDEO]](https://www.notateslaapp.com/img/containers/article_images/2024/windshield-rain-droplets.jpg/8335f3020509dab3cdb56c1a91d054a9/windshield-rain-droplets.jpg)
![Tesla Launches Robotaxi: Features, Robotaxi App, Command Center and First Impressions [VIDEO]](https://www.notateslaapp.com/img/containers/article_images/2025/robotaxi_rear_screen.jpg/bf5ea088bdebda8ca7e0aa1503b69f4e/robotaxi_rear_screen.jpg)
_300w.png)
![Andrej Karpathy considers returning to Tesla to work on Optimus [video]](https://www.notateslaapp.com/images/news/2022/karpathy-podcast_300w.jpg)
