Musk v. Altman goes to trial in Oakland



A four-week federal case over OpenAI’s soul, a diary entry, $150 billion in claimed damages, and the question of whether a nonprofit can become the world’s most valuable AI company. 


The years-long legal battle between Elon Musk and Sam Altman over the future of OpenAI moved from social media to a federal courtroom in Oakland, California on Monday, as jury selection began in the US District Court for the Northern District of California. Opening arguments are expected on Tuesday.

The trial, presided over by US District Judge Yvonne Gonzalez Rogers, is scheduled to run for four weeks, through mid-May, with court held Monday through Thursday. The jury’s verdict will be advisory: the ultimate decision on liability and any remedies rests with Judge Gonzalez Rogers herself.

The case centres on Musk’s claim that he co-founded OpenAI in 2015 alongside Altman, Greg Brockman, and others with the explicit understanding that it would remain a nonprofit organisation dedicated to developing artificial general intelligence for the benefit of humanity, and that Altman and Brockman deceived him when they converted OpenAI into a for-profit structure in 2019, thirteen months after Musk left the OpenAI board. Musk’s lawsuit, filed in August 2024, alleges breach of charitable trust, fraud, and that Microsoft aided and abetted the breach.

He is seeking $150 billion in damages from OpenAI and Microsoft, with proceeds directed to OpenAI’s charitable arm; he is also seeking Altman’s removal from both the for-profit entity and the nonprofit board, and an order requiring OpenAI to revert to nonprofit status.

Judge Gonzalez Rogers accelerated the core claims to trial because she concluded there is an important public interest in their swift resolution.

OpenAI’s counter-narrative is pointed and supported by internal documents. The company argues that Musk was not deceived about the for-profit transition, that he was, in fact, actively involved in discussions about it, but that he wanted OpenAI merged with Tesla and wanted to lead the combined entity himself.

When Altman and Brockman declined, OpenAI contends, Musk chose to leave and launch his own AI lab. The most consequential discovered document is a diary entry by Brockman, written in autumn 2017, reading: “This is the only chance we have to get out from Elon. Is he the ‘glorious leader’ that I would pick?”

That entry will be central to both sides’ case: for Musk, it evidences a conspiracy to exclude him; for OpenAI, it evidences that OpenAI’s leadership had legitimate concerns about Musk’s ambitions for control.

The witness list is a who’s-who of the AI era. Both Musk and Altman are expected to testify in person. Microsoft CEO Satya Nadella is also expected to appear, as is Shivon Zilis, a former OpenAI board member who is also the mother of four of Musk’s children.

OpenAI’s lawyers have indicated they will argue that Zilis funnelled information about OpenAI to Musk during the period he was no longer on the board, a claim that, if established, would put the personal and corporate dimensions of the story in the same frame.

Depending on how the plaintiffs sequence their witnesses, Musk could be called to the stand as early as Tuesday.

The pre-trial rulings have gone significantly against Musk. He initially sought more than $100 billion in damages for himself personally; after rulings narrowed the available claims, he abandoned personal damages and now seeks the $150 billion to be paid to OpenAI’s charitable arm.

The judge has ruled that Musk cannot be questioned during the trial about alleged ketamine use, a ruling that limits one line of attack on his credibility, but has allowed questioning about his attendance at the 2017 Burning Man festival and about his relationship with Zilis.

The trial also carries personal exposure for Musk that goes beyond the legal outcome: last month, a separate jury held him liable for defrauding investors during his $44 billion Twitter acquisition in 2022, and any damaging testimony about his business conduct in this trial will surface during SpaceX’s planned IPO this summer.

The stakes for OpenAI are existential in a specific sense. If Judge Gonzalez Rogers finds for Musk and orders OpenAI to unwind its for-profit conversion, the company’s ability to raise capital, pursue its planned IPO at a potential $1 trillion valuation, and operate as a commercial enterprise would be directly threatened.

OpenAI has nearly one billion weekly active users, is valued at $852 billion in its most recent round, and has just closed a $122 billion funding round. Microsoft holds a 27% stake in the public benefit corporation. All of that structure depends on the for-profit conversion that Musk is asking the court to reverse.

The case is also, as NPR’s Casey Newton observed, a clash between “two enormous personalities” whose public feud has been one of the defining dramas of the AI era, from Musk’s $97.4 billion offer to buy OpenAI in February 2025 (Altman countered by offering to buy X for $9.74 billion) to their competing posts on X before the trial began.

“Can’t wait to start the trial,” Musk posted in January.

“Really excited to get Elon under oath in a few months, Christmas in April!” Altman responded in February.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link