News
SpaceX installs Raptor Vacuum engine on first orbital-class Starship
Update: Providing the best views yet of the Raptor Vacuum installation process, SpaceX began installing one of Starship S20’s six engines (one of at least two recently trucked to the launch site) on Monday morning.
It remains to be seen exactly how many engines will be installed on Ship 20 or how many will be ignited during its first static fire test but barring the delivery of more Raptors, signs currently point to an initial test of two engines – one sea-level-optimized Raptor Center (RC) and one Raptor Vacuum with a much larger nozzle. Whenever Ship 20 does fire up those engines, it will be the first static fire of a RVac engine installed on a Starship and the first simultaneous, side-by-side static fire of two different Raptor variants. Since publishing time, SpaceX has cancelled a Tuesday road closure, pushing Starship S20’s first static fire attempt to no earlier than (NET) Wednesday evening.
For the third time in two months, SpaceX has begun installing Raptor engines on its first orbital-class Starship prototype – hopefully for good.
In no uncertain terms, Starship 20’s (S20) path to what could be its last Raptor installations has been about as windy and mysterious as they come. Starship 20 (S20) left the Starbase factory floor for the first time in early August – all six Raptors installed in another program first – for a brief fit check and photo op. After spending about an hour installed on top of Super Heavy Booster 4 (B4), Ship 20 was removed and returned to the build site, where teams removed all six engines and finished wiring and plumbing the vehicle.
Days before the ship’s long-anticipated trip to Starbase’s suborbital launch site for qualification testing, the mount SpaceX prepared for the process quickly had hydraulic rams – used to safely simulate Raptor thrust – were abruptly removed. Starship S20 was then installed on the Pad B mount, where SpaceX proceeded to reinstall six Raptors. Weeks later, after slow heat shield repairs neared completion, SpaceX again removed Ship 20’s Raptors and reinstalled the hydraulic rams it had removed – unused – the month prior. Finally, on September 30th, some seven weeks after the prototype arrived at the suborbital launch site, SpaceX put Starship S20 through its first major test – a lengthy ‘cryoproof’.
Now, ten days after completing a seemingly flawless cryoproof test on its first try, SpaceX has once again trucked multiple Raptors – at least one sea level and one vacuum engine – from the Starbase build site to Starship S20’s suborbital test stand. From the outside looking in, it’s hard not to view the contradictory path S20 took to its first tests – and is still taking to its first static fire(s) – as an unusually visible sign of some kind of internal tug of war or major communication failure between different SpaceX groups or executives.
It’s impossible to determine anything specific beyond the apparent fact that several of the steps taken from Ship 20’s first factory departure to its first cryoproof and static fire tests could have probably been deleted entirely with no harm done and many dozens of hours of work saved. At the end of the day, Starship S20 completed cryoproof testing without issue on the first try and is now seemingly on track to begin its first static fire test campaign later this month.
At the moment, SpaceX has three possible static fire test windows scheduled from 5pm to midnight CDT on Tuesday, Wednesday, and Thursday (Oct 12-14). A similar Monday window was canceled days ago on October 7th, suggesting that more cancellations are probably on the horizon. For now, there’s a chance that Starship S20 – with anywhere from two to all six Raptor engines installed – will fire up for the first time before next weekend. It’s hard to say how exactly SpaceX will proceed. It’s not inconceivable that SpaceX will install all six engines and gradually ramp up to a full six-engine static fire over several tests.
Given that SpaceX has already static fired three Raptor Center (RC) engines on multiple Starship and Super Heavy prototypes, odds are good that Starship S20’s test campaign will be similar – beginning with a three-Raptor static fire, in other words. SpaceX could then add one, two, or all three Raptor Vacuum engines into the fray for one or more additional tests with 4-6 engines total. It’s also possible that suborbital launch mount and pad limitations will prevent more than three engines from firing at once, in which case SpaceX would presumably perform two separate tests of Ship 20’s Raptor Center and Raptor Vacuum engines.
Given that two Raptor variants have never been static fired simultaneously on the same vehicle, it’s hard to imagine that SpaceX won’t also want to perform one or several combined static fires with Raptor Vacuum and Raptor Center engines on Ship 20.
Tesla is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.
Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.
The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.
Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:
🚨 There are now SEVEN Tesla Cybercabs registered with the state of Texas
We are just three days from Cybercab! pic.twitter.com/ndwhuFYsep
— TESLARATI (@Teslarati) August 31, 2026
Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.
Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.
The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.
Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.
The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.
Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.
Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.
Tesla has expanded the operational geofence for its driverless Robotaxi service in Austin, Texas, marking the first such increase in some time. The updated Service Area for Robotaxi in Austin now spans about 288 square miles and is roughly 9 percent larger than the previous boundary.
This incremental growth adds approximately 24 square miles of coverage, bringing the prior zone of roughly 264 square miles into a broader footprint that better serves northern suburbs.
The expansion extends the geofence northward toward Pflugerville along the US 183 corridor, incorporating additional neighborhoods north of the Domain and areas such as Mesa Park. These additions include higher-end residential and commercial districts that previously sat just outside the allowed operating zone.
Riders can now request unsupervised trips that begin or end in these newly included locations, provided the entire route remains inside the digital boundary:
Tesla has just expanded its Robotaxi service area in Austin, Texas for the first time in 10 months.
The new service area is roughly 9% larger than the old one, and is about 288 square miles in total. pic.twitter.com/i4oBM1KfWS
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla first launched public Robotaxi operations in Austin in mid-2025 with a modest initial zone of about 20 square miles. Subsequent enlargements in 2025 and early 2026 steadily grew the map until it covered much of the metropolitan area.
After the last major update roughly ten months earlier, the company held the boundary steady while it collected additional miles and refined the FSD suite.
The modest nine percent increase still matters for daily utility. Longer trips become possible, more residents gain access, and the fleet can accumulate more diverse real-world data across new road types and traffic patterns. Observers note that the added territory aligns with existing Tesla service infrastructure, which could support more efficient vehicle staging in the North end of Austin.
Although the geofence has grown, Tesla continues to operate a relatively small unsupervised fleet in the city. The company has emphasized safety and software readiness over rapid geographic scaling. This latest map update signals that Tesla remains committed to expanding Robotaxi availability in its home market as it prepares for further software improvements and potential Cybercab deployments.
The 288-square-mile zone now gives Austin riders one of the larger driverless service areas currently available in the United States.
Tesla’s 2026 Summer Update turns Grok from a talking companion into a true in-car controller, with considerably expanded capabilities. Where the assistant once answered questions and handled navigation, it can now operate hardware and software through ordinary speech, including several requests at the same time.
Grok has become incredibly robust over the past few quarters, and this new ability that Tesla has included with its Summer Update is perhaps the clearest sign of just how capable it has become.
You can issue many commands to Grok at once, and each will be taken care of: anything from headlight control to climate adjustments to mirror folding can now all be taken care of with a simple sentence spoken toward Grok:
This is cool, you can now give Grok a ton of commands at once in your Tesla and it’ll do them all together.
The commands I gave:
• Fold mirrors
• Turn on wipers to fastest setting
• Change temp to 65°
• Open self-driving app
• Open gloveboxComes with Tesla’s 2026 Summer… pic.twitter.com/drZxoHrknv
— Sawyer Merritt (@SawyerMerritt) August 26, 2026
Here’s another example I used in my Model Y:
🚨 Using Grok to control the cabin temperature and turn on headlights in 2026 Model Y on FSD v14.3.8 and 2026.26.6.5 pic.twitter.com/7clgQkGABk
— TESLARATI (@Teslarati) August 27, 2026
Tesla’s official Release Notes list the core powers of Grok’s new capabilities: Grok can place phone calls from a paired phone, search a streaming service and queue music, adjust climate, and search the Controls panel. Drivers can also ask it questions about the vehicle or the latest features included in a recent software update.
It can also take care of driving settings, dynamics, and other relevant preferences that deal with how the car operates and handles.
Tesla Summer Update begins rolling out: a look at the new features
It’s also more of a use case than a novelty feature. Grok was great for learning about something that was being pondered while Full Self-Driving was taking care of the major automotive responsibilities, but it did have some useful functionality when it came to navigation.
Another less-noted improvement is the swift transition that Grok has from thinking of its answer to giving you one. In the past, it would take a few seconds for Grok to truly come up with a valuable response. It now seems that it is improving, at least slightly.
Tesla Cybercab fleet grows in Austin ahead of launch event
Tesla expands driverless Robotaxi geofence in Austin
