Sundar Pichai on what's next for Google Gemini, Waymo, and data centers in space
59m 9s
Gemini 4 Argon has made a strong impact in early adopter circles, processing nearly 25 trillion tokens in its first 72 hours and demonstrating exceptional performance in agentic tasks, coding, and knowledge work. The model is seen as a significant step forward in frontier AI, with capabilities like autonomously navigating Minecraft showing advanced decision-making. Despite its strength, Google acknowledges ongoing challenges in code quality, hallucinations, and safety, prompting continuous refinement and internal testing. Access is currently gated to premium users due to high compute demands, though more efficient distilled models are being developed to expand availability. Safety is a top priority, with real-time monitoring, sandboxing, and government testing ensuring responsible deployment. Internally, AI is being leveraged not just as a tool but as a co-worker for researchers, improving development cycles through recursive self-improvement. Strategic leadership shifts at DeepMind signal a focus on AI’s real-world applications in science and medicine. Google remains committed to long-term innovation, allocating compute based on demand and future projections, and views AI agents as a unifying, persistent layer across its products to deliver seamless, proactive user experiences. The company also sees transformative potential in space-based data centers and quantum computing, with both areas targeting commercial applications within five years. Despite market volatility and regulatory concerns, Google emphasizes a balanced, forward-looking approach grounded in robust internal signals and long-term industry standards.
Sundar, we're here talking about a week or so after the wider release of Gemini 4 Argon. And I'd love to hear from you what the early reception has been to the new model. Pretty excited. We had been using it internally for a while. It's definitely a well-class frontier model. Nowadays, when you look at the frontier, the breadth and depth of that frontier intelligence is pretty comprehensive. Mentally, we visualize a heat map across agentic tasks, knowledge, work, coding, etc. I think it is very, very strong on many dimensions, and I think it competes very well. The reception has been in the first 72 hours since Argon launched. We've had about almost 25 trillion tokens, which is about 3x what 3.0 had in the first 72 hours. So it's definitely, and we are capacity constrained as we work through this launches. So really good feedback, particularly from our customers, but it's clearly areas to do better. But I think the frontier is constantly your ship, you get feedback, and you're on to the next thing, and it's as dynamic a moment as I've ever seen. Where are the areas that you feel like you want to do better on still? We want to continue on coding. It's a very good model. Our engineers have loved using it internally, but there are areas where we can see we can do better. At any given moment and time and we have shipped, we internally are continuing to make progress on. So you have behavioral refinements based on the feedback you're getting from people using it, so there are areas we're going to do better there. You were mentioning the compute constraints. It's interesting that even a company like Google has those for a new model like this. I mean, Argonne's a large model. It's obviously a very expensive model to serve. Can you walk me through the decision of how you have to now gate this? I believe right now it's accessible through the API, AI Pro, and ultra-subscribers, obviously not to the widest possible user base yet. And I imagine that's challenging for a model of this size. So how do you think through that gating that and releasing it? One of the things we've been very good at if you, you know, if you go back to the three-point or models, we can distill off these models and get versions which are nearly as capable, but much more efficient. So we're working on those models as well, so which will help us give wide access to as many people as possible. So those efforts are underway. We also with this model, you know, we are definitely at a moment as we are working through Frontier, you want to really think about safety of these models. So we've invested a lot more effort, both in terms of how we tested it externally, through our fair and program with the US government giving early access to cyber researchers internally, widely testing it. And we've obviously brought it out externally. You're right, it's a it's a large model. We are serving it pretty fast given the size of the model. So I'm excited what we are doing, but you know, we'll continuously expand access from now on. And so you saw the launch time we had made it available to all ultra-tier protier in the Gemini app. We followed it with protier in the Antigravity app. And we are working on, you know, distilled versions which we can serve to more people with the 4.0 series. Is this the carbon model that there's rumors about? At any given moment in time, we have internal versions of our Frontier models. And so some of these are code names of those versions. That's different from us getting a more efficient version of argon available more broadly. So more efficient version coming. The process of testing it for safety, I'm curious to hear you talk about that. It's interesting to think about how the private Frontier Labs open-and-and-thropic talk about the security and privacy of their new models versus a Google or a meta or, you know, a larger hyper-scaler. It sounds like you guys are being very methodical with the safety testing for this one. And it's maybe taken longer than previous models. Is that fair to say? Definitely. I think with the agentic capabilities and its ability to code so well, particularly when they are deploying it, you know, we are serving many enterprise customers at scale. You want to make sure, so for example, the work we've done, obviously the work you do to align these models well. But more importantly, both the compute and the systems you build to monitor them while they are working, right? And that can be compute intensive too. But that real-time monitoring, as these models are deployed, I think it's being critical so that you can, you know, you get ass early signals as possible if something is not working as intended and you can intervene. So we've taken time to build those systems, the sandboxing you would need to do, the real-time monitoring you would need to do, and with that also for customers giving them the protections they need. So you exactly know where it's running, what access it has, all the telemetry you need, all of that. This interview is presented by HyperAgent, higher AI co-workers that take on real roles, collaborate with your team and help run your business. Learn more at hyperagent.com. Thanks also to Grinola, the AI notepad for people in back-to-back meetings. It works everywhere you do and lets you focus on what matters. Try to Grinola.ai/sources and use the code sources for three months off. This episode is also brought to you by Jira by Atlassian, where teams and agents get the context, coordination, and control to move work forward. Try it free at jira.com. That's j-i-r-a.com. This episode is also brought to you by Mercury, AI native banking that's loved by more than 300,000 entrepreneurs, including me. Visit Mercury.com to learn more. Mercury is a fintech, not a bank. Check the show notes for details. How closely do you follow the rat race of new models? I mean, I'm sure you do, but on X and everything of like, who's up? Who's down? I think you all really had a moment with Gemini 3 last year, where I was like, wow, Google's back at the frontier. I think everyone obviously sees the benchmarks and Argonne is there for sure, but it feels like the energy is constantly moving to who is ahead in the pole position and how much do you focus on that? How much do you encourage your team to focus on that versus not to be curious to hear right now? How you're thinking about it? It's a great question. I think there's so much, it's such a dynamic moment. There's so much noise coming through. I obviously pay attention, I'm on X, I pay attention. It's important to get the pulse externally because you get a sense of where you're doing well where you're not, so I observe all that. Internally, but more importantly, internally, we now have, we have our own e-vals, which are pretty robust to evaluate SSR models. We can see the capability curve there on, so we get very high quality signals internally as well. I think what I encourage the teams is we are very committed to being at the AI frontier for the very long term. We didn't get on this train recently. We've been focused on this for a long time and we want to be at that intelligence frontier a decade from now and so on, so it is doing everything you need to, including safety, by the way. I think that's going to be critical to develop intelligence at the frontier. But I think one of the things for us through this year is we needed to pick up the cadence at which we are shipping things, right? I mean, the industry has been dynamic and the frontier models are evolving pretty fast too. So some of what we have to adapt this year was to make deeper progress on agentic coding, particularly, and then use that to improve our release cycles. We were able to start doing that with 3.5 to 3.6 to 3.7 to 3.8 flash. We kind of, in about three months, went through that sequence. Sequence, and so, obviously, at 4.0, we expect to have improved release cadence as well. There's aspects of Argonne, I'm interested in. One thing I saw was that it beat Minecraft on its own in a little over a day, with I think only less than 2000 in compute, which is pretty impressive. I'm curious with the implications of this level of agentic capability. I mean, in video games, one thing, but you could extrapolate that to potentially a lot of things. That's advanced, decision-making, long horizon task, right? Minecraft. When you see that, what do you think, and how does that impact how you plan ahead? We've had internal versions where, for example, with Argonne, we have seen this, like, step change in internal productivity ever since Argonne has been rolled out internally. A version of internally, there are, for example, there are large code bases on which we have pointed it to, and it's gone. Let's say we've had problems, which we know we need to fix. It's millions of lines of code programming effect. In Chromium, etc. You know, if you want to create an experience where you can drag out a tab, it's moved around, put it in an AI experience. How do you keep it live without reloading? That's the kind of, like, you can get excited about this feature in your head, but historically, for teams, it cuts through all layers of Chromium, right? So, but you can point Argonne at it and it can persistently go and work through it and get it done. So, we're seeing examples like that, like,
that everywhere. So what that excites me is, I think if in some ways I view 2027 as a golden age of that productivity frontier for us because of the new class of models and how well we are integrating it with our internal environments, you can also apply these models to deeply improve model development itself, right, and what we in the industry talk about as recursive self-improvement. So those are all, you know, practically I think areas where you will see continued progress, which is exciting to me. Look, I think what you saw in Minecraft, from now on I think we are, the capability frontier is there where you can in a dedicated way apply assuming you have the compute and resources deeper progress on many areas than we have before. Any verifiable domain really, right? Yeah, and you know, for sure. Even in other years, you can always have humans in the loop to give feedback and keep making progress, right? And so it feels like infinite possibilities. It's one of those moments where you think about, you know, if you can think about a thing, you know, you can apply it and make progress. And you've seen that with mathematics recently, you know, and so things which you would think would take a long time, you can point and put effort into it and show dramatic progress, like OpenAI did with mathematics with their, with the recent models. So I think we're going to see a lot more of that in 2027. Yeah, I've heard Sergei also talking about RSI recently and pushing the teams on that. And I'm curious, like where is Google add on RSI internally? How much of current research and development is, I assume most of it's being assisted by the models, but where are we at on that continuum of the models really pushing? There's a lot of humans in the loop on these things and given the safety aspects of it. But we are definitely at a stage where AI researchers are co-working with the models in a deep way, right? And you know, the models are involved and maybe suggesting recipes automatically evaluating next checkpoints. So there's a healthy amount of models and researchers co-working. There are aspects of the pipeline, which are like probably closer to being like, you know, what I would say in this continuum, more RSI-like, some of them are lesser, but the whole continuum is shifting. So, you know, these are the reasons I think, you know, it's important to think about how we developed the front data as we go through it. But, you know, I would expect the next 12 months to see continued acceleration because of RSI. Quickly, while we're on just the model front here, I was at the last I/O and you guys talked about Gemini 3.5 Pro and there's still some questions out there of like, whatever happened about model, is that, did that just become argon or what happened there? Now, when we were training 3.5 series, we had Flash and Pro, which we were working on. An area where we internalized through the middle of the series that there were gaps in both agentic capabilities, particularly around coding and they are related and how fundamental it is to overall progress. So we wanted to definitely hill climb there and the team felt the fastest way to hill climb was using Flash with a smaller model. It's more efficient, so you can really get a lot more iterative loops there. And so that's what led to 3.5 to 3.6 to 3.7 to 3.8 Flash. By the time we got that done, we had a chance to apply it to Pro, but argon pre-training was done. So it was just realizing that 3.5 Pro would have had a very short shelf life and so we decided to take all the learnings and apply it in argon post-training. And so it was in a constrained environment, if there were things like compute time, etc, you would do all of it. But I think it gave us a chance to kind of skate to where the future needs to be. And so obviously with 4.0 you will have again different model versions in 4.0, argon is our largest model and what we have outside, but we will shift more models there. But we are also making argon available to the Pro tier in the meantime as well. Where is the difficulty still in coding? Where is the area you're still trying to hill climb? It's not that difficulty. It's just the front here is constantly evolving. Right, right. And on every aspect of coding, argon will be the front here if you were to look two months ago, right? So it's not, I wouldn't say it's a difficulty, yes. And you're constantly giving it more complex into an agentic task and you want the model to do incredibly well in a way that you know, world class team programming would accomplish it with good taste, great code, good reliability, it's very safe, etc, etc. So it's just a dynamic frontier. There are times, you know, all our models, you know, for example, take hallucination. It's a, it's a never ending frontier to keep making progress on. It's an inherent part of the current state of the art technology, but you're constantly working to reduce that. So it's both an opportunity and a difficulty to give one example of that. We haven't talked since there were some leadership changes that I wanted to ask you about a Google DeepMind, Demis Asabis, the CEO, stepping back, becoming chief scientist and also focusing more on isomorphic, which I'm very curious about. And then Kaurai, you know, being elevated, running DeepMind, Jeff Dean, Google Legends, leaving to start Discovery Loop. And you know, when that happened, there were, there was a lot of press about that and intrigue about what was going on behind the scenes. I haven't heard you or anyone named there, speak on it since then, so I'd be curious to hear from you. Maybe you can put some of the rumors to rest. What was the thinking there? What motivated that? Why did that happen? You know, you're seeing some natural evolution since people spend their time doing things for a while. Jeff was 27 years, I believe. 27 years. I feel proud of what together with Jeff for a long time, a long time. You know, obviously it was seminal and his contributions here and we are excited to see what he does with Discovery Loop. You know, it would start with saying he definitely wanted a, I think, moment in time where he saw an opportunity to go do something, which he was excited by with a set of people. The change internally, I would just say, you're going through a moment in the industry where the frontier model development is an all-consuming thing, right? You know, you know, we've had broad AI research, AI research and so on, but frontier model development is all-consuming, it's moving, it's picking up pace, right? And it's a very scaled operation all the way from data to compute to the algorithmic work you do to managing the teams and your model agents to do that. So, I think it's become an important job on its whole. Demesis, he's obviously been thinking about this moment for a long time. He's particularly interested in both how do you go through this frontier moment safely? And how do you apply it to solve other problems? It's part of the work that he did with Alpha Fold and hence what we are doing now with Isomorphic are examples of how you can apply you know, AGI to solve other problems. Medicine, drug discovery, yeah, robotics and so on, like, you know, it'll apply to everything. So, I think he wants to spend more of his time. So, he's very leaned in into those things. Which, if you know Demesis, he's always been passionate about that. Passionate about it. And he has been at it early on. And I think in some ways, both seeing that the model development is kind of a well-established process. And Cori has been a deep mind for, you know, well over a decade too. And so, we saw this opportunity for Cori to step up to that. Allows Demesis still involved as chair of deep mind, but he's also spending a lot more time. You've seen him more involved with AI security conversations. But as well as thinking about how to apply AI in a more practical way, be it science, be it healthcare, and there'll be other areas as well. Does this signal any kind of shift with how deep mind relates to the rest of Google? Is it merging and closer? Yeah, what are the natural next order effects of this? There's been an actual process who were many years, including when Demesis was running it, where deep mind, the Gemini app gets built within deep mind, right? So, as an example, Cori had moved here to the Bay Area almost, you know, maybe 18 months ago. Just being close integration makes sense for compute for deep mind impact the rest of the Google. So, there's been deep collaboration which has already been underway a lot. So, I don't think any of this in the continuum wasn't maybe externally people noticed that as a moment. Yeah. But for us, it's been a deep coupling which has been underway for a long time. How do you manage and are managing allocating compute towards long-term research bats, I think what deep mind was historically known for.
kind of preach, IGBT and the current AI boomer-in with the near-term, the frontier models that you talked about, the Gemini app, the products, the commercialization. How do you allocate that? Is that shifted at all in the last year or two? - You know, the problem is always, you know, stakes are high and, you know, and I think we have fortunate to see extraordinary opportunities at being at the frontier of intelligence, having a very successful consumer business across many, many products and services, and being, you know, one of the top cloud hyperscaler companies in the world and the opportunities to provide the technology. So I think the opportunity space is large, and so obviously we have to plan ahead. But I think we have a pretty rigorous approach to plan ahead, you know, these teams plan independently, underlying all of that. We've been AI first company for a long time, and so with that comes in commitment to invest in the compute that you need to be at the frontier, both for research and developing the models. So that is ground zero with which we plan for the future. Beyond that, there are these businesses. For example, Thomas and the cloud team, they have their own long-range plans, you know, with their revenue projections, the opportunities, and they use that to plan compute for them. You can always have moments when you look back in hindsight, I mean, there's no company in the world now sitting here to give you a sense of how fast the technology frontier is moving. Same time last year, this agent, according lift off, hadn't happened. - Yeah. - And remember, we build our own compute, right? And that has long lead times. - Yeah. - So at any given moment in time, you're living with all the compute decisions you made two years ago. - Yeah. - But people are assessing you based on the compute decision, but they have the perfect information today, right? And so-- - You had to make the call two years ago. - Two years ago, and you make the call based on the signals, you know, you're confident, you take a long-term optimistic view and you're aggressive in your investments. - Yeah. - I don't think any company in the world today would sit and tell you, like, you know, today, they got their decision right two years ago. - Right. - And so you're working through those moments, and I think that comes with the territory, comes with the territory. We plan to be state-of-the-art in terms of our compute investments on an ongoing basis to develop, to both drive research and develop frontier models, right? And beyond that, you know, we'll have opportunities to apply it in many other parts. And I think, you know, we plan to do it to the best of our ability. - So that means you're planning right now for 2028, 2029, right? - Yeah, depending on, you know-- - Yeah. - Yeah, if you're planning for land power, - Yeah. - I accept that you're probably in the out three years. - Right. - And there was a big moment over the summer where you all went cash flow negative for the first time since the company IPO'd. And I think a lot of people in Wall Street-- - Free cash flow. - Free cash flow, right? - Yes, of course. And people saw that and go, wow, Google's continuing to invest more aggressively. I think you guided up CapEx for 2027. You're thinking about 2028, 2029. What are you seeing that's giving you the resolve? Especially the moment in the summer where Google goes negative on free cash flow. I assume that was a big decision. And how do you think about that and what is giving you that resolve? - The strength and durability of the demand signals we are seeing. So it's probably, you know, to do something like this, you need to be confident at multiple levels. One is, I think we have fortunate to have early signals from such a diversified opportunity set, right, you know, all the way from consumer to enterprise. And so we are seeing that robust demand signals. - You probably have more signal than any company on ours, actually. - I haven't thought about it that way, but you could arguably make a case for it. And so you have the robust demand signals. We have the demand signal for Google itself, which is a cutting edge enterprise of how we are using AI and adopting it. And you're seeing the capability frontier. Then you're able to independently, outside of the demand signal, in some objective way, actually assess the capability frontier and see how it's progressing, right? And seeing how that curve looks like and beat the scaling laws or like how our new models are doing compared to our old models, the complexity of tasks we are able to tackle our internal e-walls and benchmarks and so on. So you're getting first and sense of it. You're also getting sense of the breakthroughs from research, which give you a sense of, okay, will Gemini F5 point out be much better than were for organists and the answer is a yes, right? So you're getting all those conference signals across that layer of the stack and we also have durable long-term contracts with committed revenue, which we are signing. So it's not just hope, right? You're planning to book of business as well. So you take all that into account and, you know, and you lean in in a responsible discipline bay and which is what you're doing. - It's interesting to hear you talk with confidence about those signals, which obviously I believe. And then I think people are also trying to grapple with, for example, like Corrieve was the latest one that there's fears about the neoclows, there's fears about the financing of these things, the brittleness of it. When you look out there, even beyond Google, but Google's involved in a lot of these things. Do you sense anything that gives you worry about in your term, not even Google specific, but just that the market's maybe over its keys? - Look, I was obviously answering the early question from a Google standpoint, right? Like looking at it, et cetera. - You know, the broader market to me, you have any time you work through these moments where the opportunity is massive and the rewards are high, and you have a lot of players coming in. You are going to have dynamism and volatility associated with that, and I think that is in here and part of a moment like that. This is why I try to focus very hard on that signals, which I have control over, and I can see, right? And the demand signals, the business clear line of sight to the business opportunities we have in terms of contracts, backlogs, and so on. And you plan for that, right? And I think you design the company in a way in which you can work through moments where, even if there's some variation, the long term arc of it is good for the company, right? And so that's why the ability to take a long-term view helps. And even if you look through the last five years, the pandemic drove a big shift towards digital. Then some of it corrected, but it made sense to invest to drive that shift forward for most companies, which did so have done better, right? So you have to understand long-term secular trends and invest to capture the transition. In fact, we invested a lot of our headcount growth as a company through those years was for Google Cloud. And we are benefiting on the other side of having scaled up. We were relatively later to the cloud market, but we took a very aggressive investment posture into that for a period of six to eight years. And that helps us through a moment like that. I think that's how I think about the AI moment as well. Can you look out anywhere in the future and see where you're not compute constrained right now? Is there any moment in time you can look out and see? I hesitate to answer that way because-- Yeah, you got to be careful because everyone will freak out if it's like-- Now, what I mean is it's more that we live in a moment in time in which the global economy is so intermingled in such complex ways. And you can have the butterfly effect of one incident which can have ripple effects everywhere, right? And so I'm trying to decouple two things. I'm not saying, from now on, everything will be a smooth life. It doesn't work that way. You know, economies grow. There are hiccups. You work through. There are business cycles. All that are inevitable parts of how the world works. And I think knowing things, this is like the past bubble. This is not fiber. Yeah. We're using all this. Regardless of what we are super constrained. And more importantly, we're using it for real today in practical value-deriving ways. And we see clear line of sight in which all of this will work better in the future. But that doesn't mean, as a collective industry or an economy you overshoot or you have shocks to the system, which are out of your control and all that. So those are two separate things, right? And which is why part of it is, I focus on the things that are in our control or our ability to take a long-term view, take our years of experience to better forecast, better model, better invest, and apply to this wide opportunity that we have in a pretty disciplined way. And so I put my energy time and attention into that and less thinking about, you know, is there too much exuberance or not. Employ AI staff to run your business with Hyperagent. Agents can find new customers, run campaigns, and handle your business operations. They work in the cloud, collaborate with everyone on your team, and pass work to each other like real co-workers. hire your AI staff.
path at hyperagent.com. I spend a lot of time context switching between meetings. Often with no time to process one before the next starts. Thankfully, Granola runs in the background the whole time. It's an easy to use AI notepad for meetings that works everywhere, even on phone calls. I use Granola to recall what was set in meetings and create helpful summaries. I use it every day to stay on top of what I need to get done with my team. It connects to my email and suggests follow-ups for me to quickly review and send saving me valuable time. Granola isn't just a core part of my workflow. It's basically my second brain. Try Granola at granola.ai/sources and use the promo code sources for three months off. AI is only as useful as the context it has. But when that context is scattered across tools, threads, and DMs, your team and your AI agents are flying blind. That's the problem Jira by Atlassian solves. What's the goal tied to your project? What got decided last week and slack DMs? Atlassian's teamwork graph pulls all of the valuable pieces together from Jira, Confluence, GitHub, Slack, and more. So nothing falls through the cracks. You get 44% more accurate results with 48% less token usage. With Jira, you can easily share your work context with the AI agents you already love, like Claude, Cursor, and GitHub Co-Pilot. Assign them work directly or connect your tools through MCP. All of this lets you spend less time digging through endless links and messages chasing down what got decided and by who and spend more time actually shipping. Learn more at Jira.com, that's J-R-A.com. One of the biggest pains I've had running sources has been managing my books. I'm not an accountant, and all of the software out there is unintuitive, clunky, and detached from where my transactions actually live until now. Mercury recently launched Mercury Books. It's AI powered accounting that works with your Mercury banking and credit card transactions, plus external cards and payroll systems as well. You can choose between cash and a cruel accounting and quickly generate reports for your cash flow, P&L, and balance sheet. Like everything Mercury does, the design of Mercury Books is super approachable and clean. I finally don't feel overwhelmed when I'm trying to understand the big picture of my business. I love that AI does most of the heavy lifting, including for things like auto-categorizing transactions, and that Mercury's command AI agent can handle tasks end to end. You don't need to be paying for separate accounting software anymore, and you can even invite your accountant or CPA to work alongside your Mercury Books with you. This doesn't cost extra, and Mercury will even help you find a human accountant if you need one. Visit mercury.com/books to learn more and apply online in minutes. Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through choice financial group and call them in a, members FDIC. Framer is the AI website builder that powers the sources podcast website at podcast.sources.news. Framer brings AI agents into the same canvas where your website is designed, managed, and published, so you can move faster without giving up your taste or control. I use Framer to make the sources podcast website be the destination for everywhere you can find the show, plus you can also see recent issues of my newsletter. Start building with agents for free today at framer.com/sources for 30% off of Framer Pro annual Plan. Framer.com/sources rules and restrictions may apply. I've heard you say that you would love for AI to help you more with compute allocation inside Google. I'm curious even the last few months. Is it involved at all? Are you finding that you're able to make better decisions or that you would even maybe hand off certain decisions to a model on that? Something as big and important as that? Two ways I would answer the question. One is given the stakes. It's quietly, you know, the decisions of being made by humans in the loop, including me and, you know, directly in wall. But I would say even for me, one of the use cases, you know, I have agents running internally for me in agents I've deployed, both to help me understand, you know, simple thing. It's not super fancy, but, you know, at our scale, even to understand the model development arc. You know, there are all these chat groups, there are pre-training chat groups, mid-training chat groups, you know, post-training data, et cetera. It could easily take me an hour or a day to kind of catch up what's happened in the last 24 hours, right? But now I have agents running with some more eyes and bring that information to me. I can still go deeper and I do so often. Similarly, there are agents with telemetry into our compute usage by product area, efficiency, utilization. And is giving me inputs and insights, you know. So those are the ways we are weaving AI into all this. We have extraordinary people working with all of this as well. I think it's made all of us, you know, be better at what we do. And so that's how I'm using it. >> So no future near-term where AI is making the compute decisions? >> I mean, even five years ago, you know, we used AI to make power consumption efficient in our data centers. So we do have, when we're making compute allocation decisions, AI is a core part of the input it's providing, right? So I'm trying to get you off the hook here now. >> The model set it, not me. >> I think it's a continuum there. By the time it's doing that, you would be applying yourself to the next problem and so on. So that's how I think about it. >> Yeah. I'm curious what you make of this personal agent race that the industry's now in with Muse, which is a great product instinct. I remember at the last I/O you guys showed Gemini Spark. And I'm curious, you know, do you think Google needs to do more here? On consumer, I know you just had the Gemini workspace where you're giving an agent an email or workspace identity, all that. But in the consumer race, when you look at it, it's early, but I imagine you want Google to have even more of us stake in that. >> Well, it's a huge idea focus. In fact, you know, the goal that we set out for Gemini, how we call it, we wanted to be a personal, proactive, and powerful assistant track. So it's a core part of what we are trying to do with Gemini. And you are right in I/O, that's what, you know, it's Spark. I think, you know, that's the direction we are doing. We obviously spoke more about it in our enterprise and in the context of the Gemini agent. To be very clear between enterprise and consumer, it's the same model, same harness, same runtime. It is just a context of what you have in a business or your personal context, you know, is different. And everything we announced in the event, because we're building it for enterprise has world-class security governance. Every task there, you know, we're provisioning, essentially a micro VM to go complete the task, running securely 24/7 with real-time monitoring, et cetera, and providing enterprises with the governance and control and auditability of those agents. We're bringing all that to consumers as well. So, already you saw, you know, you've checked in task now in Gemini, our vision, you know, in the near future is, it's one box and, you know, it's a continuum. What is a chat, what is a task, you know, which of those need to be persistent, which of those need to be scheduled, how does it come back to you? I think we viewed as a natural opportunity. Empirically, when we look at what people are doing in Gemini, if you were to go back and classify it, we see the trend already, right? So the percentage of, if I were to call queries, which are more agentic, has been steadily increasing over time, right? And we're going to make all of that more widely available as we go through the next few months, and we've mainly launched all of this to ultra and pro users. And so we're going to make it more widely available. The newer argon models deliver a huge step change, but you will be able to, again, as a consumer, you know, talk to Gemini, not just in the app, but in the context of like, you know, maybe from Gmail or I can call, you know, so we are focused on it, you know, from search, and we're focused on it in a pretty deep way. Yeah, a thing I've been dying to ask you, especially with your experience, you know, running Chrome before, like, the moment we're in, all these agents are using browsers like humans to complete tasks. I mean, with Muse, you can literally see, right? And, you know, it feels when I look at it, I get why it's happening, you want to get the task done, and that's the way to do it. But it feels like trying to fit a triangle into a square. It doesn't feel quite right. And to me, it's making me go, does the web need to fundamentally change for these agents? And I know there's protocols you guys have worked on them, there's others, but I feel like Google's uniquely positioned to do something here bigger. And I'm curious if you've been thinking about that. No, you know, deeply, you are right. Look, it's a complex moment because, you know, when we say agents working at scale, that means many, many different parts of the economy are operating with each other in some way. In a way that has to make sense for all the players involved. Right. And I think the technology frontier will be ahead of the ecosystem, how it comes to work together in this case. I definitely think a big part of this is why there's means a lot of momentum behind MCP or agent protocols or payment protocols, like what we did with UCP, along with a set of companies. And there's going to be a chaotic evolution there. Hopefully working towards
more interoperable standards. Right? And I think that's a very elegant way to do it. Browse using computer uses a very elegant way to work too because that's what a user would do. And it allows you to efficiently build controls for the users to be in the loop as well. So I think you have both ways and they're going to develop. But there are moments where anytime I think if you solve it with better protocols, you know, I think it's a far more scalable approach and it'll work anywhere and instantly. So I think but that will take longer time. Yeah. How do you think about protecting the interface in the way that you need to in this agent world, right? There's an argument to made. There's a new kind of agentic Google search that could be invented now. Agents don't need you. Amazon is blocked. Muse, for example, you have a very large ads business that requires engagement. So what do agents do to those kinds of interfaces? How do you protect or not from that? The right answer, longer term, is you put users first and say what would users want? And you want to try your best to be aligned in that direction, work towards that direction, right? And I think I think that's what will drive these experiences. But ultimately it has to work for all the businesses who are providing value to. So at any given point, you're going to reach equilibrium and that equilibrium will shift. There'll be new players who view each of these moments as disruptive ways to do things differently. Like when the internet came, you know, you would sit and think, shouldn't the way real estate works? How people buy and sell houses overnight transform, right? But you know, it's kind of played out not quite what people thought it would happen that way, right? And I would argue, even today, most of it happens, the way it used to happen, like, you know, 20 years ago. So there are real constraints in the real world. I think AI agents and AI are even more, they will be even more disruptive, but, you know, there'll be micro-equilibrium, which will emerge. For me, from our standpoint, I think you embrace the innovation. You kind of put yourself in the shoes of users and you try to innovate in that direction. That's how I would approach our product development. So I think that's what users would demand. I've talked to Liz and some of your other colleagues over the last year or so about this idea of when to Google search AI overviews and Gemini fully merge, if ever. Because right now you've got these two large-scaled, you know, AI products, Gemini doing users search billions of users, but relative, you know, different, but overlapping in some cases, AI experiences. Do you ever see them fully combining? Okay, here's an example, right? Like when we ship personal intelligence, they work. I mean, you can turn on personal intelligence both in Gemini and in search, and it has a context. And so kind of works in a unified way. I expect our agents to provide that unifying experience across these products. In fact, that agentic layer, rather than try to converge or, you know, think about different products and how they come together, I think the agentic layer naturally ends up doing that, right? So because your agents, they're running in the cloud, they're running 24/7, they have your context, and so they can pick up things where you left off. Right? So you can start a task in some place. You go to the other place, your agent has that context for you. So I think the agentic layer offers us a chance to bring a unified product experience better than ever before. So that's how I try to think about it. You guys are also starting to send data centers to space. You've got very early, you've got projects on catcher, your first pilot with Planet Labs and SpaceX. How's it been going? I mean, they went up. Is it still there? Is it burned up? What's been the early feedback? It's been doing great. I think it's still there. It's doing well and we are, I think, we'll get a chance to say hello to the TPUs, but, you know, which I'm really excited by. I had a chance to watch the launch here while it was happening. Look, I think when we take these projects to me, it's no different from starting VAMO. I still recall flying to the desert to watch the Stanley car race as part of the DARPA challenge. And at that time, if you tried to envision where VAMO would be today, you know, it would seem like, you know, you're talking about something futuristic sci-fi thing, right? But, you know, 10 to 20 years is a long time, particularly the, with the, with the inflection points we are in. So I think we are taking the early steps, but we are deeply committed to the journey, and the team is a world-class team, and, you know, in a 10 to 20 year time frame, they're going to have amazing milestones. So that's what I'm excited about. What about like the desert, the ocean, all these places on planet Earth, where we could put them now? I mean, why, why, why invest in space right now? If you think through from a first principle standpoint of energy availability, you know, being in sun, sun synchronous orbits, getting access to 24/7 energy, kind of, it's a pretty good reason. There'll be more reasons, you know, I think we love so many opportunities to use the physical space, the constrained physical space on planet Earth. The data centers today look big to us, but they are, they are not. It's just arbitrarily big to how they were like 10 years ago. So it is tough for us to exponentially extrapolate our, our compute needs 20 years out. And so I don't think it Earth would look nice if that's how you plan to do it. Yeah, it's a good point. Yeah, and so, and we would have other constraints here, and so on. But also by thinking about these technologies, it's like in the 60s going to the moon, going to space, you're pushing so many aspects of the technology curve. That's how you drive R&D, that's how you drive the future. So there will be, you know, it's the fundamental thing about a moonshot you realize is when you focus on something very ambitious, you invent so many things along the way, all of which end up being helpful. Which you found with Waymo and. Waymo, our GPUs and, you know, because we were trying to build AI so early, and the compute wasn't there, it's what led us to build TPUs. And so, and I think so, thinking about a technology curve early and pushing, I think definitely gives you those opportunities. And you said the word moonshot a couple times. It's literally a moonshot, but is this, I saw that in the release too for it, is this the next Waymo in that sense? Is this the next alphabet? Spend off kind of new company? Suncatcher? You know, we are definitely in a computer so integrated to what we do as AI, you know, we even thought through the struck me, I viewed as our, the future way we will scale up compute, in a pretty fundamental way. And so, but it's definitely a moonshot and, you know, and, and what we are committed to doing that well. I would love to hear the strategy for Waymo, because I can see it going a lot of directions. And I'm curious, do you want to keep having these partnerships with the Ubers, etc. Or will it be the fully, you know, vertically integrated Waymo fleet? That's one phase of it. And then I have a question about just, you know, selling Waymo vehicles directly to consumers. I'm curious if you've, what those two buckets can Waymo and Uber coexist? And then could I just buy a Waymo car one day and maybe rent it out myself? It's an area where we are so, so far from a zero-sum construct. I think like, you know, it's just like, it's so early. The opportunity space seems so vast to me, so many applications for autonomous driver technology. I expect Waymo to work in a myriad of ways, including with other partners. I expect the other partners to do very well as, as companies on their own too. So, all of that and very, very bullish on. The Waymo team, you know, they're very, very focused on scaling up what they are doing. We just crossed half an million paid rights per week and, you know, we are, so the team is raised focused on scaling that up. Toronto launch is coming. Yeah, we can new cities this year, right. And so it's an operationally, logistically scaling up the vehicles, scaling up in more environments, scaling up the customer service, the operations, all with safety being a number one priority. And I think that is what the next 12 months is going to be more of it, international, other weather conditions, highways, and everywhere scaling up with this high safety bar we have, right, already driving with 95% viewers. He is crashes, compared to, you know, regular driving. And so that to me is where, through all the underlying technology we are building is so general, it has all the option values you're talking about built on top of it. I think everyone is like wondering where you're going to take that option value. Some people are scared because they have businesses to protect and others are just going, wow, what is the expansion? And I would, I would just argue historically if you looked at that,
as a company, I think you looked as build Android, mobile. Even in the AI ecosystem, we partner with a wide variety of companies. So I think we will always work with the ecosystem, and I think there'll be plenty of growth for everyone to do well. - Will I ever be able to buy a WAMO car myself, though? - It's not what we are working on at this moment, but never say, never say never, never say never. - What about wing? This is one of your other best that's really maturing and I've heard you say maybe 40 million American households while the access to wing and the not-too-distant futures has drone delivery. - Yeah. What do you imagine that's going to unlock? - I just spent time with a wonderful wing team on Friday, Friday evening, so it was my last meeting of the day. So, look, I'm very excited because they have a product which I think is very good. Early on, they've made the bet to design a lightweight product which is easy to make and easy to deploy, and you can scale it. - Yeah. - So I think so they've got on the primitive stride. I think they have ambitious expansion plans too, so I would expect us to meaningfully increase the scale of deliveries in 27, and also bring it to newer categories than where we do today, right? So those are the growth opportunities. - And this is similar to Waymo through a partnership's lead approach. - Yeah, that's how we will approach in 27. - Yeah. Okay, you've been spending a lot of time in D.C. recently, have noticed, and I haven't heard you recently talk about how you're feeling about the state of policy making. Demis is obviously laid out his proposal for this kind of fin-restile body, which I think got a lot of interest, and I'm sure you're aligned with that in a lot of ways, but I'd be curious, especially the time you've been spending recently, and you signed the thing that the White House did with all the other tech CEOs. What would you like to see happen? It feels like we're in this moment where everyone's trying to create the framework to support regulation. - It is such a consequential technology, with so many implications, including extraordinary opportunity to make society better, the economy is better, et cetera. I think we are in a phase right now where there is growing realization about how powerful this technology is, and that the companies which are at the forefront of this technology needing to operate with the right kind of safeguards and approaches so that we deploy this technology as safely as possible. So that's how I would capture the current moment. You, for us as a company, this is so cool to how we want to think and operate. We've done that for a long time. That's what we're doing with the argon launch as well. So in some ways, that's what the current moment is. I think the next step is the more we can all standardize our testing approaches with better e-vows, better standards. I think that will help us assess the frontier much more effectively. If you look at the financial world of financial statements that are clear standards, accounting standards, you operate too, there are well defined independent evaluators who do those things like the professional audit firms. I think so, those are all good, good directions for us to evolve to. There will be a time we will need to do more. I think it's, but it's important to get it right. I think the technology is so dynamic. One of the challenges here is anything you do might be too inadequate or just wrong 12 months from now. So I think building the competency creating industry standards groups are all good ways to make progress. So that's where at least I'm spending a lot of my time and effort on is as Google are we meaningfully increasing the level of investments, the bar at which we are safely developing and deploying these models? I think companies which do that well will have a competitive advantage in the future. Right, so that's the way I think about it and so that's very a lot of my energy in it. - Well, it's interesting, you know, we started this with you talking about how you guys have intentionally kind of of your own accord been more slow in the release of Argonne and testing it internally. It was your widest internal test ever. The government review all these things. And yet people are saying the government should mandate maybe a slow down. And it sounds like market incentives are maybe working already based on what you're telling me of how you guys are working. - I get nervous about these things. I get nervous about startups. Giving startups room to still grow, regulatory capture, these kinds of things. So I'm curious how you balance, you know, needing some regulation with that. - Look, in all scenarios, the main thing I would advocate is a more uniform regulation than a patchwork of state-by-state regulations. I think that really can set the industry back and actually make it inherently unsafer because it's a more complicated frontier to work through. I feel very confident in our ability to adapt to ongoing developments in this space. Already one way you can think of all of us now, if you're developing a model at the front here, even though it's voluntary, we are submitting our models to the US government for testing, right? So that's a change from a year ago. Whether it's codified as regulation or not, you have these developments which have happened. So I think it'll be an ongoing area where we are evolving based on what we are observing. And I think you want to anticipate. But I think it's important for a technology which has so much potential to make sure we are at the frontier as well as for us, for me as a company, for us as a country and so on. - I don't understand quantum, to be honest. I know you guys have a deep bat here. And quantum feels like this thing that exists kind of in a layer above everything we've been talking about that could influence a lot of things. It's a hard question, but I'd be curious to hear you share what you think the opportunity of quantum actually is because it sounds like I've been seeing you post, you know, you guys are making some progress here. And when you look at it, like when it hits, what do you think will happen? - Last of all, welcome to the club and you say you don't understand quantum. - Okay. - You're joining each and every one of us. - Okay, I think it's good to hear. - It's a technology, the more you spend with it, some ways you understand it less, right? And I think even more so I think quantum is an area where we have clearly we had set internal milestones. And the team is tracking or exceeding to those milestones over almost now a 10 year timeframe. And in terms of robustly scaling up quantum systems with the view towards commercial applications, right? The future possibilities of quantum are both vast in some ways uncertain, et cetera, but I genuinely see practical commercial applications in a five year timeframe, which we would get excited by. You know, we would be, today like we provide TPU pods, you know, if I were sitting in a chair five years out, our Google Cloud team would be negotiating deals on quantum deployments at some scale, right? And so it is incredibly exciting to me. And it's another technology we've been committed to for a long time and you'll continue to see us be committed and be at the front here. - Sundar, thank you. - All right, Alex, real pressure. Thank you. - This interview is presented by HyperAgent, higher AI co-workers that take on real roles, collaborate with your team and help run your business. - Framer is the AI native website builder that lets you build faster without giving up control. Visit framer.com/sources for 30% off. Rules and restrictions may apply. Grinola is the best AI notepad I've tried. It works everywhere on a video or phone call in person or an Apple Watch. Try it now at grinola.ai/sources and use the promo code sources at checkout for three months off. GiroBio ad lasing is where your team and your agents work from the same context. Try it free at giro.com. That's j-i-r-a.com. Banking should feel like modern software. Get everything you need in one place. Visit mercury.com to learn more and apply online in minutes. Mercury's a fintech, not a bank. [BLANK_AUDIO]
Podcast Summary
Key Points:
Gemini 4 Argon has received strong early feedback, with 25 trillion tokens processed in the first 72 hours—about three times more than Gemini 3.0’s initial volume—showing significant user engagement and performance across agentic tasks, coding, and knowledge work.
While Argon excels in frontier capabilities, especially in agentic coding and long-horizon decision-making (e.g., beating Minecraft with minimal compute), ongoing refinement is focused on reducing hallucinations, improving code quality, and enhancing safety and reliability.
Google is implementing a phased release strategy, initially limiting access to API, AI Pro, and ultra-subscribers due to high compute costs, while developing more efficient, distilled models to broaden accessibility.
Safety and monitoring are prioritized through rigorous internal testing, real-time telemetry, sandboxing, and government collaboration, with efforts to build robust, auditable systems for enterprise deployment.
The company is deeply committed to long-term AI frontier development, with internal progress on recursive self-improvement (RSI), where AI researchers co-work with models to iteratively improve performance.
Leadership shifts at DeepMind (e.g., Demis Hassabis stepping back to focus on AI applications in science and medicine) reflect a strategic pivot toward practical AI use while maintaining core research integrity.
Compute allocation remains a long-term strategic decision, guided by demand signals, internal benchmarks, and future projections, with AI agents already used to monitor and summarize operations and compute efficiency.
Google sees AI agents as a unifying layer across products like Gemini and search, enabling persistent, contextual task execution, and believes this will drive a more integrated, proactive user experience.
Summary:
Gemini 4 Argon has made a strong impact in early adopter circles, processing nearly 25 trillion tokens in its first 72 hours and demonstrating exceptional performance in agentic tasks, coding, and knowledge work. The model is seen as a significant step forward in frontier AI, with capabilities like autonomously navigating Minecraft showing advanced decision-making. Despite its strength, Google acknowledges ongoing challenges in code quality, hallucinations, and safety, prompting continuous refinement and internal testing.
Access is currently gated to premium users due to high compute demands, though more efficient distilled models are being developed to expand availability. Safety is a top priority, with real-time monitoring, sandboxing, and government testing ensuring responsible deployment. Internally, AI is being leveraged not just as a tool but as a co-worker for researchers, improving development cycles through recursive self-improvement.
Strategic leadership shifts at DeepMind signal a focus on AI’s real-world applications in science and medicine. Google remains committed to long-term innovation, allocating compute based on demand and future projections, and views AI agents as a unifying, persistent layer across its products to deliver seamless, proactive user experiences. The company also sees transformative potential in space-based data centers and quantum computing, with both areas targeting commercial applications within five years.
Despite market volatility and regulatory concerns, Google emphasizes a balanced, forward-looking approach grounded in robust internal signals and long-term industry standards.
FAQs
The model is strong across agentic tasks, coding, and knowledge work. Early feedback highlights its competitive performance in complex, real-world scenarios, with significant improvements in internal productivity and task completion.
Google is gating access to Argon through APIs, AI Pro, and ultra-tier subscriptions due to high compute costs. They are also developing more efficient, distilled versions of the model to expand access and reduce resource demands.
Google is continuously refining Argon’s coding capabilities, focusing on real-world agentic tasks that require world-class programming quality, reliability, and safety. These are seen as dynamic frontiers where progress is ongoing.
Google has invested heavily in real-time monitoring, sandboxing, and telemetry to ensure safety. These systems allow for early detection of issues and provide customers with transparency on model behavior and access.
Yes, there are internal code names for versions of the Frontier models, including one referred to as a 'carbon model.' However, this is not a publicly released or widely available model; Google is focusing on efficient, accessible versions for broader use.
Google plans to release more efficient, distilled versions of Argon to wider audiences, while maintaining high-quality core capabilities. This will allow broader access without compromising performance or safety.
Chat with AI
Loading...
Pro features
Go deeper with this episode
Unlock creator-grade tools that turn any transcript into show notes and subtitle files.