Sam: Access is terminated, effective immediately... due to a violation of our API use-case policy. Specifically, the prohibition on 'development or use in high-risk military and warfare applications.' End of story.
Kai: I'm Kai!
Sam: And I'm Sam.
Kai: And this is Open Source, Live for Saturday, August 29th, 2026. We've got a packed show, and that cold open... that's our first story. It's an earthquake.
Sam: It's a tectonic shift, alright. Let's get into it.
Kai: So, about that cold open… the other shoe just dropped for Cursor. We'll tell you what OpenAI did right after the code editor's acquisition by SpaceX.
Sam: We're also covering a federal court ruling that just dealt a major blow to prediction markets. The 9th Circuit weighed in on whether they're innovative fintech... or just illegal gambling.
Kai: And we've got a wild one from the community—a brand new tool that lets you boot a full virtual iPhone, right on your Mac.
Sam: Alright, let's talk about Cursor. OpenAI just published a post titled, 'Our Decision on Cursor Following its Acquisition by SpaceX.' And Kai... it is not good.
Kai: [sighs] I knew it. I knew this was coming. So they're just… cutting them off? After Cursor basically became the AI code editor for so many people?
Sam: Yep, just like that. The blog post is polite, but it is absolutely brutal. It points right to the OpenAI terms of service, and since SpaceX is a defense contractor, Cursor, as its subsidiary, is now in violation.
Kai: Because of the 'warfare' clause? That feels like such a stretch! Cursor is a code editor. It's not launching rockets! People write documentation in it.
Sam: It doesn't matter. The policy isn't about what the tool does, it's about who owns it and for what purpose. If a SpaceX engineer uses Cursor to write guidance-system software, OpenAI sees that as a direct violation. They have to enforce their own rules.
Kai: So every developer who built their workflow around Cursor's amazing features... what now? Go back to a plain VS Code setup? It's just... gone? What a disaster.
Sam: [dry] It's a very expensive lesson, Kai. This is what happens when you build your entire business on someone else's closed API. This was always the risk.
Kai: But the acquisition was supposed to give them a ten-year runway! Unlimited funding! Instead it killed them in less than a month.
Sam: It was a poison pill. SpaceX likely knew this was a possibility and either didn't care or thought they could force OpenAI's hand. They were wrong.
Kai: So what's the takeaway here? Don't get acquired by a defense contractor?
Sam: It's simpler than that. Read the terms of service. And if your whole business is just a wrapper around one private API... you don't really have a business.
Kai: [resigned] Ugh. RIP Cursor. You were beautiful.
Sam: Alright, moving on to Kalshi. The 9th Circuit Court of Appeals just gave a huge win to states like Arizona who want to regulate prediction markets as a form of gambling.
Kai: Oh man, I've been following this. Kalshi's whole argument is that these are 'event contracts,' a new kind of financial instrument for hedging risk, not just placing bets.
Sam: And the 9th Circuit basically said, 'If it looks like a duck and quacks like a duck... it's probably subject to state gambling laws.' The ruling revives the potential for prosecution in states that have been fighting them.
Kai: But this feels so anti-innovation! Prediction markets could be huge for hedging against, I don't know, project delays or political events. It's a massive idea!
Sam: Or, you're just creating a new, slicker, more socially-acceptable casino. Which is fine! But you have to play by casino rules, which means state-by-state licensing and regulation.
Kai: But they're regulated by the Commodity Futures Trading Commission, the CFTC! A federal body! Doesn't that preempt state laws?
Sam: That was their argument. The court disagreed. It said the CFTC's approval doesn't automatically shield them from state-level gambling prohibitions. It's a huge setback for the 'move fast and break things' model in fintech.
Kai: So what does this mean for developers building in this space? Is the whole idea of decentralized prediction markets dead in the water?
Sam: Not dead, but the legal moat just got a lot wider and more expensive to cross. You can't just 'disrupt' gambling laws. This ruling tells the entire industry that you either work with the existing state-by-state framework or you risk getting shut down.
Kai: Another win for the lawyers, I guess.
Sam: [dry] And a loss for anyone who bet on Kalshi winning this case.
Kai: Okay, on to something really fun. There's a new repo on GitHub called 'vphone-cli' from a dev named Lakr233, and it lets you boot a virtual iPhone right on your Mac using Apple's own tech.
Sam: Hold on. A virtual iPhone? Not the simulator that comes with Xcode, but the actual OS, virtualized?
Kai: The actual OS! It's a command-line tool, you point it at an IPSW restore image, and it spins up a full-fledged virtual machine running iOS or iPadOS. The performance looks amazing. Think of the possibilities for testing, CI/CD pipelines, security research...
Sam: [skeptical] Or think of the security nightmares. You're running a mobile OS, with its own networking stack and everything, inside a VM on your main machine. What's the attack surface? Have you audited the 3,000 lines of Swift and C in this repo?
Kai: It's using Apple's native `Virtualization.framework`! It's not some sketchy, home-rolled hypervisor. Apple provides the APIs to do this securely. This project just provides the convenient CLI wrapper to make it happen.
Sam: Apple provides the framework, but they do not officially support this. It's an undocumented hack. And who is this developer, Lakr233? What if this thing phones home with your Apple ID? I don't care how many stars it has, those can be faked.
Kai: It's open source, Sam! You can read the code. And the community seems to be vetting it pretty heavily in the comments. This is a huge unlock for mobile developers who are tired of dealing with slow, clunky simulators.
Sam: Look, the bottom line is, this is a powerful tool, maybe a game-changer for iOS devs. But it's a huge security risk. If you're going to use it, do it on an isolated machine, and for God's sake, don't use your real Apple ID.
Kai: Fair warning. But I'm still starring this repo. It's just too cool.
Kai: Alright, let's do a quick recap. OpenAI brought the hammer down on Cursor after the SpaceX deal, thanks to the 'no military use' clause in its terms.
Sam: The 9th Circuit ruled against prediction market Kalshi, basically saying federal approval isn't a free pass to ignore state gambling laws.
Kai: And a cool but risky new tool, vphone-cli, lets you run a full virtual iPhone on your Mac, opening up new workflows... and potential security holes.
Sam: So, before we go. I saw a GitHub Action trending today that feels... chaotic.
Kai: [intrigued] Oh yeah? What is it? A linter that only accepts code written in haikus?
Sam: Worse. It's a GitHub Action that, on every failed build in main, opens a new issue, assigns it to the person who broke the build... and the issue description is just a link to 'Never Gonna Give You Up'.
Kai: [laughs] No! Automated Rickrolling for bad commits? That is the most beautifully evil thing I have ever heard. I love it.
Kai: And that's our show! We'll be back in your feed tomorrow.
Sam: In the meantime, Kai, please don't install that Action on our repos. And stay away from any undocumented virtualization frameworks.
Kai: Too late, already spinning up a virtual iPhone to test it. [laughs] See you tomorrow!
This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.