News
SpaceX installs first ‘Mechazilla’ arm on Starship launch tower
One month after SpaceX stacked Starship’s South Texas ‘launch tower’ to its full height, the company has installed the first arm on what amounts to the backbone of ‘Mechazilla.’
At the end of July, after less than four months of work, a team of SpaceX workers and contractors installed the final prefabricated section of a ~145m (~475 ft) tall tower meant to support orbital Starship launches. Above all else, SpaceX’s first custom-built ‘launch tower’ is a sort of backbone or anchor point for several massive, mechanical arms that will accomplish the actual tasks of servicing – and, perhaps, catching – Starships and Super Heavy boosters.
Work on all three of the arms expected to make up what SpaceX CEO Elon Musk has described as “Mechazilla” has been visibly underway since the last week of June as a small army of welders carefully assembled dozens of sections of heavy-duty steel pipe into house-sized frames. Almost exactly two months later, SpaceX has installed the first of those three arms on the exterior of Starship’s skyscraper-sized launch tower.
Known as the tower’s quick-disconnect or QD swing arm, the standalone structure is reportedly designed to accomplish a few different tasks. First, as its unofficial name might suggest, the QD arm will hold a quick-disconnect umbilical connector that will temporarily attach to the base of Starships to load them with fuel, oxidizer, and other consumables and link them to ground power and networking. For years, it appeared that SpaceX planned to fuel Starship upper stages through their Super Heavy boosters, which will themselves be connected to umbilical panels on a table-like launch mount that sits beside the tower.
However, once work began on Starship S20, the first potentially space-capable prototype, it was clear that SpaceX had foregone the umbilical plate normally installed at the base of Starship skirts and moved that connection to the ship’s lower back. Musk later confirmed as much in interviews and tweets, revealing that longstanding plans to dock Starships aft to aft for in-space refueling were also up in the air. As of late, aside from reiterating that the launch pad itself (“Stage Zero,” per Musk) is even more complex and difficult than Starship or Super Heavy, SpaceX’s CEO has also repeatedly stated a desire to offload as many systems as possible onto the launch pad – seemingly regardless of the complexity of the alternative.
Enter the building-sized robot informally known as Mechazilla. While the relatively simple swinging ‘QD arm’ that will fuel Starship and stabilize both stages of the rocket is a common feature of rockets and launch pads, the only experience SpaceX itself has with umbilical swing arms is the Crew Access Arm (CAA) that allows astronauts and cargo to board Dragon spacecraft after Falcon 9 goes vertical – a structure with near-zero umbilical utility. Technically, the transporter/erectors (T/Es) that cradle Falcon rockets, lift them vertical, and fuel them before launch have some similarities with swing arms but SpaceX has always used simpler and more reliable passive mechanisms whenever possible.
A step further, though, SpaceX has also seemingly foregone the installation of a basic crane on top of its Starship tower and Musk himself has developed an almost infamous aversion to the inclusion of something as seemingly simple as landing legs on Super Heavy boosters – and, eventually, perhaps even (some) Starship variants. Instead of adding rudimentary legs to Super Heavy prototypes, Musk has seemingly pushed SpaceX to turn Starship’s launch tower into a complex, vulnerable, and fragile rocket recovery system. Beyond the comparatively mundane QD arm, Musk says that SpaceX will ultimately install a pair of massive house-sized steel arms mounted on a sort of external elevator. Those arms will apparently be capable of actuating and moving up and down the tower with the speed, precision, and reliability needed to quite literally catch Super Heavy boosters – and, eventually, Starships – out of mid-air.
The team tasked with designing and building those rocket-catching arms have affectionately deemed them “chopsticks” – a nod towards the kind of nuanced actuation they’ll need to recover the world’s largest rocket boosters and upper stages without missing or destroying them. Having really only just perfected propulsive vertical landing with Falcon 9 and Falcon Heavy boosters, SpaceX thus intends to throw a few extra points of failure into the mix.
To SpaceX and Musk’s credit, whether the company’s second attempt at catching rockets goes as well as the first, some version of the massive ‘chopstick’ arms SpaceX is working on was likely going to be necessary just to rapidly turn around boosters and Starships – and do so regardless (within reason) of weather conditions. By replacing a tower crane with giant arms, SpaceX will hopefully be able to stack Starship on Super Heavy (and Super Heavy on the launch mount) even in the high winds that are almost always present on the South Texas Gulf Coast. If SpaceX can also reliably catch boosters with those arms, it could be a significant upgrade for the operations side of Starship reusability. For now, though, only time will tell.
Tesla’s reason for Starlink integration on Cybercab might surprise you, as the company’s Head of AI, Ashok Elluswamy, finally shed some light on the reason they are putting a satellite internet terminal on its ride-hailing-geared vehicle.
On Monday, Tesla officially confirmed that it would integrate Starlink V5 terminals into Cybercab vehicles, something many Tesla fans had figured the company would do, as the vehicle is primarily geared toward giving rides without any passenger intervention.
Starlink V5 directly integrated in Cybercab pic.twitter.com/FxzTtzjB6I
— Tesla (@Tesla) July 20, 2026
The ability to access the internet would allow riders to work or play in the car with their devices. It seemed like a more-than-reasonable feature to add to the Cybercab, which made its way off the production lines for the first time earlier this year.
Tesla reveals first vehicle model to receive Starlink integration
However, the move is not for the rider, as Elluswamy confirmed on Monday night. Instead, it’s actually for Tesla to be able to have a constant connection to the cars in the Robotaxi fleet so it can troubleshoot issues, contact riders, or resolve other issues.
Elluswamy said:
“It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.”
It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.
— Ashok Elluswamy (@aelluswamy) July 20, 2026
Many initially assumed the option of constant connectivity would be enabled on the Cybercab for passenger entertainment or work. With the Cybercab, passengers won’t be doing anything but enjoying the ride, so it seemed more than logical that they would be hanging out with Starlink internet access as an amenity.
However, Tesla’s primary concern with Robotaxi is safety, and nailing these first unsupervised rides is a crucial step to setting a good narrative on how effective driverless transportation can be.
Being able to get in touch with passengers or a vehicle if something is wrong is a crucial part of the overall experience, and preventative measures are being taken by Tesla to ensure a smooth process, even in the worst-case.
Tesla has expanded its Robotaxi program in Florida to include two new cities: Tampa and Orlando.
This marks the second and third cities to be added to the company’s available locations for autonomous ride-hailing in the Sunshine State, joining Miami, which was the first Florida city to offer Robotaxi rides.
Tesla announced the addition of Orlando and Tampa to the Robotaxi program on Tuesday morning. The cities now join Austin, Dallas, Houston, Miami, and the San Francisco Bay Area as locations where Tesla can operate its Robotaxi platform:
Robotaxi now in Tampa & Orlando! pic.twitter.com/fYtmXgJq3O
— Tesla Robotaxi (@robotaxi) July 21, 2026
These rides are unsupervised, as AI Head Ashok Elluswamy confirmed the suite in Florida is operating without safety drivers or anyone within the cabin to assist with operation.
Orlando Tesla Robotaxi Operation
The geofence in Orlando covers a prominent irregular shaded zone on the map, roughly 4-6 miles across in key dimensions, so it likely measures somewhere between 25 and 45 square miles, which is comparable to other early Tesla launches in other cities.
It encompasses central and southern areas bounded by major highways including SR-417 and SR-528, including parts of the Orlando metro core, tourism-adjacent zones, and residential/commercial districts. This represents an initial targeted rollout in a tourist-heavy region, positioned for quick expansion via Tesla’s software updates.
Tampa Tesla Robotaxi Operation
In Tampa, the shape of the geofence is a shaded polygon covering key neighborhoods, explicitly including West Tampa, Tampa Heights, Hyde Park, and downtown Tampa proper, with boundaries along major roads and the Hillsborough River area.
This focuses on high-demand central zones and will offer tourists and citygoers rides without drivers.
Robotaxi Progress
Tesla has been operating Robotaxi since last June, when it launched in Austin. The geofences in most regions have already expanded several times since their launch last year, but the bigger complaint is vehicle availability. Tesla has been working to add more Robotaxi-enabled vehicles to its fleet.
The company still plans to utilize its Cybercab, a new vehicle that is being produced at Gigafactory Texas, for the Robotaxi suite alongside the Model Y, which has been the vehicle of choice for Tesla with early operations.
News
Tesla’s AI Chief just hinted at something big for FSD v14 lite owners
Tesla’s AI chief suggests the newest FSD v14 Lite build may finally go wide release.
Tesla’s head of AI, Ashok Elluswamy, noted on Sunday that the newest FSD v14 Lite build rolling out to Hardware 3 cars is likely the version that goes to wide release, the strongest signal yet that Tesla is near to closing out an early access phase that Hardware 3 owners have waited more than a year for.
Elluswamy made the comment in response to an extensive review from Tesla owner Zack, known on X as @BLKMDL3, who tested software version 2026.20.6.10 and detailed the changes in a lengthy post. “FSD v14 Lite (for Tesla AI3 hardware vehicles) review.
The update restarts a rollout that had stalled after its initial release. Tesla began pushing FSD v14 Lite to Hardware 3 early access drivers on June 29, bringing driving behavior learned on the newer Hardware 4 computer down to the more limited chip that has powered Tesla vehicles built between 2019 and early 2023. That release, as we covered in detail, gave roughly 4 million HW3 vehicles their first meaningful update since being frozen on version 12.6 in early 2025.
Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features
The latest build adds features that bring Hardware 3 closer in line with what Hardware 4 owners already have. FSD can now start directly from park without a brake pedal confirmation, a change Zack called a small but meaningful quality of life improvement. The interface also picks up the blue “P” park icon, approaching destination alerts, and a dedicated Self-Driving app with streak tracking, all details previously exclusive to the AI4 branch of v14, as outlined in Tesla’s original release notes.
The stakes around Hardware 3 go beyond software polish. Tesla sold the Full Self-Driving package for years on the promise that every vehicle equipped with it had the hardware needed to eventually drive itself without supervision. That promise broke down during Tesla’s Q1 2026 earnings call, when Musk acknowledged HW3 cars could not run unsupervised FSD, prompting Tesla to offer trade-in discounts and hardware retrofits alongside the Lite software track.
Tesla confirmed HW3 can’t do Unsupervised FSD but there’s more to the story
Tesla has continued to frame v14 Lite as the primary path forward for the HW3 fleet, telling owners in April that international markets would follow the U.S. rollout once regulatory approvals came through. For now, HW3 owners in the early access group are the only ones running the new build. A broader rollout would mark the second major software delivery to the legacy fleet since Tesla first released FSD v14 to Hardware 4 vehicles, and the first sign since June that the Lite program is still moving rather than stuck in early access limbo.
Tesla’s reason for Starlink integration on Cybercab might surprise you
Tesla Robotaxi program expands in Florida to two new cities
