This is a preview from our weekly newsletter. Each week I go ‘Beyond the News’ and handcraft a special edition that includes my thoughts on the biggest stories, why it matters, and how it could impact the future.
Earlier this week, there was plenty of talk about the Revel taxi fleet in New York City, comprised of 50 Tesla Model Y all-electric crossovers that would contribute to the ride-sharing services that the Big Apple has long been accustomed to over the past century. As the automotive sector has transitioned to a more sustainable look and feel, taxi companies are also putting their hand in the cookie jar, adding sustainable vehicles to their fleets, and taking gas-powered machines off the road.
Revel is an independent company attempting to make this happen. The company has 50 Model Y taxis ready to take on the streets of Manhattan and the other boroughs of New York. However, reports circulated earlier this week that the New York City Taxi and Limousine Commission blocked this possibility overwhelmingly with a five-to-one vote.
New York City Taxi and Limousine Commission: A Giant Game of Telephone
While the reports from various media outlets, including our own, highlighted the spectacle, which seemed to be an incredible chance of corruption, there was actually a huge misunderstanding. New York City TLC’s Deputy Chief of Public Affairs, Allan Fromberg, took some time out of a busy Thursday to talk to me, clarifying the situation that has been misconstrued since its original report.
Tesla Model Y taxi fleet successfully blocked by NY commission
After getting in touch with Mr. Fromberg on Thursday, we talked about the initial reports. “The whole narrative that Revel would have to buy 50 gas cars to then convert to EVs is just a giant game of telephone. In fact, for Revel to bring on its 50 BEVs, they would have to replace 50 existing, already-licensed vehicles, and not new vehicles.”
Initial reports indicated that TLC Commissioner Aloysee Heredia Jarmoszuk stated that congestion was why Revel wasn’t granted licenses. In fact, this is true. Revel was never required to purchase 50 gas vehicles, which didn’t make much sense from the get-go. In my initial communication to Mr. Fromberg, I stated that the contradictory nature of the TLC’s implied decision to block Revel’s Model Y fleet because of congestion, but then suggest 50 additional gas-powered vehicles needed to be purchased didn’t make much sense.
Fromberg agreed and said that this misconception was due to the aggregation of media reports looking to push out this controversial angle of the story quickly.
Mr. Fromberg then explained what the vote on Tuesday evening entailed, straight from the TLC Commissioner’s mouth.
2018 Legislation: The Taxi Cab “Cap”
Ms. Jarmoszuk said:
“First and foremost, no one and no entity has been blocked. The public meeting/vote was neither about electric vehicles nor about any particular company nor about car models. Rather, the public meeting was about vehicle licenses, which are presently capped since the market is saturated and distressed, with low performance as a result of the pandemic and previous market stressors. Presently, there are nearly 100K vehicle licenses, which is too large a supply for current passenger demand. The public meeting was about ensuring mechanisms to properly manage applications for new/additional licenses against current ridership numbers/needs.”
This is actually in reference to series of five pieces of legislation that were passed in 2018. According to the New York City Office of the Mayo, on August 14th, 2018, Mayor Bill de Blasio signed the following pieces:
144-B: Requiring the TLC to stop issuing for-hire vehicle licenses for 12 months, to study congestion and various aspects of the industry, and after the study, allows the TLC to establish vehicle utilization standards and regulate the number of for-hire vehicle licenses;
634-B: Waiving licensing fees for accessible taxi-cabs and for-hire vehicles;
838-C: Pertaining to the licensing and regulation of high-volume for-hire vehicle services;
890-B: Directs the TLC to establish rules to provide minimum payments to high-volume for-hire vehicle drivers;
958-A: Reducing penalties for unauthorized street hails.
Really, 144-B, 634-B, 838-C, and 890-B are the four pieces that are relevant to this story. In 2018, 144-B halted the licensing of any additional “For-Hire” vehicles, meaning taxis or ride-hailing vehicles. Simply put, there was an incredible number of vehicles on the streets of New York, and congestion was becoming a real issue there. The “cap” limit on the number of vehicles was enforced in 2018 and was set to last one year. Mr. Fromberg informed me that this legislation has been extended and renewed several times and is still effective to this day. Therefore, the City still will not license any additional vehicles. When one fails or loses its license, a new vehicle takes its place.
There are several other reasons for this, including fair wages for drivers and affordability for taxi companies. But, unfortunately, drivers were suffering and still are due to the COVID-19 pandemic. While many of the economic negativities are finally beginning to subside, 2020 was an ugly year for the NYC taxi sector. Many drivers weren’t making enough money to afford loan payments on medallions. Unfortunately, some of these drivers took their own lives, and it is an absolute tragedy that this occurred.
With that being said, taxi drivers are hard-working, and they deserve to make enough money to feed their families. In the 2018 passing of these legislative pieces, De Blasio said, “We’re putting hardworking New Yorkers ahead of corporations. We are taking immediate action for the benefit of more than 100,000 hard-working New Yorkers who deserve a fair wage and halting the flood of new cars, grinding our streets to a halt.” The changes increased take-home pay for drivers by approximately 20 percent on average — more than $6,000 per year.
With all of that being said, New York City is operating with a substantial number of taxis, and the TLC has granted nearly 100,000 vehicle licenses. Before any more vehicles can obtain one of these licenses, some of the current vehicles must lose their licenses through expiration or vehicle removal in a company’s fleet. When 50 licenses open up, Revel will have the ability to obtain them, giving the company full rights to operate as a ride-sharing service, just as it aims to do.
To Mr. Fromberg’s knowledge, there would be no cost for Revel to go through the normal administrative procedure to obtain the licenses.
Revel’s Response: EV Taxis are a necessity to NYC
Revel CEO Frank Reig is under the impression that the TLC is operating under “shortsighted bureaucracy and entrenched interests,” according to a Tweet from Wednesday night.
After the Tuesday hearing, Reig said:
“At today’s hearing, the Taxi and Limousine Commission offered no evidence or analysis to support ending the EV exemption. The Commissioners sat through almost 3 hours of testimony on all sides yet asked zero questions and spent zero time deliberating before making a policy decision with profound consequences. The TLC never intended to consider what drivers and New Yorkers had to say, and only cared about jamming through this vote on Primary Day with as little scrutiny as possible. This decision doesn’t change the fact that New York City needs an alternative to the predatory leasing system that exploits drivers and pollutes our environment, and Revel is exploring ways to accomplish that.”
Revel told Teslarati earlier today that it is aware that the TLC is not recommending the purchase of 50 gas-powered cars. The company is also aware that the TLC has capped the number of licenses it would issue. In order to encourage the adoption of electric cars, Revel spokespeople said that additional licenses would be given to wheelchair-accessible vehicles and EVs. A few hundred EVs have been added to the NYC Taxi fleet in the past two years, but these cars only account for .5% of the total number of For-Hire vehicles on NYC’s streets.
Tesla Model 3 wins hearts as famed NYC Taxi, picks up where Nissan Leaf couldn’t
This rule is brought up every six months and was last addressed and subsequently renewed in February. That means that it was due for review in August. However, the TLC brought the issue to light early and revoked the rule. The TLC says that if Reval wants to operate a rideshare service with its fleet of 50 Model Ys, they will have to obtain the licenses from displaced and no-longer-active taxis in the city.
Revel states that it would take two to three additional vehicles off of the street because the company will hire TLC-licensed drivers, who will no longer lease gas-powered vehicles. In addition, revel owns the vehicles, and different drivers will use the same car through different shifts, which could become a long-term advantage for the TLC as fewer cars will be on the street.
This would also line up with the Legislature items 634-B and 890-B, which would alleviate short-term leases and provide drivers with guaranteed wages, benefits, and vacation time.
The Bottom Line
The issue is this: Congestion is a real issue in the city. And while EVs only making up .5% of the total taxi fleet in the Big Apple, there is evidently no room for more vehicles, of any kind, in the City. Over time, the concentration of EV Taxis in the City that Never Sleeps will surely rise, but the existing vehicles need to be removed from the licensing pool before Revel can unleash its 50 all-electric Model Y taxis.
To summarize it easily, Fromberg said: “The TLC is fully committed to a 100% electrified future, just not at the cost of additional congestion.”
A big thanks to our long-time supporters and new subscribers! Thank you.
I use this newsletter to share my thoughts on what is going on in the Tesla world. If you want to talk to me directly, you can email me or reach me on Twitter. I don’t bite, be sure to reach out!
-Joey
On behalf of the entire Teslarati team, we’re working hard behind the scenes on bringing you more personalized members benefits, and can’t thank you enough for your continued support!
News
Tesla briefly offered this Robotaxi part for your personal car
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
News
Tesla Robotaxi gets sweeping but polarizing change
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

