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.
Elon Musk
OpenAI cites distrust of SpaceX in decision to drop Cursor partnership
OpenAI will cut SpaceX-owned Cursor’s model access in November, citing Musk’s history of broken contracts.
OpenAI, the company behind ChatGPT, announced late Friday that it is ending its partnership with Cursor, cutting off the coding tool’s access to its models on November 12. The move comes two weeks after SpaceX completed its $60 billion acquisition of Cursor’s parent company, Anysphere, folding the popular AI coding assistant into Elon Musk’s growing SpaceXAI division.
In a post on its website, OpenAI said the decision came down to trust, not technology. “We cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk’s companies violating contracts,” the company wrote. OpenAI pointed to two specific incidents: X, now part of SpaceX, allegedly breaking the terms of an existing OpenAI contract after Musk bought Twitter.
That lawsuit is the backdrop for all of this. Musk cofounded OpenAI in 2015, left the board in 2018, and sued Sam Altman and Greg Brockman in 2024, arguing they abandoned the company’s nonprofit mission for profit. A federal jury sided with OpenAI in May, finding Musk waited too long to sue rather than ruling on the merits of his claims. Musk said at the time he would appeal to the Ninth Circuit, calling the outcome a “calendar technicality” rather than a real judgment.
SpaceX’s interest in Cursor predates that verdict by weeks. The company first struck a deal with Cursor in April, securing an option to acquire it for $60 billion or pay $10 billion for joint development work instead. As Teslarati reported at the time, the logic was straightforward: Cursor was paying retail prices to Anthropic and OpenAI, two of its most direct competitors, every time a developer used its product, while SpaceX had idle capacity on its Colossus supercomputer, roughly the equivalent of a million Nvidia H100 GPUs, that Cursor could use to train its own models instead. SpaceX exercised the option in June, days after its own IPO, and the deal closed in mid-August.
Once it closed, Musk moved fast. On an all-hands call with more than 1,000 Cursor employees, he reportedly told staff that SpaceXAI’s Grok was playing catchup in the AI race, unlike Tesla and SpaceX in their own markets, and singled out Anthropic as the company to catch. Cursor CEO Michael Truell now reports directly to Musk inside SpaceXAI.
Losing OpenAI’s models leaves Cursor leaning harder on Anthropic’s Claude, which has its own compute agreement with SpaceX, and on Cursor’s in-house Composer model, the one SpaceX’s compute was supposed to accelerate in the first place. OpenAI framed the November deadline as maximum notice under its contract, and said it wants to “go above and beyond” to help developers through the transition. Whether Anthropic makes the same call is now the open question in AI coding.
The in-car Tesla Theater is among the most unique features available within the cars. When charging, parked, camping, or just hanging out, vehicle occupants can access a variety of streaming platforms on the large center screen, helping keep them entertained during downtime.
However, the Theater might be getting plenty more streaming platforms, something that owners have requested for some time.
Tesla owners recently discovered that visiting Apple TV in the vehicle browser can launch a fullscreen interface that looks and behaves like a dedicated application rather than an ordinary webpage:
Today I learned that if you go to Apple TV in the Tesla browser, it will open up an actual Apple TV app, fully functional. Not just the site.
Apparently there are more apps than just the few that show on the apps page. pic.twitter.com/os1Ypfm4JR
— Jason W (@jmwilt21) August 20, 2026
The experience drops the usual address bar and browser chrome, presenting catalogs, continue watching rows, and playback controls in the same window Tesla Theater already uses for its listed services. Independent testers soon found similar treatment for HBO Max, Paramount+, Peacock, Disney+, and Prime Video when those sites are opened from the car browser.
This shift is a plausible early signal that Tesla is widening Theater support without a formal software note. Theater has long been a set of web views rather than native applications, so recognizing extra domains and stripping the browser frame is a small server-side change that can expand the catalog quickly.
Owners still lack permanent Theater icons for the newly recognized services, and video remains limited to Park, yet the smoother launch is a meaningful step toward a broader lounge while charging.
Tesla Theater arrived with software version 10 in September 2019. The first video services were Netflix, YouTube, and Hulu, available only while parked and originally tied to WiFi. Spotify arrived in the same era as music rather than Theater video. Disney+ joined officially in July 2021 with the 2021.24 update, giving owners another major catalog on the center screen. Twitch and TikTok later appeared among the default Theater tiles, and Tesla Tutorials remained a persistent educational tile.
Not every addition stayed put. In December 2023, a Holiday software build removed the Disney+ tile for many United States owners after a public dispute involving advertising on X. Hulu stayed visible even though Disney owned it. Visiting disneyplus.com in the browser often restored the tile, which suggested the removal was a recognition list change rather than a complete block. Owners have also reported occasional blank Theater grids after updates, usually fixed by language toggles, resets, or later firmware.
Tesla axes Disney+ from vehicles with Musk-Iger rivalry, but there’s a workaround
Code archives from 2024 listed many unused source names, including Apple TV and Prime Video, that never became official icons, which now looks like groundwork for the current fullscreen browser behavior.
Now that this hint toward an expanded Theater experience has been recognized, Tesla could follow through with these additional shortcuts as a sign that more streaming platforms are available in Teslas than ever before.
Tesla recently received its largest order for the all-electric Semi from Einride, a Swedish transport service, for 500 units, a groundbreaking invoice to receive before the first deliveries begin.
Even more remarkable, Einride CEO Roozbeh Charli said in a recent interview that he expects his company to take delivery of all 500 — the entire order — before the end of 2027. He even expects to have 75 Tesla Semi units in the Einride fleet before the end of this year.
🚨 Einride CEO Roozbeh Charli on the Tesla Semi partnership:
“If we start with the Amazon announcement that we did earlier this year, that was on the back of having gone through a proving period together with them and proving out our technology. Then we took that next step in… pic.twitter.com/oazkXjwoig
— TESLARATI (@Teslarati) August 28, 2026
Charli said the Tesla partnership was part of a broader push, along with its earlier partnership with Amazon. Einride is assisting Amazon with the use of its Saga AI platform, which helps eliminate questions about budgeting and forecasting for logistics companies.
The Semi, as well as Tesla’s production and subsequent delivery of the units to Einride, will help the company “to have a good supply of vehicles that we can deploy on the [Saga AI] platform,” Charli said. “Tesla is also a relationship we’ve had for a while, and as the Tesla Semi deliveries are firming up, we decided to do a larger commitment to that and deploy that on our platform.”
In its initial announcement, Einride said it anticipated taking delivery of the trucks over the next two years, but now it appears the company is expecting all 500 units within the next 16 months.
Built at a dedicated factory in Sparks, Nevada, the Tesla Semi has been perhaps the biggest and most intensive testing process the company has ever had for a single vehicle model. For the past several years, Tesla has been working with many companies, most notably Frito-Lay and PepsiCo, to gain knowledge on the performance on regional routes.
Tesla plans to launch the Semi officially on September 24, five months after production started ramping.
Additionally, drivers have said they are happy about the Semi’s performance and that its numerous safety and productivity features have made their jobs and routes much easier.
OpenAI cites distrust of SpaceX in decision to drop Cursor partnership
Tesla Theater might be getting plenty more streaming platforms
