News
SpaceX’s response to Crew Dragon explosion unfairly maligned by head of NASA
In a bizarre turn of events, NASA administrator Jim Bridenstine has offered harsh criticism of SpaceX’s response to Crew Dragon’s April 20th explosion, suffered just prior to a static fire test of its eight Super Draco abort engines.
The problem? The NASA administrator’s criticism explicitly contradicts multiple comments made by other NASA officials, the director of the entire Commercial Crew Program, and SpaceX itself. Lest all three of the above sources were either blatant lies or deeply incorrect, it appears that Bridenstine is – intentionally or accidentally – falsely maligning SpaceX and keeping the criticism entirely focused on just one of the two Commercial Crew partners. The reality is that his initial comments were misinterpreted, but an accurate interpretation is just as unflattering.
Stay ahead of the curve and be the first to learn about new industry trends each week!
Follow along as our team gives you their take on the biggest stories of the week.Ultimately, Bridenstine responded to a tweet by Ars Technica’s Eric Berger to correct the record, noting that the criticism was directed at his belief that SpaceX’s “communication with the public was not [good]”, while the company’s post-failure communication with NASA was actually just fine. In fact, according to Commercial Crew Program (CCP) Manager Kathy Lueders, NASA team members were quite literally in the control room during the pre-static fire explosion and the failure investigation began almost instantly.
A blog post and official update published by NASA on May 28th further confirms Lueders’ praise for the immediate SpaceX/NASA response that followed the failure.
“Following the test [failure], NASA and SpaceX immediately executed mishap plans established by the agency and company. SpaceX fully cleared the test site and followed all safety protocols. Early efforts focused on making the site safe, collecting data and developing a timeline of the anomaly, which did not result in any injuries. NASA assisted with the site inspection including the operation of drones and onsite vehicles.”
— NASA, May 28th, 2019
Why, then, are Bridenstine’s comments so bizarre and unfair?
A trip down memory lane
Back in mid-2018, Boeing’s Starliner spacecraft suffered a major setback (albeit not as catastrophic as Crew Dragon’s) when a static fire test ended with a valve failing to close, leaking incredibly toxic hydrazine fuel all over the test stand and throughout the service module that was test-fired. The failure reportedly delayed Boeing’s Starliner program months as a newer service module had to replace the contaminated article that was meant to support a critical 2019 pad-abort test preceding Starliner’s first crew launch.
According to anonymous sources that have spoken with reporters like Eric Berger and NASASpaceflight.com, the anomalous test occurred in late-June 2018, followed by no less than 20-30 days of complete silence from both Boeing and NASA. If Boeing told NASA, NASA certainly didn’t breathe a word of that knowledge to – in Bridenstine’s words – “the public (taxpayers)”. Prior to Mr. Berger breaking the news, Boeing ignored at least one private request for comment for several days before the author gave up and published the article, choosing to trust his source.
After the article was published, Boeing finally provided an official comment vaguely acknowledging the issue.
“We have been conducting a thorough investigation with assistance from our NASA and industry partners. We are confident we found the cause and are moving forward with corrective action. Flight safety and risk mitigation are why we conduct such rigorous testing, and anomalies are a natural part of any test program.”
— Boeing, July 21st, 2018 (T+~30 days)
SpaceX, for reference, offered an official media statement hours after Crew Dragon capsule C201 suffered a major failure during testing, acknowledging that an “anomaly” had occurred and that SpaceX and NASA were already working closely to investigate the accident. Less than two weeks after that, Vice President of Mission Assurance Hans Koenigsmann spent several minutes discussing Crew Dragon’s failure at a press conference, despite the fact that it was off topic in an event meant for a completely different mission (Cargo Dragon CRS-17).
“Earlier today, SpaceX conducted a series of engine tests on a Crew Dragon test vehicle on our test stand at Landing Zone 1 in Cape Canaveral, Florida. The initial tests completed successfully but the final test resulted in an anomaly on the test stand. Ensuring that our systems meet rigorous safety standards and detecting anomalies like this prior to flight are the main reasons why we test. Our teams are investigating and working closely with our NASA partners.”
— SpaceX, April 20th, 2019 (T+several hours)
Within ~40 days, NASA published an official update acknowledging Crew Dragon’s accident and the ongoing mishap investigation. Meanwhile, a full year after Starliner’s own major accident, NASA communications have effectively never once acknowledged it, while Boeing has been almost equally resistant to discussing or even acknowledging the problem and the delays it caused. On May 24th, NASA and Boeing announced that Starliner’s service module had passed important propulsion tests (essentially a repeat of the partially failed test in June 2018) – the anomaly that incurred months of delays and required a retest with a new service section was not mentioned once.
On April 3rd, NASA published a Commercial Crew schedule update that showed Boeing’s orbital Starliner launch debut (Orbital Flight Test, OFT) launching no earlier than August 2019, a delay of 4-5 months. In the article, NASA’s explanation (likely supplied in part by Boeing) bizarrely pointed the finger at ULA and the technicalities of Atlas V launch scheduling.
In other words, NASA somehow managed to completely leave out the fact that Starliner suffered a major failure almost a year prior that likely forced the OFT service section to be redirected to a pad abort test.
Following SpaceX’s anomaly, the company (and NASA, via Kathy Lueders) have been open about the fact that it means the Crew Dragon meant for DM-2 – the first crewed test launch – would have to be redirected to Dragon’s in-flight abort (IFA) test, while the vehicle originally meant to fly the first certified astronaut launch (USCV-1) would be reassigned to DM-2. Thankfully, this practice can be a boon for minimizing delays caused by failures. Oddly, Boeing has not once acknowledged that it was likely forced to do the same thing with Starliner, albeit with the expendable service section instead of the spacecraft’s capsule section.
Again, although the slides of additional CCP presentations from advisory committee meetings have briefly acknowledged Starliner’s failure with vague mentions like “valve design corrective action granted” (Dec. 2018) and “Service Module Hot Fire testing resuming after new valves installed” (May 2019), NASA has yet to acknowledge the Service Module failure and its multi-month schedule impact.
So, if SpaceX’s moderately quiet but otherwise excellent communication of Crew Dragon’s explosion was unsatisfactory and worthy of pointed criticism straight from the head of NASA, the fact that Boeing and NASA have scarcely acknowledged a Starliner anomaly that caused months of delays must be downright infuriating, insulting, and utterly unacceptable. And yet… not one mention during Bridenstine’s bizarre criticism of SpaceX’s supposed communication issues.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
