Transcript: ‘Microsoft’s AI Vision: An Open Internet Made for Agents’

The transcript of AI & I with Microsoft CTO Kevin Scott is below. Watch on X or YouTube, or listen on Spotify or Apple Podcasts.

Timestamps

1. Introduction: 00:01:44
2. The race to close the “capability overhang”: oo:02:49
3. How agents will evolve into practical, useful tools: 00:04:31
4. The role Kevin sees Microsoft playing in the agent ecosystem: 00:06:48
5. How robust security measures can coexist with open ecosystems: 00:12:05
6. Kevin's philosophy on being a craftsman in the age of agents: 00:15:39
7. How the landscape of software development agents will evolve: 00:20:52
8. The future of agentic workflows: 00:25:33

Transcript

(00:00:00)

Dan Shipper

Kevin, welcome to the show.

Kevin Scott

Thanks for having me.

Dan Shipper

Really excited to have you here. Really excited to be back at Build. One of the things that's interesting is that I was here last year. And you said two things here. There are two big themes. One was that agents are going to be everywhere. That's one of the things you said, which I think really came true. That was very prescient. Another thing is I noticed a big emphasis last year on scaling models. There are a lot of graphs like, we're building big infrastructure, we're building these bigger models, and every two years we're going to get these big performance improvements. This year the emphasis is really on the agent web. So what has changed? What have we learned from last year to this year?

Kevin Scott

Yeah, I think there's a bunch of things that have changed. One of the things is that I think about last year people were really in this state of mind that they were doubting that the scaling laws were going to continue to work really well. Whereas I think we've demonstrated year after year after year that they are intact and working quite well. That's not a thing that people need to be reminded of anymore. And I think the other thing too that's happened honestly is that the reasoning capabilities of the models has actually gotten a little bit ahead of what we're using the models to do in products. So I've been talking a lot lately about this thing called the capability overhang. And I think we actually have some work to do collectively across the whole industry to close the gap between what the models are actually capable of and what we're delivering to users of that capability. So that's one of the big thematic things: why scaling laws might not be as interesting to talk about at this year's Build as last.

And then the other thing too is that. We've just discovered that all of these agents have emerged over the past year. And so both the number of agents and the amount of time that people are spending doing stuff inside of these agents or with these agents is that there's a bunch of other stuff other than reasoning that has to get sorted out in order to make them as useful as they should be. So the things that I was talking about at the keynote today at Build, were we need better agentic memory in our agents right now because memory is constrained in a bunch of interesting ways. They're a little bit transactional, so you use them for like one thing and memory's coherent across the course of that task. But then it may or may not completely go away and you're starting from scratch the next time, which really inhibits your ability to delegate increasingly complicated tasks to these things.

And then there's just this real issue that like, if agents are going to be useful, they have to take action on your behalf. They have to be able to use tools and make changes in systems and consult information sources that are diverse and rich. And in order for that to really be great, you need an ecosystem that looks a lot like the internet, where if you have a source of information, you already have a website, you already have an API that's doing something for people out there. You've gotta figure out how to plumb things through where agents can talk to those things. And where all of the incentives are aligned for everyone to go have all of this stuff participating in ways that make sense to them in this agentic web.

And so I think that is the big story this year. You've seen the first glimmers of like real progress with like super awesome, simple open protocols like MCP that are serving the same purpose in this agentic web as HTTP does on the internet, and where you have things like NLWeb that are serving the same moral equivalent purpose as HTML does on the internet. And so I think you're going to see these things like simple things that are composable and layering and just lots of activity in the open community and a bunch of things, hopefully getting to ubiquity so that agents can actually do stuff right.

Dan Shipper

To play that back, one of the things I hear is, we have agents, agents are starting to work. And in order to make them powerful, agents need access. They need access to whatever is out on the internet, whatever's on your computer, all that kind of stuff. And you need basically protocols. And processes for agents to be able to access that stuff. And so you're looking at different parts of the stack, the runtime layer where you're building memory and all this kind of stuff. And then MCP, which allows you to connect into the internet, into the wider internet to get more information into agents. Why is that important to Microsoft and what role do you want to play in that kind of ecosystem?

Kevin Scott

Well, look, I think there are two, maybe three things that are super important. So one is we make agents and in order for our agents that we're building for folks to be useful, we need to solve these problems inside of these agents. And even if you sort of scope it down narrowly to enterprise agents, one of the things as CTO that I've been pushing for at Microsoft I want all of our systems internally to speak a standard protocol to all of the agents that we're writing inside of Microsoft. So that we are not exposing the entire world to Conway's Law, which is this really funky thing in compilers where this guy Conway said that the number of stages or passes in your compiler is going to be dictated by the number of teams you have working on the compiler.

Dan Shipper

You ship your org chart.

Kevin Scott

Correct. You ship your org chart. And so you certainly inside of the confines of a company like Microsoft, you don't want to be shipping your org chart when you are building your agents. And it's just kind of a horror show to watch as an engineer all of this inefficient building, when you don't have those standard protocols and services that everybody's using.

If you sort of imagine what agents could do and what users like—not me, but just people who are hoping these things can be more useful than they are right now. You need things to start happening the same way that they were happening with the web. And I kind of see it right now. MCP is a really great example. So it is a really simple protocol that solves a really important problem, not just for people who are making agents and building platform infrastructure, but for users of these systems who want them to be more useful. And for people who are providers who are like, hey, I want to be participating in this new agentic web, people are doing less of one thing, which I knew how to connect to and they're sort of sitting here using these agents like, how do I get my stuff wired up into this and how does it make sense for me like even from a business model perspective to do that.

And so like those two things. It's like, make our own agents more useful and then we're a platform company. Even more important than the agents that we're going to write ourselves. That platform layer that Microsoft has been building in technology for 50 years. We just want to make sure that we are helping solve. The problems that are emerging as this agentic web is happening.

Dan Shipper

It's been really cool to see you guys leaning really hard into MCP and integrating it into all Windows and all that kind of stuff. That's really awesome. I’ve been starting to hear rumblings from people who are thinking a lot about MCP that the security model needs a lot of work. And I'm curious, for your take on that, because you're making a lot of comparisons between this stack and the internet stack. And the internet has a bunch of things in its security model—the same origin policy that makes sure that you like it if a website is serving you code, it's only able to execute on its own data. And MCP doesn't really have that. So what do you think the right security model is for this?

Kevin Scott

Well, I don't know that I know what exactly the right security model is. But the interesting thing about MCP is it is so coherently simple that it's going to be relatively easy for the community to decide what the security model is. We have a bunch of enterprise things that we care a lot about and that we're doing really good work with the MCP team to get done. So we need agents to have identities so that you can build entitlement systems so you can say this agent is acting on behalf of this person and they're entitled to see these resources in this system. And even having a way for an agent to sort of query a bunch of systems and say like, here's the thing that I would like to do, these are the systems I need to touch in order to do the thing. What entitlements do I need to ask for in order to do this? And so I can request permission from the user, the person who's delegated this task to me can I present to them, can I have permission to do these things in order to do this thing you asked me to do? Yes or no? And then for the administrators of all of these systems: hey, is it okay for all of this to be happening? And so all of that's going to be relatively straightforward to do. Not easy, but relatively straightforward to do on top of MCP, right? And the important thing is, let's do it in an open way. We don't need it to be proprietary to our agents. We've just gotta figure out how to get this done where things kind of work like the web works.

(00:10:00)

Dan Shipper

Well, it's an interesting question for me because I feel like there's maybe two potential models or potential go to markets for AI stuff that you guys have been talking about. One is this sort of verticalized model where you own the model and you own the UI layer, you do all the applications and everything in between. The thing about that model, which maybe it's sort of— you could say that the App Store or Apple iPhone model is a good example of that—is you can guarantee security in a lot of ways. And an open model it's harder to do security stuff, but you get much more like innovation basically because there's no central authority. So how did you guys think about making that decision?

Kevin Scott

Yeah. So look, I know that's the argument that a lot of people make. I think it might be a false dichotomy. There is a thing that you have in these open systems where they are permissionless. And there's a real advantage in having permissionless innovation. So the thing as an individual that excites me most about what's happening right now is the extent to which you can go innovate and build things without having to seek someone's permission, where you have to have them grant you permission for distributing your things to other people and having all of these complicated gatekeeping things that are sitting in between you, who are the person who had the idea, and the people who might benefit from it. I think some of these middle layers that have emerged over the past handful of years, just aren't contributing much value honestly to the two parties in the transaction that matter, which is the person who did the hard work to make a thing and then the people who are going to either spend their attention or their money or some other currency that's valuable to access the thing. So, I get kind of excited about that. And so that's one of the reasons why we've made the decisions that we want to, but I also think that there are ways that you can get real robust security in these systems leveraging some of the AI capability that you have now that you may be able to have better security.

If you have an agent that you are running that is attending to your personal security requirements. These are things I'm willing to share, these are things I'm not willing to share and that has some kind of knowledge of risk assessment. For instance, my wife this morning while I was, while I was getting ready to jump on stage, I got this flurry of emails that because I'm the backup security account for my wife where like somebody was fiddling around with two-factor authentication on her account and the first thing I did was I texted her. I didn't want to email her because somebody might have gained unauthorized access to her email account. I texted her, I was, hey, are you screwing around with the configuration here? And she's like, yes. And so you could imagine having an agent that is privy to a whole bunch of your communication modalities, being able to notice that something funky is going on and then using a bunch of resources to triangulate whether that's legit activity or illegitimate activity. So I think there's just a bunch of stuff like that, that you can have both, right? I don't think it needs to be like one or the other as you framed it.

Dan Shipper

Yeah, that makes sense. One other thing that I'm curious about is it just seems pretty clear that software engineering is changing. And you're someone who's been involved in software engineering for a long time. You’re someone who also I think cares a lot about the craft of things—the craft of how things are made. We were talking earlier about you doing a lot of ceramics, you make your own bags. You love having your hands in things. And I think one of the knocks on using agents for coding is, it gets rid of some of that feeling or something like that, which I don't necessarily agree with, but I'm sort of curious for you as someone who cares about the craft of code looking into this future of coding with agents. How do you feel about that?

Kevin Scott

Well, so let me start by saying that I love the fact that my people, and when I say my people, I mean makers writ large, so software engineers or mechanical engineers or woodworkers or potters or just sort of pick your thing where people are trying to create things from raw materials or nothing. If you are really passionate about what you do, you're going to have very strong opinions about how you do it. The tools that you use, the materials that you use, how things get put together. It is a necessary thing for you to be great at your job.

The interesting thing is people have lots and lots of different opinions, and like you said, I've been doing it for a long time. I'm an old fart. I wrote my first program. When I was 12, which means I've been programming for 41 years. And so the, the thing that you get to see when you've been doing a thing for a very long time is, this is not the first moment in the past four decades where the nature of software development has changed in a non-trivial way, and where people have very strong opinions about the change and what it means. And so I think the reality is that people will have a choice. I still, when I go into a text editor— I probably shouldn't say this because like we make Visual Studio Code. I'm such an old recalcitrant fart that I still use VI. But my text editor of choice is this extremely antiquated thing and I just refuse to go use something different. Even though I know for sure that is sub-optimizing a part of what I'm doing, I make the decision anyway because I get to choose. And then in other aspects of my making, either software or something else that I'm doing, I will be like, okay, the important thing here is not the way that I'm doing this particular part, it's the outcome that I'm trying to get to. And I'm going to use the most powerful or most convenient way to get to the outcome and I don't care who's going to throw rocks at me for doing it. And it's literally everywhere.

I've been a woodworker for almost as long as I've been a programmer. And when I was a teenager, the big debate was, oh, are you a real woodworker if you use power tools? Real woodworkers only use hand tools. There's still a little bit of that debate today. But the real debate is, are you a real woodworker if you use CNC tools—computer controlled power tools vs. just power tools? And I understand it. I actually think it's interesting the debate itself. But sometimes people are going to make different choices because they value something different than you do. If you value the process more than you value the outcome, sometimes you'll make different decisions and people who value the outcome more than the process.

Dan Shipper

And I think, are you a real woodworker, a real programmer. You're sort of saying you’re only real if you do it the way I grew up doing it, when you ask that question in a lot of ways.

Kevin Scott

But it's just so varied, right? And so, the thing that I will say is, I would never in a million years tell anyone not to have strong opinions about their craft. Have them. It's great. The advice that I would give people and this is not me telling them it's just advice on things that I've found useful for myself is just having an open mind when the tools are changing. I can't even tell you the number of times where I have looked at a new technology in some other, non-software dimension of making that came along where I'm like, ugh. I don't want to learn 3D printers. I waited forever to learn how to use 3D printers and I regret it. I should have started earlier. They’re so damn useful for almost everything that I do. And for a whole variety of complicated reasons. I didn't let myself be curious about that, which is odd. And so just be curious, try stuff like, and if it works for you, use it. And if it doesn't, don't.

Dan Shipper

What do you think is the future of software engineering agents? Is there going to be one agent to rule them all, or is it you're just going to use many different agents with different tastes or how do you see that ecosystem shaping up?

Kevin Scott

I think it's going to be a lot of different agents. I mean, and it's good to have a lot of agents and we certainly work with GitHub Copilot and the GitHub Agent stuff that we're working on. I think we will compete very hard to be a tool that lots of people will choose because it's very useful to them. But I think it's unrealistic in the universe of developers to think that every developer on the planet is going to snap to using one tool for an important part of their job, part of the joy of being a developer is you actually have that choice and you can sort of choose and play around with a bunch of different things and do irrational things and do rational things. And it is one of the very consistent things that I've seen over the past four decades of my programming life is people choose to change their tools all the time.

(00:20:00)

Dan Shipper

What are the dimensions? Do you have an opinion on the dimensions along which the different agents might differ?

Kevin Scott

Well, I think the most important thing about agents is probably the product making part of them. And so the most interesting startups that I'm seeing right now are not trying to innovate by building some kind of differentiated infrastructure. They're innovating because they think they have an understanding of a problem that someone has that is better than anyone else, and they think that they can pick up infrastructure or modify infrastructure, or tune infrastructure to solve their understanding of that problem in a world-class way.

So I think that's what we need a lot of right now and that's what's going to dictate the diversity of agents and which things get used for what. And I think honestly because it's so much easier now to have that nuanced understanding of what someone's problem is and to pick up these tools to go take a swing at solving it that you're just going to have a lot of companies building a lot of things, trying to— You can even see it with the software development tools. It's like crazy how many things have come out over the past year and they're interesting—All of them. It's a lot to respond to when you're a company building software development tools yourself, but it's super, super interesting. And it's what we've seen is if you've got some kind of nuanced understanding of what someone needs, people have high tolerance and high interest in giving things a try.

Dan Shipper

We're almost out of time, but I'm curious. Let's say it's a year from now, we're back at Build. What are some things that are a hot topic right now? Or big questions that people have right now that are not going to matter in a year, and what is going to matter in a year and what are your, and what are your predictions for what we're going to be talking about?

Kevin Scott

I think people who are still hanging onto these ideas that, oh, the technology's not ready yet because I tried to do something and it was marginally too expensive or it was marginally capable of doing the thing that I wanted to do. I think anyone who is using those as excuses to wait to get started is going to be super behind because everything's going to get cheaper and everything's going to get more capable every year. I think this is actually not a hard sell in 2025. It was this loud chorus of like, oh the progress is about to end and everything's going to stop and everybody's going to be super disappointed. I mean, there's still some people out there saying that, but I don't think folks are paying much attention to them anymore mostly because what do you win by paying attention to, some crank who's saying the thing's about to stop you're sort of betting on failure and the cost of betting on failure vs. betting on optimism is a real big difference there.

I think we're going to see a ton of progress on the level of ambition of problems that people are tackling with agents. And then I think modalities that are going to be really different is this agentic web starts to get more complete, more plumbed out and the models’ reasoning and planning capability get better and better, you’re going to start to get to the point where you're able to go from this synchronous mode of interaction with agents to asynchronous.

Right now, most of what people do is, they sort of sit down, they’ve got a thing they want to do, they issue the prompts, and they wait until the thing comes back and do something with that response. And so I think by next year you're going to see people using these agents to, hey, go sort this out and the agent is going to take a lot of time. It's going to make a lot of calls out to systems, the things that it's sort of like taking action on are going to take a while to come back, then they're going to integrate all of those responses and do something and that whole thing may iterate a bunch of times. And then at some non-trivial amount of time later, you're going to sort of say, okay, here's as far as I got. Now it's your turn. Go take some action now.

Dan Shipper

Sounds like a future I want to be in.

Kevin Scott

Yeah. Me too.

Dan Shipper

Right. Well, Kevin, thank you so much. It was really great to talk to you.

Kevin Scott

Yeah, good to talk to you as well. Thank you for having me on.

Thanks to Scott Nover for editorial support.

Dan Shipper is the cofounder and CEO of Every, where he writes the Chain of Thought column and hosts the podcast AI & I. You can follow him on X at @danshipper and on LinkedIn, and Every on X at @every and on LinkedIn.

We also build AI tools for readers like you. Automate repeat writing with Spiral. Organize files automatically with Sparkle. Write something great with Lex. Deliver yourself from email with Cora.

We also do AI training, adoption, and innovation for companies. Work with us to bring AI into your organization.

Get paid for sharing Every with your friends. Join our referral program.