AMP

“The value of keeping users on doing the old thing is, is actually negative. I mean, in the past, you would have a five or 10 year technology cycle, and you could acquire a user, and then they'd be with you for 10 years. But now, if you're not nudging them, yan…”

“So, you know, local dev, in our opinion, is dead, and that's been a huge change to, you know, how we all build.”

“On the AMP team, we are 20 people. We are all co-founders.”

“Mandatory code review before it gets to main. Yeah, it's dead. It's been dead ever since we started working on AMP.”

“And that's the kind of thing that means that this transition, I think, is going to go a lot faster than people think. Because if security and devs both benefit from it, then, you know, I don't know, in two months, we could be seeing CLI coding agents as basica…”

“We're not using issues. We're not using pull requests. We're barely on GitHub actions, and we're looking to get off of that.”

“And compared to a few years ago, You do not have the need to go and hire people that you do not trust, that you do not trust to have high agency or the right skills, because you can use an agent to do those things.”

“We will be releasing a lot of these little, you know, jelly ware is what we're calling it. It's like softer than software. But it's not totally vibe coded and you can customize it with your own agent. So we'll get some of that jellyware that we've been buildin…”

“We actually continued, completed our software system, AMP, From, like, start to finish, so anyone can go quote a wire harness to getting it shipped in our end-to-end software system.”

“In order, if you study, like, the history of grids, the most enduring ones were those that never owned their own assets. They were ones that had, ah, already often started with long-term anchors who are uncorrelated sources of demand”

“We pool demand, we pool supply from a number of partners we trust at about 1.3 gigawatt scale over four years.”

“We put a few hundred million dollars into Anthropic from our fund earlier this year.”

“Unfortunately, what's happened the last six weeks. Is, you know, we thought we'd have a bunch of excess capacity by the end of this year. It's all gone.”

“If I'm looking at all my portfolio companies, you know, these clusters are running at like half utilization.”

“In fact, Elon's like got 500,000 GBP hundreds in Memphis. And running an 11% MFU and less than 60% node allocation. I mean, this is twelve billion dollars of compute being wasted.”

“And by the end of this year, I think we'll have, you know, several billion dollars of compute coming online.”

“We have more than 1.3 billion dollars in commits for our first fund. I've been added eight weeks.”

“We put three hundred million dollars into entropic.”

“We need to raise another roughly, you know, six and a half billion dollars this year, and a lot, and more is getting committed by the day.”

“Look, I don't want to get sued by shareholders for whom it's not legible why I'm giving away billions of dollars of compute at cost of portfolio companies, right? Because that's what we're doing.”

“We're actually giving away most of our compute at cost. Now, if you're a shareholder, you'd go, wait on, do you have billions of dollars of compute infrastructure you're giving away at cost? Yes, because we think that's the right thing for humanity.”

“We, we're not a cloud provider. We don't own our own data centers. We're not a traditional venture capital firm either. We see ourselves as an independent system operator, which means our job is to coordinate capacity across the ecosystem in a way that allows …”

“We have started securing about 1.3 gigawatts of computer infrastructure. That's roughly forty billion dollars of cloud spend over the next four years. And that is financed roughly, you know, between with about 20% of equity. The remaining is debt. So 20%, that…”

“Their product has a great reputation of just being, like, you know, punching way above its weight, but I think the other thing that I really respect is that they helped initiate this whole, like, standardization around, like, agents.md and, like, dot agents sl…”

“You know, what's funny is I think they crushed it on AEO answer engine optimization. Because when I was talking to AMP about this, you know, like, hey, I want to send emails, you know, programmatically, it was like, why not resend?”

“I'm actually secretly showing you a new feature. If you see deep here this is a mode. We're actually using a GPT five, two instead of Opus four or five.”

“Now, what I actually do is I actually run three of these agents at a time. So I actually have three amps open any one time, and I'm usually working on three different parts of the app at once.”

“I'm thinking the next step is, is not just to get the email, but actually have AMP implement the suggestion. And then I wake up to a PR that I review where it's actually done the thing that it suggested, and then I get to review that instead.”

“So what I do is I fire up AMP and I basically start talking. I use Whisperflow. Love it. And I basically say, okay, I want to build this feature and this is all the stuff it should do. And I just talk for often like 2:03 minutes.”

“Your agent should be getting smarter every time it makes a mistake. And by updating agents.md, you are going to get that long-term benefit. This isn't just during this iteration. You're going to benefit every time from now on that you use amp or clog code.”

“And what's happening is you're getting a fresh loop every time. So you're getting a brand new thread or a brand new instance of cloud code every time. So you're starting fresh with a brand new context window starting from fresh.”

“Dev browser use this because what this does is this allows AMP or cloud code to actually use your browser and test, and your user stories that involve front-end code remember that the agent needs to be able to test that, and testing browser is hard for agents,…”

“It's growing more than 50% month over month, a lot faster in, you know, some weeks.”

“So we have teams with like two or three people that are on annual run rates of like hundreds of thousands of dollars.”

“It just so happens that we are positive gross margins along the way.”

“So there's a lot of things on AMP that we do, like no consistent pricing, no user model choice, no checking off all the boxes that security and compliance and legal want that, you know, takes nine months. We're able to get away without doing that stuff because…”

“I think we're around eight people now on the AMP core team, and we still don't do formal code reviews. We still push to main. We still ship 15 times every day.”

“We had, like, an internal poll last week at our company meetup where Beyang was asking who of you uses the CLI and who of you uses VS Code, and it was a fifty-fifty split”

“There's absolutely a market today, literally today, someone will pay a monthly fee for that cheaper AI product today. But they're not going to be paying that in six months. It's going to be a different product, or they're going to be paying for something else.”

“And people are now also waking up to the fact that it's not just the model, it's the system prompt, it's the tools, it's the harness. The scaffolding around the model. So I can give you the choice to use Gemini 2.5 in, in AMP, but without the system prompting …”

“So we, in our internal team right now, and this could change. We have about half of our internal team using a different model other than Sonnet as their main way of using AMP.”

“You want to build a scaffolding around the model, a wooden scaffolding that if the model gets better or you have to switch it out, the scaffolding falls away. You know, like the bitter lesson, like embrace that a lot of stuff might fall into the model as soon …”

“So we've had one head to head loss with Amp where we lost against the usual players. And the reason why is one of them discounted their other product a hundred percent for two years. The other one discounted at 85% for two years, which is just crazy.”

“Even with a good agents that MD guidance about how to run tests, I still see with AMP. And I think, you know, we've tried to make this really good. It only gets it right maybe 90, 95% of the time. Sometimes it'll run the wrong testing or it won't escape it cor…”

“And we've had non coders, including one of our board members who built something with AMP that replaced like 250 K a year piece of software that he used for a lot of their internal fund tracking.”

“I think we don't have any set evals. We don't. And this was controversial up until a week ago, I think, when I think Boris from Or two weeks ago from Anthropix that they don't have evals for the coding agent too. But we don't, and we haven't had them.”