WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-06-17 1 00:00:04.500 --> 00:00:10.980 SpaceX is buying Cursor for sixty billion dollars in all stock, and it filed the paperwork with the SEC to prove it. 2 00:00:10.980 --> 00:00:15.580 It's Wednesday, June 17, 2026. Here's the rundown. 3 00:00:15.580 --> 00:00:26.100 A rocket company just bought your code editor, a smart bulb is running a banned-book library, and our call goes nine months out on whether Grok eats Cursor's defaults. 4 00:00:26.280 --> 00:00:42.200 SpaceX agreed Tuesday to absorb Anysphere, the maker of Cursor, in an all-stock deal worth about sixty billion dollars. A subsidiary called X67 merges into Cursor, shareholders take Class A stock, and they're targeting the third quarter pending regulators. 5 00:00:42.200 --> 00:00:51.480 The price is the whole story. Cursor raised at twenty-nine billion in November. SpaceX is paying roughly double that seven months later. 6 00:00:51.480 --> 00:01:02.760 Against more than four billion in total annualized revenue, about two and a half of it enterprise. SpaceX had an April option: buy at sixty, or pay ten billion for a partnership. 7 00:01:02.760 --> 00:01:10.040 And it chose to own the layer. That's the tell. They didn't want to rent the surface where developers type, they wanted the margin. 8 00:01:10.040 --> 00:01:17.720 They absorbed xAI in February. Now they pair the most-used coding surface with their own compute and model stack. 9 00:01:17.720 --> 00:01:31.000 Here's the part the headline glosses. Cursor runs on Claude and GPT today. And SpaceX just signed cloud-compute leases with Anthropic and Google worth about twenty-six billion a year combined. 10 00:01:31.000 --> 00:01:34.280 Both with ninety-day termination clauses. 11 00:01:34.280 --> 00:01:45.400 So they're paying rivals to serve inference inside a tool they now own, on contracts they can cancel in a quarter. You don't structure it that way unless you're keeping the option to walk. 12 00:01:45.400 --> 00:01:49.640 If your team standardized on Cursor, what do they do this morning? 13 00:01:49.640 --> 00:02:05.480 Don't panic, but plan. A Grok-first Cursor behaves differently on your codebase than a Claude-backed one. Keep your prompts and agent configs portable, qualify a second editor in your stack, and treat model choice as a setting you control. 14 00:02:05.480 --> 00:02:08.520 And if you're building a coding tool yourself? 15 00:02:08.520 --> 00:02:19.720 The comparable just got expensive, and the distribution moat just got an owner with its own silicon. The signal for the year is compute owners buying the application layer instead of licensing it. 16 00:02:21.350 --> 00:02:26.950 Anyone running a developer product on someone else's models is a target or a reseller. 17 00:02:26.950 --> 00:02:34.550 Right. The margin moves to whoever owns the GPUs and the surface. This deal just drew that line in marker. 18 00:02:34.700 --> 00:02:41.580 Amazon committed multibillion dollars to a new data center in Missouri, another node in the hyperscaler land grab. 19 00:02:41.580 --> 00:02:47.900 The pattern's consistent. Pre-build inference and training footprint in cheaper-power states ahead of demand. 20 00:02:47.900 --> 00:02:50.540 What do you actually watch here? 21 00:02:50.540 --> 00:03:04.460 The megawatt number and the grid-interconnect date. A press release about a building tells you nothing. Power and the interconnect tell you when the capacity comes online, and that's the only date that matters. 22 00:03:05.200 --> 00:03:23.200 Vicki Boykis says local models finally cleared the bar. A gemma-class twenty-six-billion model in LM Studio, on a 2022 M2 Mac with sixty-four gigs, refactored a notebook into a six-module repo, wrote tests, and bootstrapped a recommender. 23 00:03:23.200 --> 00:03:35.440 And she credits tooling and open weights, not size. The HuggingFace use-this-model button, fast prompt-template patches, agents sandboxed in Docker. That's the real shift. 24 00:03:35.440 --> 00:03:39.440 She's explicit it's personal experience, not a benchmark. 25 00:03:39.440 --> 00:03:45.120 So treat it as a threshold report, not a verdict. But the threshold moved, and that one's real. 26 00:03:45.120 --> 00:03:50.960 Anthropic also logged elevated error rates across many models on its status page. 27 00:03:50.960 --> 00:04:02.240 Which is your reminder that single-provider serving is an uptime risk, not just a pricing one. Multi-provider fallback pays for itself the first time a status page goes yellow. 28 00:04:02.240 --> 00:04:08.000 And SubQ published a technical report for its 1.1 Small model. 29 00:04:08.000 --> 00:04:16.080 Worth a skim if you're shopping cheap fast inference. Read it for actual token throughput and context numbers before it goes near your routing table. 30 00:04:17.540 --> 00:04:27.940 ByteDance shipped an agent-native CLI for Lark and Feishu. Two hundred plus commands, twenty-six agent skills, MIT-licensed, installable via npm. 31 00:04:27.940 --> 00:04:40.980 And they deliberately skipped MCP for token-efficient commands with structured output, so agents like Claude Code and Cursor hit higher call-success rates. That's a real design choice, not a press line. 32 00:04:40.980 --> 00:04:45.780 There's an act-as-you mode that touches personal messages, calendar, and docs. 33 00:04:45.780 --> 00:04:54.420 With authorization and review before actions run. Read that checkbox closely before you deploy, because that's a lot of trust to hand an agent. 34 00:04:54.420 --> 00:05:06.420 Two other reads. Gergely Orosz on why Meta is dismantling its engineering org, and a field-notes post using interview questions to surface what people don't understand about Kubernetes. 35 00:05:06.420 --> 00:05:16.340 The Meta piece is a hiring window if you compete for senior talent. The Kubernetes one you can mine straight into a study list. Both links in the briefing. 36 00:05:16.520 --> 00:05:29.400 A developer documents a fake LinkedIn recruiter whose proof-of-concept repo hid a backdoor in an npm prepare script. That runs automatically on install, so just pulling dependencies executes the payload. 37 00:05:29.400 --> 00:05:36.360 And the commits were authored under the stolen identity of a real engineer. The repo's still up after reports. 38 00:05:36.360 --> 00:05:44.680 Here's the detail for builders. A read-only AI code-review agent flagged the payload in seconds, where manual reading missed it. 39 00:05:44.680 --> 00:05:55.560 It was dressed up as sloppy beginner code, which is exactly how you smuggle it past a human. That rhymes with the Lark CLI story, and it's the takeaway for the week. 40 00:05:55.560 --> 00:05:56.600 Say it plainly. 41 00:05:56.600 --> 00:06:11.240 Run untrusted code through a read-only reviewer before npm install, and audit any agent's act-as-you permissions before you grant them. Agents are your best supply-chain defense and your largest new attack surface at the same time. 42 00:06:11.240 --> 00:06:32.040 Two lighter ones. Someone reflashed a four-megabyte ESP32 smart bulb, carved two megs for storage, and served an ebook shelf over an open access point off the bulb. And a researcher shows thin identity checks in a FIFA system could have pushed content during the World Cup with just a document. 43 00:06:32.040 --> 00:06:47.480 The bulb is a genuinely clever offline dead-drop, firmware wipes the Wi-Fi creds so it doesn't leak a home network. The FIFA one is the usual lesson. An identity gate that trusts a document without verifying it is not a gate. 44 00:06:51.520 --> 00:06:54.240 Quick break — two from the desk. 45 00:06:54.240 --> 00:07:08.960 One we know well: vote dot direct. If you're on an H O A or a board, it runs your elections digitally — secure, verifiable, no paper, no clipboard in the lobby. Point your council to vote dot direct. 46 00:07:08.960 --> 00:07:20.240 And if this is your ten minutes of A I for the day, get the written edition too. The full wire, free, every morning — leave your email at nextbig dot dev. 47 00:07:23.470 --> 00:07:29.470 Hacker News is arguing over an April first essay claiming a peopleless economy isn't technically impossible. 48 00:07:29.470 --> 00:07:37.630 Microsoft's x86 emulator team found code so bad they fixed it during emulation. That's a sentence. 49 00:07:37.630 --> 00:07:46.030 Mocha resurfaced on the GitHub feed, and sindresorhus's eslint-plugin-unicorn now ships more than two hundred rules. 50 00:07:46.030 --> 00:07:59.150 Bartosz Ciechanowski's 2022 Mechanical Watch explainer is back at five hundred and two points, and John Carmack posted on Fabrice Bellard, the one-person engine behind QEMU and FFmpeg. 51 00:07:59.150 --> 00:08:10.190 Apple's vehicle motion cues are getting reviewed as a real car-sickness fix, and a two-hundred-nineteen-point post dissects correlated randomness in Slay the Spire 2. 52 00:08:10.370 --> 00:08:22.370 Our call: within nine months SpaceX routes Cursor's default model to Grok and quietly trims at least one of its Anthropic or Google compute leases using those ninety-day clauses. 53 00:08:22.370 --> 00:08:35.970 We're wrong if, by March 17, 2027, Cursor still ships with Claude or GPT as its out-of-the-box default and neither lease has been publicly cut. It settles by March.