News
SpaceX CEO Elon Musk talks Starship explosion: “We were too dumb”
Two days after a last-second failure caused Starship SN9 to smash into the ground and explode, SpaceX CEO Elon Musk has returned to Twitter with some harsh preliminary reactions.
Right off the bat, in response to a question about why Starships SN8 and SN9 both attempted their unsuccessful landings with only two of three available Raptor engines, Musk frankly stated that “we were too dumb.” At face value, it’s a decent question, given that there are no obvious showstoppers to explain why Starships couldn’t make the most of the redundancy their three Raptor engines can offer.
After completing an otherwise flawless 6.5 minutes launch, ascent, and belly-flop descent, Starship SN9 began a critical ~120-degree flip maneuver, sequentially igniting two Raptor engines and using that thrust to flip from a belly-down attitude to a tail-first landing configuration. Unfortunately, though the first Raptor did fire up and put in a good effort, the second engine failed to ignite, leaving the building-sized rocket to impact the ground traveling far too quickly.
Ironically, more than three years ago, Musk himself revealed in a Reddit Ask Me Anything thread that he and his engineers had decided to modify Starship’s (then known as BFS) design by adding a third Raptor to its central cluster of two engines.
“Btw, we modified the [Starship] design since IAC [2017] to add a third medium-area-ratio Raptor engine partly for that reason (lose only 1/3 thrust in engine out) and allow landings with higher payload mass for the Earth to Earth transport function.”
Elon Musk – Reddit AMA – October 2017
Primarily meant to enable more efficient landings in Earth’s atmosphere, adding a third engine to that cluster would logically increase the chances of a successful (or at least survivable) landing in the event that one engine fails. Greater thrust and an improved thrust-to-weight ratio both during launch and landing would fundamentally improve the efficiency of Starship, likely making up for most or all of the added weight.



In retrospect, it’s not entirely surprising to learn that a three-engine landing burn is probably the most logical option if three landing-class engines have been included in the design. In SpaceX and Musk’s defense, however, there are also several good reasons to use as few Raptor engines as possible.
It was foolish of us not to start 3 engines & immediately shut down 1, as 2 are needed to land— Elon Musk (@elonmusk) February 4, 2021
Throttling high-performance rocket engines is exceptionally difficult and Raptor is not yet a fully mature engine, meaning that it’s throttle capabilities are likely less than optimal. That’s relevant because the higher a rocket’s thrust-to-weight ratio during landing, the more aggressive its landings have to be. SpaceX is apparently extremely conservative with Starship in this regard, prioritizing slow, gentle landings by only using two of three available engines.
Ironically, it’s possible that that attempt at risk reduction resulted in harder landings for both Starship SN8 and SN9, as three-engine landing burns could have potentially slowed them down significantly more before impact.
At the same time, though it may have mitigated the severity of both landing failures, three-engine landing burns would not have resolved the fundamental issues that caused them. In SN8’s case, low fuel header tank pressure doomed the Starship, while SN9 is more ambiguous. Aside from the clear Raptor ignition failure, which a three-engine burn could have resolved by downselecting to two healthier engines, the one Raptor that did ignite appeared to suffer some kind of uncontained failure seconds before landing.
Impressively, despite that apparent combustion chamber or preburner failure, the engine’s landing burn seemed to continued uninterrupted until the moment of impact. As such, it’s hard to say if that lone Raptor was still producing substantial thrust or if it was in the throes of a catastrophic failure. If it could have held on for another 5-10 seconds and the third Raptor (the engine that didn’t reignite) was able to restart and perform without issue, a three-engine landing burn could have easily made SN9’s demise less violent or even have enabled a soft landing.
While a three-engine burn all the way to touchdown appears to be extremely risky or impossible for present-day Starships, Musk implied that there was nothing preventing SpaceX from reigniting all three engines during the initial flip and landing burn and using that time to determine the health of all three engines. If all three were healthy, Starship would shut down one for a soft landing. If one engine failed to restart or lost thrust shortly after ignition, the other two would already be active and able to take over.
Musk says that Starship SN10, already at the launch pad and likely days away from its first tests, will attempt to adopt that approach on an upcoming test flight expected as few as 2-3 weeks from now.
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.
News
Tesla Theater might be getting plenty more streaming platforms
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.
News
Tesla Semi’s biggest adoptee gives an update on production timeline
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.