
OpenAI Podcast · 2025-11-13
ChatGPT Atlas and the Next Era of Web Browsing
Hosts: Andrew Main
Guests: Ben Goodger, Darin Fisher
Why it matters
Chromium was chosen for web compatibility and extension support.
Key claims
- ChatGPT Atlas is built with ChatGPT at the core of the browser, not as an extension, enabling deeply integrated features like personalized writing and browser memories.
- Agent mode features a separate workspace of tabs isolated from the user's tabs, allowing parallel agent tasks without UI clutter.
- The architecture uses an out-of-process Chromium embedding called 'OWL', with Atlas itself built as a lightweight native Swift application, enabling fast restarts and process isolation.
- A 'sensitive mode' keeps users engaged during agent actions on sensitive sites, with a prominent stop button and optional signed-out execution.
Episode summary
Summary
This episode features OpenAI's Ben Goodger and Darin Fisher discussing the launch of ChatGPT Atlas, OpenAI's AI-native web browser. The team explains why OpenAI decided to build a browser rather than just a Chrome extension: integrating ChatGPT at the core of the browser enables deeply woven features like personalized writing assistance in any text field, browser memories that recall past activity, and an agent mode that can autonomously operate on websites. They emphasize that Atlas represents a long-term investment and is positioned as a foundational evolution of the browser, not a short-term experiment.
- ChatGPT Atlas is built with ChatGPT at the core of the browser, not as an extension, enabling deeply integrated features like personalized writing and browser memories.
- Agent mode features a separate workspace of tabs isolated from the user's tabs, allowing parallel agent tasks without UI clutter.
- The architecture uses an out-of-process Chromium embedding called 'OWL', with Atlas itself built as a lightweight native Swift application, enabling fast restarts and process isolation.
- A 'sensitive mode' keeps users engaged during agent actions on sensitive sites, with a prominent stop button and optional signed-out execution.
- Chromium was chosen for web compatibility and extension support; the team acknowledged they explored using a new rendering engine but prioritized compatibility.
- Windows version is in development using Swift, and mobile is being researched with focus on information retrieval and continued cross-device workflows.
- The team frames Atlas as a long-term investment (compared to 'Netscape 1.0' of the AI browser era) with significant features still to come.
- Future vision: agents handle 'toil' work while users focus on high-level decisions, with a significant share of internet traffic potentially becoming agent-driven.
Source material
Transcript
Hello, I'm Andrew Main and welcome to the OpenAI Podcast.
There have been a lot of exciting releases from OpenAI recently, including GPT 5.1, Sora, and one of my favorite new applications, ChatGPT Atlas.
Today we're going to be talking to the team behind it, Ben Goodger and Darin Fisher, and explore some of the reasons for why OpenAI decided to make a browser, what the future of agentic capabilities mean, and where everything's headed next.
Time is right because it's actually how people should be starting their journey.
We're moving to a world where you can just tell the computer what you want.
So I think it's kind of powerful, this idea that the agent has its own workspace.
My view for this has always been that this is like a long-term investment.
Let's begin with what is Atlas and why?
So Atlas is a new kind of browser for an era of the web where people are interacting with new technology in natural language.
It's the kind of browser where you can just tell it what you want, whether it's to find the next outfit that you're going to buy or to help you solve a really hard problem.
Then it can help you harness the web to get a bunch of stuff done.
Central to this idea is that if we take chat TPT and make it the heart of your browser, not just an add-on, it's something that can actually help you make sense of the content that you're seeing on the web.
It's something that can help you take action on the web.
It's something that can learn from your browsing to personalize your experience and help you with tasks that aren't just done in a few minutes, but might take days or weeks or months or just generally help you become a more curious, more effective person.
And it can help you come back to a task that maybe you've not had a chance to work on in a while because it will remember what you were doing for you and help you get right back into where you were.
Why now?
I think the progression of technology with these AI models has been really stunning to watch over the past couple of years.
It feels like we're at this sort of sweet spot where the capabilities of not just the LLMs that have powered chat TPT, but also this new area of computer use and some of the other surrounding technology is at a point where we can build some really compelling experiences for people.
So we wanted to give it a shot.
Like Ben said, the models have gotten so much better and they continue to get better.
And you see the slope of innovation there and the pace of improvement.
If you look back at the beginning of the year when Operator first came out, for example, and it hints at some of the potential.
And now you fast forward to where Atlas is with agent and how much faster it is, how much more capable it is.
Just look at that slope and you start to project what's it going to look like next year, five years out, et cetera.
And to get that foundation in place, that's what we were excited about.
And it felt like the right time for me personally, I felt like I had made that transition to seeing how chat TPT makes so much sense in my life and how much I was using it and feeling like I'm putting chat TPT at the core of a browser, not just another tab that you have to go to, but to have it be at the core and part of that flow.
Time is right because it's actually how people should be starting their journey.
And so we want to make that just so natural and easy.
And so I'm really excited that we've been able to bring Atlas up and I'm excited to bring it to more platforms.
You too have quite a bit of history working in browsers.
Netscape, you've worked on Firefox and Chrome.
And I'd like to kind of understand where you think we are right now with browsers.
We've got like over 30 year history of these and now it seems like they've been changing a little bit incrementally and then all of a sudden now we're adding AI to it, et cetera.
And how do you look at the browser landscape?
Well, I think we have entered this really exciting time on the web where we've added this very human form of interaction in the form of these large language models that you can just speak to the software and have it do the right thing for you.
And so I think that's really going to transform the way people get stuff done online.
We've gone from a world where you've had to remember website addresses, you've had to go and search for them and now you're just going to be able to ask for the tasks that you want to get done and you're going to see it get done.
I've noticed that a lot of people were thinking like, well, we still have browsers.
That was a question.
Are we going to have browsers?
And it seems like browsers are going to be here to stay for a while.
Is that something you both feel?
It's a tool that people reach for a lot and get a lot of things done on the web and using a browser.
It's hard to imagine that not being a big part of how people use their computers.
We've been through many phases of the internet and many phases of browser development.
There was a time when here comes mobile.
Why would anybody use their laptop anymore?
Why would anybody use a desktop computer?
And yet people continue to use desktop computers.
They reach for it for very different things maybe.
And now that they can also reach for their phone for certain things.
But the web browser continues to be like such an important tool on your computer for how you get work done, how you do research tasks, how you look for information and do that kind of work.
Substantive work happens within the browser, happens on the web.
Don't really see that changing.
If anything, I see that growing because it's just like conduit to all the world's information.
It's such an easy platform for people to bring experiences and make it available to everybody.
The browser just makes that so easy.
There's something sort of interesting about it where all of the technological advancements that we've had over the past 25-30 years with the web, there's something very durable about the browser.
Even if you look at this most recent wave of generative AI with chat GPT launching, it launched on the web.
It's a very powerful reflection of the capabilities of this platform.
And the platform itself is amazing.
I don't really need to recount all of the ways it's amazing, but the fact that it's this very inherently open platform, content is published to an open platform, an open internet where anybody can stand up a browser to consume that content.
There are real no gatekeepers when it comes to the web, which is a really remarkable aspect to it.
People can freely publish information and people can freely go and find that information.
It allows it to just blossom and grow and evolve in different ways.
Then it's very natural that you might want to take something like an LLM and point it at it, because now it can on your behalf try to understand it and help you navigate it.
The idea that it can do all that means it just makes it so much easier when you're trying to take advantage of all that information that's out there as a user.
There it is.
It can go and find it for you or understand it for you or explain it to you.
I just want to say, I think it's been really interesting to see the evolution of the web.
We got started in an era where it was coming off of the dot-com boom.
The needs of the browser back then were different.
The kinds of things people were doing on the internet were different.
They were totally exploring.
Then over the course of time, as we've worked on browsers, the kinds of things people tried to do in the browser was just so much more.
If you go back to early 2000s, you had the evolution of these more advanced web applications.
I remember marveling at Google Maps when it first launched.
The fact that you could just scroll and pan through a map so effortlessly.
Then it goes on from there.
All the different kinds of web apps that people take for granted, things like YouTube or-- I'm going to list a lot of Google apps because I worked at Google-- Gmail, Google Docs, all these things.
The kinds of things that you mean I can do all that in my browser?
It's kind of amazing.
It's become sort of like this operating system for your life and your laptop kind of deal.
Yeah.
It pushes what the browser needs to be able to do.
This era that we developed Chrome in was an era where people were already pushing the boundaries of what you could do inside of a browser.
But they had good reason to do it because the web, being this platform where it's so easy to put new experiences onto the internet meant there was a lot of motivation to do that.
Developers are being very creative in how they could push the bounds of what the browser could do.
But fast forward to today and it's like you have all that.
That's this foundation.
Now, just think about how the world's gotten more complicated.
I think there's a lot of opportunity for it to feel overwhelming, the amount of complexity for people.
Well, actually, I think even going back a few years, I remember when I was a kid and my school friends and I would trade shareware with each other on floppy disks, as you did back at that point.
And my mind is just not meant to retain certain types of information.
And so all of the things like the command line for how to run your unzip tool or however that worked, this was just something that felt entirely bizarre to me.
And so in that sense, the web was kind of a really refreshing take on that.
It was something where I could just go and click on things and explore without having to sort of understand the underlying nature of the machine.
And view source.
That's true.
But what I find with where the future of technology is going is that when we have these AI assistants that are attached to your computer, I think we'll find that we make that computing capability much more accessible to more people who aren't necessarily experts.
Even in maybe not just even in terms of how an operating system works or how a browser works, but even how individual websites work, you can express yourself more naturally as to what your intent is, what your goal is.
And then the system can kind of figure out how best to accomplish that for you.
It seems like there was a lot of ideas about what the web could be.
And part of it is that a lot of standards were things that were sort of decided after the fact, or we had to sort of go here and do that.
And then there was things that would have been nice to have like the semantic web.
We made sure that everything was sort of annotated and did that, but just in the real world, the corporate world, it's often hard to do that.
And now did you think you'd see a world where, hey, we could have LLM sort of understand this and make that possible?
Well, I think it's amazing to see, this is kind of the magic of these modern AI models is that they are really able to interact with things the way we interact with them.
So systems, and that's, of course, the world is designed for people with eyeballs and on the online people with mice to click on things or fingers to tap on things.
And so you talk about the semantic web, of course, it would be really nice if people would publish websites that were more inherently understandable by machines, but their motivation is to go where the users are.
And as much as we make a push for websites that are more accessible and screen readers and whatnot, the reality of course is that that's just not where developers spend their energy first and foremost, right?
And it's usually an afterthought to make sure that you make everything extremely accessible.
So kind of the beauty of these AI models is that they kind of meet the technology where users are.
Technology is designed for people to consume.
So you take a look at the way that it interacts with language and understands language.
It can interact with language the way we interact with language.
Self-driving cars, they can interact with the roads and the systems of transit the way that we interact with them.
And I think that's kind of the beauty of these AI models is that they can be developed for this world that was designed for humans.
And so that extends naturally to the browser.
I think it's not necessarily that we predicted exactly 100% how all of this would play out, but there's some very powerful ideas in that original internet where there was this idea that it was structured data that would be read and interpreted by a machine and then presented to the user in some way.
And so with the original web, there was this idea of a user's agent, a user agent, and that's the browser.
And then that takes that machine readable content and then applies some presentation preferences to it.
Maybe you like your font to be a little bit bigger, so it's easier to read.
Maybe you like it a certain style or weight or other stuff like that.
And it does it.
That was back in the original web was that idea.
And so I think that that carries forward in today's era actually very, very well.
And you can view where we are today as just sort of the natural endpoint or a continuation of that journey.
Evolution of the user agent, right?
So back in the day, even in Netscape browser, you could write what was called a custom style sheet or a user agent style sheet.
You could override the colors of any website and people maybe were who were more sophisticated would know how to do that.
Later on, browser extensions kind of made that a more universally available kind of thing.
People could write an extension, share it with other people more easily.
But it just makes a lot of sense now to like empower an LLM to be able to go and on your behalf, as Ben said, to really supercharge that user agent to be able to do more things on your behalf.
Yeah, there were a lot of interesting ideas, I think going back, it kind of at the dawn of all this and you look even the names of some of the tools like Gopher and Chirlock and Chirlock and whatnot and how it was kind of more proactive.
The idea that as you mentioned, these are sort of tools that don't just aren't document viewers.
And I think that we kind of take the browser for kind of granted and the idea that it just sort of like, it just shows me the website.
And I can see where it's helpful for you to probably haven't spent most of your careers working in the space of browsers and trying to understand that.
And it seems like there's like an inordinate amount of complexity there that's invisible.
Could you give me an example of like, you know, the kinds of things you have to deal with when you're trying to figure out how to make something work?
Man, browsers are maybe surprisingly complex.
I don't even know where to begin.
I'm amazed at how much work there is and how much technology goes into building a browser.
It's basically like an app platform or a mini operating system that's running on your desktop.
So everything, every discipline of computing, it feels like there's like you can nerd out on some aspect of the browser.
I was just having a conversation over lunch with one of the engineers on our team explaining how our OWL works, which is our embedding of Chromium that runs out of process.
I was explaining the rendering model for this and it kind of led to a conversation about how Chrome first worked when we first built it and then how the advent of GPU accelerated rendering evolved.
And now fast forward to the way it all works today and what we're trying to do with OWL and just sort of the depth of complexities there.
And I could go on and on actually.
It is interesting because I think that people kind of overlook like kind of the browser wars led to technologies like running node on servers to actually do stuff, which is I think nobody even thought would happen, but because just trying to make these things much more efficient and faster.
And I again, I kind of marvel that anything works at all.
And looking at some of the technical stuff you have released on chat GPT Atlas and understanding it's not just a plugin.
It's not just a thing that adds a chat GPT sidebar.
Could you explain a little bit more about the architecture?
So from a design perspective, I would say that we wanted to imagine the entire experience with chat GPT at the heart of this thing.
Not just I mean, we have a chat GPT extension as well that you can install in Chrome, for example, but there's some limits to what that can do.
And so when we approach this from a design perspective, we wanted to just be really empowered to look across the entire browsing surface.
And I think maybe like two to five percent of what we want to do is there today.
But we think that this being able to own the whole browser experience in this way gives us the opportunity to weave that chat GPT magic in throughout.
And that includes things, for example, like on any text field, you can sort of invoke chat GPT and have it help you write.
And then as it is helping you write, that is your personalized chat GPT.
It can sign your email as you because it knows you from your other use of chat GPT.
And so being able to build it in a way that enables these very like richly integrated use cases felt felt very important to have a browser as opposed to just an add on for an existing app.
And it gets to some of the foundational stuff.
When chat GPT is at the core of this thing and you enable things like the memories feature, it means that you can ask this thing, hey, what was that thing I was looking at again?
And it's going to know and it's going to help you.
Like I who hasn't had this this sort of experience of, oh, yeah, I remember I saw some video or I saw something.
What was that again?
How do I get back to it?
I want to share it with somebody else.
Traditionally, you might go through your browser history or your YouTube history and scroll through there trying to find it.
Or you're like, what was that tweet again that I saw?
Or I was looking at a recipe with my son on the weekend.
It was what was the third Buffalo wings recipe that we found that I wanted to make?
How do I find it again?
And just to be able to easily recall it, because this thing is able to do that.
So effortlessly, it's a side effect of it just being there.
Probably the most probably the probably what I would say is the biggest advantage for doing this and especially in the way that we have done it is how we thought about integrating this agent capability.
And this is really where having our own concept of browser, including what it means to have a collection of tabs.
If you think of your regular browser window, that's a collection of tabs.
Then you can also imagine that your agent has a collection of tabs.
Maybe each instance of the agent that you've chosen that you've asked to go off and do something for you, you might have like five of them each running on different problems.
And each one of those has its own collection of tabs.
And of course, they're not showing up on your top tabs because you didn't open them.
But it's nonetheless has them and it's working through them and it's getting information from them and it's processing it and taking action on your behalf and clicking on things and all that sort of stuff.
That is the sort of functionality that you can have when you go and you design a system like this sort of end to end.
You can invent all these abstractions.
And you had this in the very, very first version.
I remember when I joined Ben to work on this and he had already had sort of this idea, this idea that we would be able to segment tabs between the tabs that are the user's tabs and that tabs that are that the agent is working on for your behalf.
And that kind of shows up in the product today when you start an agent task, it goes off and it's going to work on whatever you asked it to work on.
And it might need to open some additional tabs.
And instead of those tabs just appearing in your tab strip and perhaps feeling a little discombobulating because like where are all these what are all these tabs, it has just sort of accumulated some work in the background.
And when it's done, then it presents it to you in a tabular form.
You can go and click through and see what it actually did.
Or you're just happy with the outcome and you really didn't need to see all the intermediate steps.
And so I think it's kind of powerful this idea that the agent has its own workspace.
I would say for many people using this on the surface, it seems pretty easy to understand.
I've got a browser, I've got chat GPT, but we also have agent mode.
What is an agent task?
What is not?
What would be a chat GPT task?
Could you explain that?
Yeah, so agent mode is basically you're inviting chat GPT to take action on the web on your behalf.
And so maybe you are looking at a website and you would like to do something on that site, but you're not quite sure how to do it.
What you can do is you can just ask chat GPT directly.
If you're let's say you're on a spreadsheet and you want to synthesize a pie chart and you don't know how to do that.
You can just say, hey, make a pie chart with this data.
And it will go off and it will figure out how to use that software.
Now, if you could think about sometimes some of the software that you use, it can be pretty complicated.
So just being able to ask a natural language and your own words, what you want to see, and then you could just sort of sit back and watch it take over and it starts moving the mouse around and doing stuff like that for you.
It's pretty, pretty amazing.
And you can see how it's going to do it.
So actually you can learn how to now make that pie chart because it's going to show you, which is pretty cool.
I found it pretty useful.
Like I like, I like to study memory methods and stuff.
And I have to do a thing where you have to have like a system for decks of cards and stuff.
And I didn't want to have to paste in a bunch of like card emojis.
And I'm like, can you just go do this for me?
And it's like magic.
It's like witchcraft.
One of the fun, fun things I've seen people do around the office is they'll have written a doc and then I'll ask it to take a review pass on their doc and like add some comments.
And so I'll actually go into your doc and it can use sort of the integrated commenting tool of whatever document editing system you're using.
And it will just add comments as if it was a collaborator.
Yeah, it's really amazing.
I mean, just we, of course, being software engineers, we experienced the model of critiquing our code.
And over the past year, just amazing to see how much better it's gotten at that.
Like in the beginning, it was not always the case that it would find things that were useful.
But it's these days, I'm like, this thing is sharing important, like amazing nuggets that are saving me from, you know, shipping bugs.
And I can just, you know, I can see the analogy to like reviewing any document that I might have and just asking it to go and give me some style feedback or, you know, maybe some grammar suggestions or like, you know, tone suggestions.
And I just, it's very exciting to think about how any tool you're using on the internet, you could ask this, invoke this agent and ask it to interact with that in the same way that I would or somebody else would and just see what it would do.
And maybe you learn from it or whatnot.
One of the things that's come up a lot during my conversations with the teams inside OpenAI is how much they're using the tools, you know, they're using GPT-5, GPT-5 codecs to do that.
And how is that affected you?
And do you think that's going to create an accelerated product cycle?
So absolutely, a couple of anecdotes on this one.
You know, one of the top codecs users at the company is on our team.
And they're just sort of like raw productivity in terms of like PR output is like off the charts, you know, as a result of using this tool.
And you know, it's really exciting to see what what experience PR output.
Yes.
Yeah.
So it's really exciting to see what experienced engineers can do with these tools because they can you can both sort of explore an area, help you explore an area, decide if something is worth doing.
And then you apply your judgment, you kind of tell it what you want it to do, and it goes off and does it.
And then for folks like me who maybe spend less time coding than I used to, I can also have it go off and prove some stuff out.
So like everyone on our team is able to contribute.
Our product managers are producing PRs, our designers are producing PRs because of these tools.
And so I'm like a true believer.
Yeah, I did a 4G, I did this week long refactoring to try to unlock a certain feature that we were trying to ship.
And then I had one more to do.
And this time I asked codecs to do it and it was done within the whole project was done within an hour and it was of similar scale.
And I was able to tell it, hey, just do this other one, kind of like I did that one.
So I had shown it the way.
And I just asked it to do this other task that was very similar.
And it was it was almost one shot.
One of the promises of really capable code tools that are able to write multiple languages, porting code from one language to another.
We saw with Sora and how they said, hey, Android is coming.
Yeah.
And people were like, oh, great.
When all that?
Oh, no, it shipped.
No, no.
I mean, actually, chat GPT has been amazing at doing cross-language translation for quite a while.
I mean, coding languages.
So we're bringing this product to Windows now and we're actually going to be using Swift, which because we are a bunch of the team is full of Swift experts.
And we are excited to have a shared common code base.
Swift in the Windows?
Yeah, Swift in Windows.
And so I'm not I'm you know, I think it's very in my past experience, I've been I was marveling even years ago at just how good chat GPT was at being able to essentially generate code for me in Swift that was that did not exist on the Internet.
So it was taking code that maybe was written for dotnet and could translate it to Swift for me.
And I was just I was marveling at its capability or or to generate a bunch of obscure WinRT code that's normally a very tedious C code with lots of GUIDs and all kinds of things that are very detailed.
But it was all just spinning out this code and saving us just an enormous amount of time.
Yeah, I had code XCLI spin up a Swift app with ever having to go into Xcode to paste anything in and it was work just right out of the box.
It really impressed me.
So it's it I mean, it's it's like kind of like one of the strengths of these models.
So the fact that you know, if you can ask the right question, get the right prompt, and it can and if it's on the right path and like how to build something, it can do it in any language.
That's really not a problem.
So I've been using this and I've been switching it to agent mode to do stuff.
And I know sometimes I can just leave a tab and go off and do something else.
And sometimes it's like, hey, if you leave this tab, I'm going to pause.
What's going on there?
Yeah, so this is sometimes you'll have asked the agent to do something that's very sensitive.
You know, an example is it's looking at your email and we would like you to keep your eyes on the road, so to speak.
You know, I have a car that has sort of an auto drive feature and it wants me to pay attention to the road.
It's helping me drive, but it's not going to let me like check my phone or, you know, take a nap or something like that.
And so it has a little camera that's watching my eyes.
It's making sure that I'm paying attention.
So you can kind of view this sensitive mode and in agent mode is kind of like that.
It wants me to pay attention to this tab while it completes, just so that I feel like I have a good level of control over it.
And in fact, if you look at the bottom of the tab, you'll see that there's a little bar that has a big red stop button in it.
And if you've ever been in a machine shop, you'll know that the machines there have these big red buttons on them.
If suddenly it starts to do something that you don't want it to do, you just whack that button and it stops.
And so that's the idea.
Just keep an eye on it, watch it go, and you can always take over if you want to do it yourself.
Yeah, we put a lot of thought into making sure that these features help you feel in control of the experience and take away some of that maybe uncertainty when you want to go use them.
For example, on top of what Ben mentioned, there's also the signed out method of using agents.
So if you want to start without it being in an authenticated session, meaning it doesn't have the cookies required to even access your email, you could do that.
And I think that can be a great way to kind of try some things and do it where you're learning like, how does this thing actually work?
And you might then hit a point where in order to take the next step with agent, well, actually, it would be helpful if it were authenticated.
And so then you might try doing a task where it does benefit from having your cookies.
You might not remember the probably the first time you actually run agent, it shows the screen that explains how all of this stuff works for you.
So you can like if you read through that, you'll see sort of the choices that you have and you'll learn about how to use them.
I have about a half a million unread email, I'm ready to go full auto, it can't do a worse job than I have so far.
You might find it just hit select all archive.
Yeah, wouldn't be the worst.
Yeah, I can have somebody to blame.
But it has been it's been super helpful for me because there have been times when I'm trying to surface an email and the keywords just don't work or the results are too many and just being able to go in and say, find this thing about that.
Yeah, that's saved me numerous times.
And so one of the other things that we did with agent as well, because there are times when you'll want to keep an eye on it, is that we and I'm pretty proud of what the team was able to come up with here is to make it like very visually compelling.
And so there's you know, all of the little sparkles and pixie dust and so on that appear around it as it's working.
It's pretty cool.
So yeah, love to see more people try it out.
Yeah, it's fun to watch that.
And in also the chat, GPT to an agent mode, I've said that I could probably watch a live stream of just watching these systems solve problems, because it's like how it's made, but watching computers do it.
It's exciting to see where this headed.
I also sort of wonder, what's it going to be like when you know, there's going to be a lot of different AI powered browsers out there.
And also we have to think about like, what is what is the ecosystem like when most of my tabs are opened by my agent and not me and somebody is trying to capture my attention.
The way agent works right now is that it's only it's only like running in response to your request.
And so if the agent is doing something, it's because you at some level you asked for it.
Pages that it opens actually have some limitations.
So like you might be used to browsing around the web and you'll see some page, you know, show a pop up window saying give me like notifications permissions so that I can sort of spam you with updates.
Never ever clicked on that.
Nobody's ever intentionally clicked on that.
Yeah.
The agent tabs can't do that.
They're actually blocked from doing so.
There's a bunch of stuff like the design of the system to avoid you accidentally ending up in that state.
And of course you're free, you know, when you browse to a website and you're asked for a notification permission, if you want to receive updates from that site, it might be your calendar.
Right.
You're free as a user to go and like say, yes, I want this, but the agent will never do that on your behalf.
It's an interesting world where we think about part of the beauty of the early web was the serendipity.
Oh, I found this other thing.
I found these other links.
But I think then that kind of got sort of weaponized against the user where basically you try to do a thing and it's hard to do a thing.
And I think we've got to.
Yeah, it's really interesting.
I don't know if this is where you're going with that, but like a lot of websites want to just keep you on their website.
Maybe they'll run ads, which would take you off, but otherwise they kind of keep you in that lane.
One of the amazing things about the side chat or the model being present there and the agent even is just that you can ask a questions about that site where the answer might be something on a different site.
And so it makes the web bigger for you and helps you not just be stuck down that rabbit hole that you were on, but to help bridge you to something more useful to you maybe or more helpful.
I know you have some good stories on this.
There's something just wonderful about the, I call it beautiful chaos of the web where you kind of don't want to always be stuck in the same place.
You want to be able to embrace the diversity of the web and all of the content that's on it.
So yeah, I love that.
I love that you can do it as well without having to leave the site.
I know you can do it right there on the side and then you can choose to go somewhere else.
But it's sort of, there's this aspect of, I know with Wikipedia, you can go on these like multi-hour journeys through content.
That's really only a, that's like a feature of Wikipedia.
Whereas I feel like the Ask Chat GPT sidebar gives you that ability for like the web at scale.
And so it gives you the ability to ask questions about random sites and then go off in different directions and that sort of thing.
I mean, this is extremely useful if you're looking for certain kinds of products and you find yourself onto one product page for one company or one vendor, but now you can be like, well, what else is out there?
And the model can say, well, here are some other sites to go check out that are related to this and off you go.
Now your world has gotten bigger, right?
I've had some wonderful discoveries with both videos and books that I couldn't find through the YouTube search engine or the Amazon search engine.
I found places where because Chat GPT understood a bit more about what I was looking for, what I was really trying to find.
And that was like, it gave me more utility out of those sites.
Yeah, it's actually another, like so for Chat GPT as a whole, like the personalization features, the fact that it sort of learns more about you, the more you use it, has been like a super popular feature of Chat GPT with Atlas, you know, this extends to your browsing activity, like your sort of web history.
And so this allows the browser to create these browser memories, which Darren pointed out before is kind of something you can use to help you get back to a site if you kind of can't remember it later.
But it also helps in situations like with the agent.
You know, I'm a United Mileage Plus member, and so I tend to like to look for flights on that site.
It would be very tedious if every time I asked the agent to go and do something like that, if I had to tell it and always use United Airlines.
But it kind of knows from my browser memories that I'm a frequent user of United.
And so it will just go there.
Yeah, it helps you in the forward queries, right?
Because it's like now this search experience has so much more context about what matters to you.
So it just ends up being a lot more efficient, saves you a bunch of time because you don't have to tell it as much again and again.
So I feel like that's something that helps me a lot.
I think some people probably have, you know, different preferences around these things as well.
So there are controls where people can go and see and control what memories are used.
You can turn it off if you want.
You can turn it off entirely.
And you also have to, when you use it, and I don't go into these tabs as much.
I'm starting to do that more because I realize there is I can go to images, I can go to news, I have kind of like a search engine.
And that's the thing I'm trying to sort of understand is the browser, but is also opening and heading towards its own search engine.
Well, part of that comes from the fact that when you're building a browser, people come to that browser with existing intents and like navigational intents or the idea that they do want to look for images, right?
Or they want to see a certain kind of subset of information.
And so we brought those controls into the landing page of chatgbt.com so that it would be both familiar to people, but also useful in the way that they're used to, right?
We want to make sure people didn't feel like they're so out of, you know, that we didn't want people to have to learn so many new things in order to be successful using this product.
We wanted them to have a lot, a good dose of familiar tools and familiar sorts of things.
And anyways, these are just useful.
There are many people search and browser just very connected.
That's one of the same.
And, you know, it's very important to internalize that as we're building this experience.
I think it's very powerful that, and I was touching on this before, that as people search and use the browser in maybe a very normal way, they're also learning about that there's a model there that's going to respond to them.
So you get the, a set of chips across the top, which is like quick links to go to where you were trying to go.
Perhaps these different tabs where you can click on to see like familiar or different kinds of subsets of information, but also this model response coming in.
And so you start to, you using a product in a normal way, you start to learn that there's another way or that there's a superpower that this thing's providing.
And it's, some of it is just the normal chat GPT experience that people are used to, but not everybody's using chat GPT to the fullness.
And so when you, and when it's core and central to the experience, we have an opportunity to present that to people as part of their normal journey.
And I think that's really cool.
Similar to side chat.
Of course you have to activate it, but it's right there as chat GPT.
And you might be curious.
And now you kind of unlock the superpower, but it's right there.
The context is there.
Interesting experience for me was the, the very first day when I started using it.
And I look at this, I'm under trying to understand, okay, this is basically, it's, it's an app that has a browser and chat GPT.
It's not like we just sort of glued those things together.
It's sort of like they're both there and there's a deep connection to the chat GPT.
And I asked it to, could you add a bookmark for, you know, Amazon?
And then a moment later, the bookmark appeared and that was a really kind of special moment to sort of understand what happens when you're the LLM deeply understands the system and is able to make those kinds of changes.
We're very excited about this.
I think from a, just like a conceptual transformation point of view, we're moving to a world where you can just tell the computer what you want in like whatever way you want to tell it simplest way possible.
And so what this means for making computing more accessible to more people is just like really profound.
And that's like the company's mission is to make AGI beneficial to all of humanity.
We take that really seriously.
And I think being able to transform computing in ways like this that might seem very small on, on face of it, they add up to something, you know, far more profound.
And so yeah, that we're excited about that kind of thing.
Some of my first experiences with chat GPT as a user was really this idea, Ben's talking about, you know, I was comfortable, happy just sitting there doing my Google searches, but sometimes I didn't quite know what Google query to type in.
And, you know, when I, when I realized I could ask sort of a really poorly formed question to chat GPT, and it would come back with, make some sense of what I asked, what I said, it would, it would give me something that maybe now I could query Google for.
And that's how I first started using chat GPT.
And then I started to realize over time that like, oh, why am I not just asking it in the first place, you know, and, and it's sort of, I think for people, they all have like a, there's like a bit of a journey with new technology, right?
You're, we're all creatures of habit, we're used to the things the way we work, and it works well for us, the things we're used to, we're used to it.
So it's not a problem.
And but as you maybe explore something new, you start to see, oh, there actually is a better way.
And for everybody, that journey is a little different.
And so for me, one of the things I was most excited about with Atlas was this idea that when you're typing into the address bar, that the default is chat GPT, because for me, that's actually makes sense for most of what I'm going to do.
And this is one of these things where I feel like now when I don't have access to that, I feel like there's like this little bit of friction.
Like it takes longer now, because then I've got to go, I've got to go find my chat GPT tab and another browser and like figure out how to get at that and do that.
Whereas with Atlas, you can just like open a new tab and start typing.
The old way was a much more manual way.
This way is a much more, I don't have to be as like clever about what I ask.
I can just give some sort of problem.
Yeah, I have a problem.
I can say it in a much more simple way.
I know that I'm still having trouble kind of context switching and understanding that it's not just a URL search bar, just an empty keyword search, whatever, that literally I can ask it for things and not just have, what is the capital of Nepal and not just have that pop into a Google search box.
And that's the thing now, I'm going to be like, oh yeah, when I go type in the thing, if I type in the URL, I get the URL, but I can also type in kind of my query and do that.
But that's still taking me time to adjust.
Well, just as a general rule, like I find sometimes modes can be a reflection of some of the limitations of the system underneath that at the end of the day, humans don't understand.
And so I think the North Star for us with so much of this stuff is can we just help you arrive at the right place?
Regardless if you're needing to know, I should put it in this mode or I should put it in that mode, like that is sort of the struggle that comes down to like, how do you want to use this tool?
And so we want to make this thing something that, you know, if you just go in, as Darren was saying before, you can just kind of tell it what you want, maybe this half formed thought, and it will give you something good, it will help you figure out the problem.
And of course, there are ways that you know, if you are a user that understands some of the underlying capabilities of the system, we want to give you the option to invoke those two to bring them down and help you.
And that that sort of an efficiency gain that you can get, but the certainly the system shouldn't require that you know, all of those sort of incantations, it should be able to just take what you say to it and give you something good.
Yeah, I think it reminds me back to like the early days of browsers in the era when people would install like a toolbar for their search engine.
And, you know, that meant they had yet another box on their browser, right?
And Firefox had a dedicated search box for doing your web search.
But back then, as much as people were very used to that and very comfortable with it, you know, you have one box to type URLs, and one box to type search queries.
When we were working on Chrome, we're like, why why have two boxes?
Why do people have to stop and think about which box to type it into?
Just gives them one box.
Now, if you look at Chrome, that's what its URL bar looks like, right?
Just one box and that's become the industry standard.
But even on Chrome's new tab page, there's actually two boxes.
There's one for the address bar at the top.
And then there's this box in the middle.
That's the maybe comfortable familiar Google box, right?
What we wanted to do and we kind of pushed ourselves with is like this whole topic of like, hey, you might have a conversation, you want to start with the model, you might be interested in navigation, navigational query, but really, you might not make up your mind about what your intent is until you start typing.
And just one box is a lot simpler.
And so when you open up Atlas, you just have one box on the new tab page.
And that was something from a design perspective that we really tried to achieve.
And I think we were able to and it keeps the whole system a little bit simpler for people.
It might be a little unusual and not what people are used to, but I think over time, they'll get to like it.
What was some of your favorite features, some of the things you're glad you're able to implement?
Oh, man.
You know, it's interesting, whenever you get a chance to build a new browser, you have having worked on quite a few, you get a chance to sort of start over and reset on certain things.
Not everything, because I think one of the core tensions is that people are used to their browser the way it is.
But you do have a chance to rethink some things.
So one of the features I worked on was the scrolling tabs feature.
It kind of came from an insight of that tab life could be a little better if maybe new tabs all started all were inserted on the left, or just on one side.
If you're a user who pins tabs in your browser, which is a pretty advanced use case, maybe a lot of people don't know that you can pin tabs to the tab strip in Chrome, or Safari, or other browsers.
But it is a common thing.
And if you pin a tab, it'll be pinned on the left side.
And whenever, suppose that was like a Gmail tab, when you click links, those new web pages would open just adjacent to that pin tab.
But if you press the plus button, the new tabs would appear off to the right.
And what ends up happening is you're working throughout your day, you're going to Gmail, opening a URL from there, you're hitting the plus button, opening button tabs on the right, and you're sort of accumulating old tabs in the middle.
And so it becomes a little bit painful to close all the tabs to the right, from the middle, to clean up those tabs, and you just end up with a lot of clutter.
So scrolling tabs was one of the innovations that we worked on to try to make tab management better.
And it's not an AI feature, but it's like when you have this opportunity to rethink browsers, it's an opportunity to rethink some of these primitives and try some different things.
Many is a major productivity tool.
So finding these wins can be like really, really exciting.
And we think about one of the things that I came to realize and appreciate only later is that if you have a browser that more naturally scales to having tons and tons of tabs, it means that certain kinds of things get unlocked for you.
So everybody's, many people are probably familiar with the ability to search for a specific tab that you might have open.
There's a command shift A or a button for that in many browsers.
With our system, with scrolling tabs, the fact that it can allow for a lot of tabs to be accumulated without them all being in your face, you can still search across them and find these old tabs.
So in a way, it's like this history of things you've done in your browser is there for you to search in a very familiar way because it's your command shift A, it's right there.
And you can have that capability without it being cluttered.
Darren's talking about tab search.
Search over your tabs, you can just type and that will find the tab that you want.
But I think the most interesting thing about this feature is the fact that you don't need to close tabs.
And so you can end up having, I think my browser, I've got like well over a thousand tabs open and I just wouldn't think for that to be possible.
Or you might think that that'd be a problem, right?
But it's not.
No, because the system manages the memory for you.
Yeah.
Now this is the scrolling tabs feature that is not on by default.
And part of the reason why it's not on by default, as much as we think it's magical and I'm a huge fan of this thing we built, it is also a little different than what people are used to.
And we wanted people to not have to learn so many new things all at once when they're approaching this browser that is bringing all these AI capabilities.
But one of the amazing things when you have allowed for thousands of tabs to be open means not only do you get to access it again with tab search, but the model can see them.
The model can see these tabs.
It means your working set can be very large, larger than what you might keep in your head naturally.
But you know that there was something there so you're going to ask the model for it and it can go and interact with those tabs again.
And I think that's actually pretty amazing.
I would be remiss if we didn't, if I didn't mention for this question as well, just the basic feature of Atlas, which is the Ask Chat GBT sidebar.
This is something I get some value out of every single day as I use the browser.
I pull that thing open, I ask it to summarize a page if it's too long or I want to figure out like if I'm reading an article, like how it really matters to me in particular.
If I have a question about something that's going on in the world, it can go off and do some research for me and come back with stats and facts and figures.
I've used it when I'm online shopping to make sure I'm looking at what really is the best deal on something that I'm looking at.
I've used it to help spin up agent tasks to go off and automate some of my productivity workflows.
I've had it build you know Google Forms for me to help me like quiz my co-workers on the best way to design new features for the browser.
I really like that example because if I remember correctly you said you also asked side chat to help come up with the outline of the survey and then you said, "Hey, can you just put it into Google Form for me?"
and it did it and that's really cool.
Yeah, so it's just, you know, we talked before about bringing the power of chat GBT with you everywhere you go on the web and I think that sidebar really it's like having chat GBT sitting on your shoulder just right there to help give you some advice wherever you might need it.
And sometimes even just simple things like I was in Slack and there was some somebody shared some text that was in another language so I just selected it and I right click and asked side chat about it and it translated it for me and it was so much easier than having to you don't have to sit there and copy paste right.
My favorite use of that so far with the in the agent mode and I won't name the cloud provider but it's a very big company that often you find out you run a lot of services and you forget what those services are and at the end of the month you get a bill and it's a very confusing bill because you're trying to figure out I thought I shut this down.
Isn't this all of them?
Yeah, well some of them are a little bit or maybe you've been around longer and trying to parse through that's like reading the Soviet tractor manual and I went in and I said, "Hey, I got this bill.
I think I should have been going.
I don't know what's going on.
Can you help me with it?"
and I watched it navigate through the website, go to the page, find the different things I was doing, explain to me what the service was doing.
I'm like, "Can I shut this down?"
I'm like, "Yeah, shut it down."
and that was like a hundred dollar a month bill that was just saved through.
Wow, that's really that's awesome.
Another one I had as well, I was actually I had some medical tests done recently and sometimes it can take a while for the doctor to come back and explain to you like what they mean and then in the meantime you have the patient portal there and you can access the sort of doctor language stuff there and I can't read that.
It's not written in English, normal English and you can have the thing you can ask and that will tell you kind of like what that means for you and I found that to be really helpful.
So saving you money, helping you get some answers.
This thing feels very, very, like I'm pretty convinced that this is the way, increasingly the way that people will interact with information.
Or you're using some very popular yet complicated HR tool or something like this and you're like, "Where's that thing again?"
and it of course has studied the manual for you and can go and show you the way.
It's kind of remarkable.
I feel like it took me a long time to realize that once I had an iPhone that I always had a camera and a flashlight in my pocket and there are many situations where I'm like, "What was the name of this thing I saw in the store?"
It's like, "You could have taken a photo."
Or, "Man, it's dark."
It's like you've got a flashlight and I feel with these tools there's a lot of capability there that we even saw that to a search.
Some of us were power users of search and other people was a complete mystery and do you think we'll see a faster acceleration here that people are going to start sharing and understand how to use this?
Yeah, I think the stage that we're in with Atlas right now is we think this is a really powerful tool but we don't know all the ways in which people will use it and it's kind of like the internet in that sense.
One of the reasons why we wanted to get this out when we did is we just want to see how people use it and hear from people where it works well, where it sucks and needs to get improved.
I think over the course of time we'll get a better feel for that.
I also think we'll need to help explain in more cases when the right time to use it could be because I think there's a part of building something that feels like magic instead of making that magic real for more people in more situations and we don't want to have to rely on people to always think I should ask this question at this time.
Yeah, it's really easy to just we're creatures of habits.
We use the browser the way we use the browser.
We use our computers the way we use them.
We don't always realize when there's a better way to do something or a more efficient thing that we could be doing.
I feel this way about when you know the process of learning how to use chat GPC in the first place.
It's like it's just like realization.
Oh, I should just ask the model for that.
It'll save me time but it takes a little while and there's a bit of a tipping point for people where they start at some point in their journey they're going to learn that how to use these tools and there might be some people who are early adopters and they can show the way and figure things out and share those ideas but also it's kind of like I think a lot of people haven't yet found their way to how to use these tools in the best way.
I find myself still trying to shut down tabs because I'm still you know I started using browsers in the era of getting the pop-up message you have too many browser tabs open and now the you know compute and the capability and the management internally these things is way advanced and so I think about like you know I'm not optimized in many ways.
Also another like say non-ai feature of our browser was that we kind of took a took a page out of the playbook of mobile browsers recognizing that you know your laptops computing resources are not really limited you have a battery you care about you know so we put a limit on how many tabs would actually be backed by a live web page instead of trying to might be the more traditional approach that desktop browsers would take which is to just try to mitigate the cost of those background web pages that you haven't used in forever.
We will just close them down and if you go back to that tab it'll get reopened and we keep a reasonable limit there and we apply you know somewhat of a clever ish caching algorithm to try to be smart about keeping making sure that that tabs you care about are kept in memory.
So as to sort of lessen the burden on your computer you might notice also with Atlas that it restarts super fast when you restart Atlas because of the way it's structured the AL process is separate from the Atlas process AL being our embedding of chromium so the two can start up in parallel and we can restart Atlas very quickly with all your tabs and the data associated with them but the web pages aren't loaded yet and when you click on them bring those web pages back but this way the whole system can stay fast lightweight and as we were able to build Atlas as a separate application from this from AL Atlas is controlling AL.
AL is projecting data into you know the rendering of web pages into Atlas but Atlas itself can stay a relatively thin Swift application.
Why chromium?
That's a fantastic question.
I answered this question on the site formerly known as Twitter by saying that you know web compatibility so it turns out unfortunately or for better or worse a lot of websites are only really designed to work with chromium.
There are features of major websites which I won't go into the naming names but that are just not present if you're not using chromium based browser and the other reason is chromium extensions.
Extensions built on top of chromium are very popular and when you build your browser on top of chromium it means those extensions will just work and so we wanted to make sure that we were building a browser that first off works for people that all the websites they care about will be supported and all the features of those websites will be supported and we want to make sure that they could install any of the extensions that they care about and that they're used to using in the browser.
And it seems like there's also you know we kind of non-technical people they hear chromium they hear chromium but not understand there's like a really deep lineage that even goes further back you as well.
Webkit and KDE and whatnot.
So what I'd say is and you know I think there's like a lot of excitement for you know from among the community for for to see like new rendering engines come about and that's certainly been part of the DNA of the web too over over the years.
At the same time just like Darren said you know when you build a new browser and you don't have that many people using your product just yet it's it's you kind of just want the web to work as people know it today and actually back when we were starting working on Chrome we had the same concern like you know chromium today you know has blink which is sort of its own rendering engine that sort of diverged from from that lineage but at that point like there wasn't much appetite for taking risks like that and so that the chromium rendering engine is based on Webkit which is the Safari rendering engine which is open source and that itself was based on an earlier rendering engine from from the Linux world called KHTML.
And so yeah it's really interesting to go back in time so you can see how these sort of open source projects for can branch and so on.
Yeah there's code in chromium that comes from the Mozilla project too.
You're going back to the 1990s you can find this.
This is true.
This lineage.
So you know browsers are this sort of this layer cake of technology that's been built up over time and you know really where we are wanting to innovate is that next layer where the the AI model comes in and how it's articulating and interacting with the foundational layers and so far as building on top of chromium is like gives us this well-known foundation.
We built on top of chromium in a very different way than normally browsers would.
Most browsers are just taking chromium and forking the UI or layering another you know UI on top of chromium but running right in the same process as chromium.
What that means is that if chromium is doing work your application is not doing work.
And so in the structure that we set up with OWL it means that Atlas is able to work in parallel with the rest of the all the activities related to rendering the web and producing web pages which is pretty cool.
So if the browser part crashes.
Yeah if the OWL part crashes if something goes wrong with that piece then you sorry Atlas can restart OWL.
So that's actually a really interesting thing because I remember back when we were originally doing the design of Chrome there was this thought of like well the web page might crash and therefore your browser should be around and then because you know chromium has sort of become this very sophisticated platform for web pages it itself has become super complicated and now like Atlas is this very lightweight frame around the outside that really is about like that core productivity use case of using a browser with chatchee-bt kind of as this tool that you can bring down on onto any page and that's really where its focus is.
Whereas like the chromium i.e. OWL piece is able to focus on being that platform and then both parts are not really they're resilient to each other's you know difficulties.
This is true in that sense.
Yeah just actually like another fun fact about like open AI and the benefit of the system that we've built every engineer that starts at open AI merges code on their first day and if you think about you know how massive chromium is as a platform you know it's it's really super powerful but it's a lot of code it takes a while to get all that code onto your device.
Just a little bit complicated.
Yeah and it takes a while to build it all and so we tend to get our new hires in the afternoon as they've gone through all of their onboarding training and then they have to merge a change so to be able to check out all of that code and build it and then make a change to the code in your first afternoon can be pretty tough if you have to do all of that but because we have structured this in a way that they don't have to you can go and make a change to the to the atlas side get that checked out and built very very quickly our engineers are able to be productive right away and merge code on their first day and like ship features and their first day.
Related to this so always when you're starting a new project you get to make new technology choices you get to when we were starting chrome we got to say what is the latest and greatest way to build code right fast forward to starting atlas we're like what's the latest and greatest way to build a native app on mac os so of course we're going to be using swift we're going to be using swift ui where where it makes sense and we're going to be you know using all these um you know the app is built in x code and just done in a very familiar way so people who are are used to doing swift development maybe because they're building ios apps they can come in and just be instantly productive because this is not a foreign code base not a foreign system you know and uh and yet it's it's harnessing the power of chromium at the same time which is super complicated when you look at this from the outside a lot of people draw comparisons to go well you know there was operator now they're doing chat gpt atlas you know is this going to be a real thing for them or is this another experiment so a browser um you know i think it's a it's a super core tool for productivity um and it's something that you need to be able to count on and so my view for this has always been that this is like a long-term investment and so that's the way that we're approaching it um there's a set of functionality that we've launched which is sort of like the first phase if i come back to browser history i sort of say it's the you know netscape 1.0 if you like of this new era of of web browsing um so there's going to be a lot of future improvements to come features that we're building because people have told us about it from the initial set of feedback things that we come up with you know through our partnership with research a whole host of new functionality that will come out over the course of time the other thing that we hear from folks is they want to see this across different platforms yeah basically this browser isn't available for my windows device or on my phone or that sort of thing so these are things that we are we're thinking about and working on so there's like a long roadmap of enhancements and so we want people to both feel confidence that this will get better over the course of time it actually gets better every week when we push an update and they will see it increasingly on more of the surfaces where they are so definitely a long-term investment for us yeah we got this app to the point where internally the users at openai where we were seeing them enjoy this product and you know and we wanted we were at a point where uh the kind of feedback we were getting was uh was was was uh you know uh why haven't you shipped it yet you know why haven't you shipped it yet is exactly what i was thinking because it's like we weren't getting new feedback yeah we we were we and we realized we're ready to ship this we want to share this with the world we want to we want to hear how other people are experiencing it and i think that you know this feedback's been all kinds of amazing uh you know obviously there's been uh you know people who have their pet feature that's missing or like when ben said how come i can't you know where's windows when but you know the other day my my 14 year old son came back and he's like oh man my friends at school they love this browser you know kind of a thing and and i was asking like really what do they love about it and then they just he just was like talking about all the different ai features that they were checking out i think it's really interesting to see um that sort of spark of fascination from people um whether it's kids or or uh you know people we work with or friends as they sort of share their experiences with this thing and i don't know i just love to see how people um my my wife was so giddy when she first got to try atlas when when we did the friends and family testing and just to be able to go and explore researching some task and asking uh the side chat about what she was looking at and just she had so much fun with it my wife loves it this is not a lie and exaggeration the night that it came out we're sitting in bed i'm reading and i look over how i do and she says i swear to you i swear to you goes i can't stop thinking about chat gpt atlas because for her it was her first use of an agentic system like this and to be able to go do these things it was a huge unlock was her favorite tools chat gpt now connected to the browser yep exactly because i'm just the tediousness that it takes away when you i'm looking at this website or i'm doing some research and i can just ask it now about the thing i was talking about it to it before and now we can take this as context and we can kind of keep going and research and whatever the topic is it just becomes a lot easier when the ai when the model is right there with you i think a lot of folks like struggle with you know how to do you know you know sometimes like what seem like very complex tasks on certain websites you know one of those websites i think is you know if i'm on a spreadsheet um a web base pick your favorite web base spreadsheet program how do i visualize this data in a certain way if you just have a tool there that you can ask you know drop in and help in a very consistent way i think that's really really interesting um yeah the other piece that i think is interesting you know related to uh to your wife's reaction is um this is a lot of net new capability i think for a lot of folks in the world um i'm what i'm really excited about with this tool is that you know our our model capabilities are always evolving so at any given point in time it's not like sort of the ultimate state of it but we kind of get to show people how this stuff works and i think it with that build some more understanding some more trust um about you know how this this this technology is working on on your behalf and i think it's you know even if we came up with the world's best model um tomorrow that solved every problem perfectly in the way that you personally would have wanted that problem solved you probably would still want to be able to come along for the ride and understand how that was actually happening uh just you know front for your own education i think over time i think when as your trust level builds eventually you'll be you'll feel comfortable fully delegating very complex tasks uh to this technology but we're not at that stage yet um and so i think one of the things i'm really really happy and excited about is that people are able to come and observe the sort of the next step of this technology and you know watch it see how it does you know tell us you know yellow dust when it doesn't work you know that kind of thing but i think you can kind of get a feel for how it works and as a result like you will know like what it what it's going to be capable of and you'll kind of know what the controls are like where you want it to stop doing something or you want to do something differently you can just tell it and so on i think you can kind of dial up and down how much you use the model and the ways you use it in this product but it's kind of like right there it's easy to try again and i think sometimes the magic the magic i've felt with chat gpt is is when it when it really works ever so well that i'm like oh i'm going to go back for that right it's that you have an you have those magic moments where it's like oh my gosh i i'm going to change my habits because of how this works right and i think i think in this case it's like easy for people to use familiar patterns right i open the new tab page i do a search it lands me into an experience that includes some links i can click on but there's also the model response and so you start to learn that like uh maybe instead of that website i was looking for that was going to answer my question it's just right there and and i can go and explore that and i can ask it another question you start to learn the power of of this model just by virtue of using the product in a familiar normal way and so for me that's that's kind of exciting to see how people it might open the door to people starting to realize just you know what the capabilities of this model are looking to the future and first let's start short term i can understand how a windows version you're going to pretty much want parity of what you have right now in the mac version but when you talk about mobile and it's one thing when i have a lot of desktop space and i can put a sidebar and have the chat thing there but when you're talking on mobile browsing as you guys know especially as a very tricky thing and moving a search tab from the top to the bottom or whatever seems like a revolutionary change uh how are you thinking about that the mobile experience and also is it going to maybe or are we going to be thinking more agentically and how we use these links so maybe fun fact some of our initial explorations were actually on mobile and and part of the way we were thinking about it was really what does it mean to bring the model to the web right and that can take many different forms and of course chat gbt is exist as an app on on your phone as you can imagine ways in which you might share to that the kinds of memories that have been generated by using atlas right so there's a lot of different flavors and forms in which mobile could come how this can manifest on mobile but at the basic level it's like what are some interesting you know we're going to be looking at like how can we bring the web to the model and what does that mean what makes sense on mobile the ux you know may look a little bit different obviously as you point out there's a sort of a different form factor there we've got very talented designers though i'm sure that they'll come up with a good way to solve some of this stuff definitely i think on mobile or at least i noticed through my own use um like my use case is far more information retrieval like i have a question you know actually i use the chat gbt app a lot if i have a question about something i'm around or i point the camera at the thing and like what is this you know that type of thing so i think that there are a whole host of situations like that where there is web content that is part of that journey and we want to make sure that that that user flow that you have with atlas where you can view some web content where you can ask follow-up questions and then go back and look at the content again that that feels very good that's something that we're sort of in the midst of figuring out right now and so you know like not too much more thought on it than that other than that it's something that we're going to want to make sure it's like very feels very good yeah i think we hear from people that the importance of mobile because uh you know they're doing work on their laptop and they want to continue in some fashion on their phone right so you can start to imagine the kinds of uh space and possibilities there where are we going to be in five years with how we're using the web and how we use tools like this so i would love to be in a place where people think less about the particulars of the tools they're using and are more just expressing what they want to the system and then the system is smart enough to understand how to respond to that in a good way and so in that sense we can be as you know as humans we can be focused on the highest you know the questions the highest order um piece which is like what is the most um interesting for me to do you know the model maybe can take over an agent can drive maybe the less appetizing part of the work the more more i use the word toil to describe some of that sort of grunt work of pulling information from a bunch of different sources um maybe it can do on do a bunch of things that just seem very difficult to you because you've not done them before it sort of knows how to do those things and then you can be focused on the things that you want to do so i imagine a world where actually there may be a lot of internet traffic in the future that is um that is agentic that may even be most of the internet traffic i still see um people as doing a bunch of generating a bunch of traffic as well um but uh that should be you know it should be efficient it should be people should be focused on doing the things that they want to do and delegating more of this work uh to uh more of this toil really uh to to agents that can take on all of that that other stuff and then like if you have to uh make a decision on a project maybe your agent comes back to you and gives you some choices you know if you're going to take a vacation do you want to stay at this hotel or that hotel you can pick uh between them you get to make a choice but all of the sort of grungy clicking around and scouring the internet uh for these things maybe it it took the first pass and presented you some choices we talked a bit about how as users and developers of this tool you look at it if i was somebody who had an e-commerce site and if i was looking at i'm going to be putting information on the web and i know that one there'd been conversations you know for a while like what happens when llm's go search the web and now we get into the world of agents when agents are using this and plus you know llm-powered browsers what advice what direction would you be telling people to think you mean the publishers yeah yeah i mean i think that um it's really interesting like in some ways i think about the the maybe a little bit related to what ben was talking about like um you know you see the more recent models they've they've learned how to uh based on the query decide hey i should actually look at the internet to um to to answer your question right and so i think it's really interesting how these models can um help you connect to publishers in web apps and whatever content that's out there either um you know giving you a you know a snippet and like a citation to it so you can go deeper or or even just connecting you to it because that's actually what you you know if your intent was to navigate to a site then it can help you get there i think one of the things we've been exploring with atlas is how to for example better handle and better serve navigational intents sometimes people come to their browser with absolutely the intent of i want to buy this product on this site you know and that's our job just to get you there as fast as possible and so it's been actually an element of building atlas was making sure we're serving those kinds of queries well other times you just want to probe the knowledge the knowledge of the model and have it go and research something for you and sometimes that involves it needing to invoke tools to do that on your behalf and so again sort of depends what ben was talking about it's i you know i imagine a world in the future when you don't have to be so prescriptive about what tool you want the model to use but rather it has this incredible palette of tools that it can draw upon and some of them can be you know actuating your browser things like this we're going to be using web pages in 10 years i think so i you know it's kind of uh um it's kind of this this fabric of like of this world where people are publishing through this this this it's the core primitive how people are putting content out there right so it's kind of the you know the internet superhighway all that kind of those analogies but it is like this this open fabric for which people can publish and i don't see that changing it's the world's largest you know as you mentioned before most open platform and i think some of that power of openness is always going to make it attractive for people to put content on the way i look at it is these tools yes they are able to understand that fabric understand that internet understand the content that's out there but they're also able to bring that content to people and connect people to that content and it can be very powerful and again it's all in service of what is that user's intent i think it's fairly interesting to think about how we can do a better and better job of that it really serving the needs of those users and ultimately as people are putting content out there that's intended for people if you're you're you're putting out content that's your you know it's a gallery for somebody to go shopping or something like this we want to help people find that help people get connected to that help people with the journey that they're on and whatever that may be this is exciting thank you for sharing this um any last suggestions any power user tips yeah definitely definitely the scrolling tabs feature is like a favorite uh for both of us um yeah i would just say like uh challenge yourself like i said at this point very early stage but challenge yourself with your curiosity on any given page ask a question on more pages that that you visit and you might be surprised with what you come up with awesome and we'd love to hear from everybody about you know how they how they're experiencing the product so please keep the feedback coming definitely ben darren thank you very much thank you thank you [BLANK_AUDIO]