Why AI Agents Will Demand 1,000x More Compute | Aaron Levie
MTS
October 14, 2026
Box CEO Aaron Levie discusses the massive compute and infrastructure bottlenecks facing the future of AI agents, explaining why enterprise workflows and agent swarms will consume 100x to 1,000x more compute than personal AI assistants. Turn ideas into software people love.
Aaron Levie
The really, really big increase in compute, and by extension, effectively, agentic workflows is going to be when I deploy agents, maybe in swarms, maybe just in background kind of operations at some kind of frequency, to go and do task execution for me, that is again 100% decoupled from my ability to go and kick them off. That's just going to be an incredible amount of compute that is probably 100 or 1000x more than what we're currently consuming in AI at the moment.
SPEAKER_2
Hello everyone and welcome back to MTS. Today, we are joined live with Aaron Levie. He is the co-founder and CEO of Box. And last week, Aaron posted just about how much compute the next era of AI agents are going to require, and what that means for the infrastructure we're building. So Aaron, welcome back to MTS.
Aaron Levie
Hey, good to be here. I want to be thoughtful on the credit. I think I quote tweeted the CEO of Daytona. About some of the trends that we're seeing, which was the math on every personal agent that Muse creates. Basically, you have each user of Muse essentially is running a computer in the cloud.
And so you can start to see, like imagine billions of users of these personal agents, the amount of compute infrastructure that we're going to need.
And that's obviously just one of the many, many use cases we're starting to see. And I think the really, really big use case is actually going to be on the agent swarms and all of the work that those agents are going to do. That's just going to be an incredible amount of compute that is probably 100 or 1000X more than what we're currently consuming in AI at the moment.
SPEAKER_2
Yeah, exactly. I wanted to talk about it.
It was the quote that Ivan posted. He is building Daytona and he specifically said, he calculated that Muse needs around 65,000 CPUs, 775 PB of DRAM to serve 100 million users. And that was the specific thing that you were quote tweeting. You're talking about the magnitude. And this is just Muse. And what you shared is there's going to be a ton of other use cases. Even when it comes to just like the personalized agent side of things, this is relatively new. This all happened within the last few months with like Instinct and Grokbot. Now we have Muse, we have DOTS, we have all these things. What are the other trends you're seeing and why this compute infrastructure is just going to be insane and grow crazily?
Aaron Levie
Yeah. So personal agents, you can just kind of imagine that everybody will have between one and agents just kind of doing useful things for them in the background at almost all times.
That will be a lot of computers to be clear. There's going to be a lot of volume on that, but that will probably cap out at some point on a kind of a per person basis.
Just because there's only so many kind of tasks simultaneously that the average consumer needs. I mean, there's going to be stuff around health care. There'll be stuff around kind of their personal lives, but that somewhat caps out. Where the massive, you know, probably 100X increase in token and compute consumption will ultimately come from is all of the enterprise workflows and enterprise workload. So if you think about it, you know, most work that we do today, even with AI, but certainly pre AI is basically highly dependent on the amount of energy I personally can contribute to a task. My energy in terms of how much I'm thinking about something or researching something or typing something or communicating something to somebody else, that's effectively, you know, all work in the economy is basically rate limited in knowledge work, rate limited by our ability to generate information or move information or produce information. Agents are the first step into kind of, you know, being able to decouple my ability to execute with energy and the ability for just now computers to do work on top of that. But even today, most agents that we're all kind of looking at or thinking about are me sending a task to an agent, that agent basically doing some work, you know, for me to speed up three or five hours worth of work in 10 minutes. But it's usually still rate limited by my ability to give that agent a task. So when you're working with Claude or Chachabi-T, you know, these are obviously still, I'm sort of causing the task to go on and have the agent go work on it. The really, really big increase in compute and by extension, effectively agentic workflows is going to be when I deploy agents, maybe in swarms, maybe just in background kind of operations at some kind of frequency to go and do task execution for me, that is again 100% decoupled from my ability to go and kick them off.
Read the other 18 minutes of this episode here.
$15 gets you this episode and 99 more. Credits never expire. After checkout, one link brings you back here to read it.
Not what you expected? Full refund within 14 days.
Thousands of transcripts fetched by people building searchable podcast archives
Fetch transcripts with code
The same credits work from a script or an AI agent. The demo key returns a sample episode in full, no card needed:
curl -H "x-api-key: pt_demo" \
https://spoken.md/transcripts/1000651996090Markdown with the speakers named, for your notes, your knowledge base, or anything that makes HTTP calls.
From $0.10 per transcript. No subscription. Credits never expire. Prices exclude VAT, added at checkout for EU customers. Not what you expected? Email us within 14 days with 20 or fewer credits used and we refund the pack in full.
Using your own key:
curl -H "x-api-key: YOUR_KEY" \
https://spoken.md/transcripts/1000796296578