Leo Aschenbrenner was absolutely right on the AI trend—the capex data supports his memo—but absolutely wrong on portfolio construction; accumulating high-volatility stocks with forex leverage made his wipeout mathematically inevitable.
Nikesh Arora distinguishes between Aschenbrenner's correct macro thesis on AI capex and his flawed portfolio construction—high-volatility assets stacked with forex leverage that made a wipeout statistically inevitable. ✦ AI generated
Nikesh Arora · 20VC · 2026-08-06 · original ↗
starts at this moment · 25:45
I mean, I think he was absolutely right on the trend. I mean, absolutely right on the trend and remains to date right on the trend. In other words, the data just last week about capex absolutely supports his memo. So conceptually right on the trend and then absolutely wrong on portfolio construction. If you accumulate a portfolio of high volatility stocks with forex leverage, the math makes it clear your probability getting wiped out once is just very high. This is as simple as that. Absolutely right on trend, absolutely wrong on portfolio construction. It's almost like it was inevitable.
verbatim transcript · starts at 25:45
25:37going to be the weakest link when these capabilities are everywhere. >> Yeah, you said it so well, Rory. >> I mean, I'm It just feels so good. I don't mean to be >> I think you should be on the podcast talking about how people need to buy more cyber security. I'm just going to buy the stocks. But >> now Nash, can we get him some swag? I
25:55mean, Jesus, he's a basic give give Nash a hard question. You >> I want to ask Nikesh as my I want to ask him as my cyber security therapist. I had two fable issues and they're internal security, but I'd love to get your and you can make fun of me for this. Like I I've got I pretend to have a thick skin. I don't, but I I I I love
26:13criticism. >> I already figured I don't have a thick skin the first 30 seconds of this conversation. >> Okay, good. So, I'm building an app for the Saster community. It's called Saster Connect to help with recruiting. That details don't really matter, but it's it's the biggest thing I've built, right, myself in this era. And um and I'm among other things, I've got a Google doc. It's called Jason's gems.
26:33It's my ideas on how to improve that. It's just ideas. They're just scratches, okay? No one's seen them. It's not ready. Just a side dock I keep. So, the other day I I went into Claude and I just turned on the Google Drive connector since it's one of the three primary connectors. This is not esoteric. This is not third party. And I never knew. It went in, scanned all my
26:53docs, found Jason's gems, found the ideas. Fable then went and changed my code and my algorithm without telling me. Never got a notice. Never was told. Never was in a change log. Never was anywhere. I only found out later when the agent flashed conflict with Jason's gems when I was trying to fix something else. I mean, I'm not saying it's terrifying, but how can organizations deal with this fact when an LLM will go
27:18out and change your core code, your core corporate OS without even telling you what if you have a thousand employees doing this? And this is goo this is just oh and and the the the hack the part I didn't tell you is the way it did it is it mcped in. So I had I had Google Drive to Claw to Fable to MCP and so it was
- ·Right on the AI trend—conceptually and still today
- ·Last week's capex data absolutely supports his memo
- ·Absolutely right on trend, absolutely wrong on construction
- ·High-volatility stocks with forex leverage
- ·Math makes a single wipeout probability very high
- ·Almost like it was inevitable