Learning Library

← Back to Library

OpenAI Atlas: AI Browser Review

Key Points

  • OpenAI introduced Atlas, an AI‑enabled web browser that adds a persistent chat assistant sidebar, mirroring the “smart‑browser” model popularized by tools like Perplexity’s comment browser.
  • In a live demo, the assistant successfully generated and styled a PowerPoint slide deck—handling layout, color schemes, and content expansion—though it struggled with finer formatting details such as precise text‑color placement.
  • The reviewer found Atlas to be the most practically useful AI‑browser utility they’ve seen in a while, noting its ability to execute commands (e.g., adjusting font size) while the user multitasks across other tabs.
  • While Atlas isn’t yet powerful enough to dethrone Chrome, the reviewer is bullish on its development trajectory and the broader possibilities of an AI‑driven browser modality.
  • The tool shows promise for automating repetitive web tasks (e.g., folder creation, content editing), potentially freeing up significant time for users.

Full Transcript

# OpenAI Atlas: AI Browser Review **Source:** [https://www.youtube.com/watch?v=9ydIVzh7TBo](https://www.youtube.com/watch?v=9ydIVzh7TBo) **Duration:** 00:10:03 ## Summary - OpenAI introduced Atlas, an AI‑enabled web browser that adds a persistent chat assistant sidebar, mirroring the “smart‑browser” model popularized by tools like Perplexity’s comment browser. - In a live demo, the assistant successfully generated and styled a PowerPoint slide deck—handling layout, color schemes, and content expansion—though it struggled with finer formatting details such as precise text‑color placement. - The reviewer found Atlas to be the most practically useful AI‑browser utility they’ve seen in a while, noting its ability to execute commands (e.g., adjusting font size) while the user multitasks across other tabs. - While Atlas isn’t yet powerful enough to dethrone Chrome, the reviewer is bullish on its development trajectory and the broader possibilities of an AI‑driven browser modality. - The tool shows promise for automating repetitive web tasks (e.g., folder creation, content editing), potentially freeing up significant time for users. ## Sections - [00:00:00](https://www.youtube.com/watch?v=9ydIVzh7TBo&t=0s) **OpenAI's Atlas Browser Review** - The speaker explains OpenAI’s AI‑enabled Atlas browser, showcases its sidebar chat assistant creating a PowerPoint presentation, and highlights its strong styling assistance alongside its formatting limitations. - [00:03:11](https://www.youtube.com/watch?v=9ydIVzh7TBo&t=191s) **Leveraging LLMs for Linear Browser Tasks** - The speaker advises assigning low‑ambiguity, linear tasks—like folder creation, writing assistance, and simple spreadsheet calculations—to browser‑based language models to ensure they perform effectively and reduce user frustration. - [00:06:21](https://www.youtube.com/watch?v=9ydIVzh7TBo&t=381s) **AI Browsers and Prompt Injection Risks** - The speaker warns that AI‑powered browsers, while useful for summarizing web content and interpreting media, are vulnerable to prompt injection attacks that can exploit any text on a page, raising unresolved safety concerns about their rapid, unsupervised use. - [00:10:03](https://www.youtube.com/watch?v=9ydIVzh7TBo&t=603s) **Invitation to Share Opinions** - The speaker expresses curiosity and encourages the other person to provide their perspective or information. ## Full Transcript
0:00OpenAI heated up the browser wars by 0:02launching their browser that is AI 0:04enabled called Atlas. I'm going to get 0:07into what they launched, what the 0:09promise was, and where I think it works 0:10and where I think it doesn't. So, first 0:12off, what did they launch? It is a 0:14browser that looks a lot like Chrome or 0:16any other browser you might use, except 0:18it has a chat assistant in the side. In 0:20this sense, it's very similar to other 0:22smart browsers that have already 0:23launched. The comment browser from 0:25Perplexity comes to mind. Exactly the 0:27same idea. You just launch it in the 0:29sidebar and you do your task with the 0:31chat and then you have the main browser 0:33pane just the way it always is. I can 0:35actually show you what that looks like. 0:36So, here we are in the browser. I'm 0:38actually working on a presentation about 0:40the browser. I realize that's super 0:42meta, but you can see I have a little 0:43chat here, right? And you can kind of 0:45interact with the chat. In this case, 0:47what I had the agent do is to help me 0:50create the PowerPoint presentation about 0:52the agent. And just to be transparent, 0:54it was able to lay out the styling. So, 0:56it got this green and this blue 0:58highlight uh really effectively. It was 1:00able to lay out the title. It was able 1:01to lay out the dark background look very 1:04professional. It also was able to take 1:06and expand the copy really effectively. 1:08Where it didn't work as well was it 1:10struggled with some of the details of 1:11formatting. I know this doesn't look 1:13like fancy formatting, but just to be 1:15transparent, getting it to do white text 1:17on background was not something it was 1:20super good at. But that's a minor 1:22nitpick, right? I don't want to go into 1:23that. I want to talk about the larger 1:25theme here. I wanted to try something 1:27that was a real life task and just to 1:29play with it and see how it worked. And 1:31I got to say this is closer to useful 1:33browser utility with AI than I've had in 1:36a while. And that's what makes me 1:37bullish on the trajectory here. I don't 1:39know that this browser by itself today 1:42is knock it out of the water. 1:44Incredible. We're going to dethrone 1:45Chrome. But I see the trajectory that 1:47this team is shipping on and I'm super 1:49interested in where they go next. And I 1:51do think there's some really interesting 1:53opportunities in the way this browser 1:56modality works. So the way it interacts. 1:58So for example, if I say 2:01uh please adjust the font size on this 2:05slide, it's going to take that challenge 2:09as we chat and actually start to do 2:12something. You can see it start to 2:13organize and turn the sparkles on and 2:16actually do something with my screen 2:20while I go and do other work. And so if 2:21I go and I look at other things, I can 2:25come back later. If I go and look at my 2:29LinkedIn, for example, I can then come 2:32back to my slide deck and see that it 2:34continues to work. Ironically, what the 2:37slide deck is showing is one of the 2:38things that I think is most useful here. 2:41Think about the boring work that you do 2:43on the web. Things like automating 2:46folder creation. That takes a lot of 2:48time. You can do that work much more 2:50easily if you just open a tab and you 2:52ask this browser to do it. Similarly, 2:55you can think about the work you would 2:57do as a writing coach. You can see it 2:59has these issues, right? Like it 3:00actually made it worse. And this is why 3:02I don't want to overpromise it. This 3:04thing does struggle with some of the 3:06aesthetics and some of the direct tasks. 3:08I also asked it to book a yoga class for 3:11me. It eventually got through, but it 3:13was about 10 times more painful than 3:15booking it myself. And so I look at 3:17these situations and I say, where are 3:18their linear tasks that I can get into 3:22that enable the browser to be at its 3:25best, not at its worst. And so instead 3:28of throwing it into something that has 3:30fairly high ambiguity, like a 3:31PowerPoint, how can I give it a task 3:34where it's set up to succeed? In this 3:37case, creating folders is super linear. 3:39You can't screw it up. You create the 3:41folder, you name the folder, and you're 3:42done. Another one that I think is really 3:44effective is being a second pair of eyes 3:47on the screen. So, if you're writing 3:49something, can it be a Grammarly or 3:50writing coach for you on the side? I 3:52realize that there are probably people 3:54at Grammarly that will hear this and 3:55sweat bullets, but like I think it's 3:57fair. Like, it can literally look at 3:58anything you're writing on the web and 4:00give you a fairly thoughtful writing 4:02critique. I think that's a great use 4:03case for it. I think another great use 4:05case is just letting the LLM do the 4:10planning and thinking for you where you 4:13have complexity. So, a great example is 4:15look at this spreadsheet, perform some 4:17simple calculations off the spreadsheet. 4:19I don't really have time to and then 4:21come back. As long as it's in the 4:22browser and it can see it, it can do 4:25that math for you. That can simplify 4:27budgeting. That can simplify financial 4:29tasks. it can simplify a lot of the 4:31basic math and thinking that we do 4:34around the web because a lot of it 4:35happens in the browser anyway. A 4:37creative one that I've come up with, I 4:39don't know, you you tell me if you think 4:40this is effective, but in theory, this 4:43should work really well for time 4:45tracking because you should be able to 4:48investigate time spent per site or task 4:51by interacting with the browser around 4:54what you were actually doing. And that 4:55brings up one of the most powerful 4:57features about the Atlas browser, which 4:59is it remembers more about you the more 5:03you use Atlas. And so it will have an 5:06Atlas specific memory set that is 5:08private to you. They say where if you 5:11are interacting with the browser more, 5:13you get more value. The browser knows 5:15you better. The browser knows your 5:17previous chats. It knows the previous 5:20places you visited and it understands 5:23what you are trying to do because it has 5:25seen your work already. So those are 5:28some of the positives. If we turn around 5:29and we look at some of the difficult 5:31things, I think you saw some of them in 5:32the little demo I gave you. Like there's 5:34some challenges around ambiguous tasks 5:36like PowerPoint deck creation. I think 5:38there's also an unclear use case around 5:42the value of the utility they're trying 5:44to go for. So to unpack that, if it 5:47books your yoga session for you in 20 5:50minutes instead of you taking 2 minutes 5:52to do it, is that really adding value 5:54even if it is doing all the work? I have 5:56questions. Another example, if it is 5:59going to be able to shop for you, do you 6:02lose the pleasure of shopping? Do you 6:03lose the pleasure of planning the trip? 6:05Planning the trip is one of the things 6:06that is right on that browser's 6:08suggested use case. So, we have to think 6:10about what we want to do and whether we 6:13want to delegate that task to an AI 6:15browser. And that's going to become a 6:17very real thing because this is not the 6:18last update we'll see on this browser. 6:20This is not the last browser that's 6:21going to launch. AI browsers are a big 6:23thing. And that brings me to my final 6:26question, which is what about security? 6:29Because right now, these browsers are 6:31taking in the text from a website. 6:33That's actually one of the great use 6:34cases for them is they can summarize 6:36text on a website. that you can use them 6:37to look at YouTube videos and tell you 6:40what's in the YouTube video. You could 6:41probably do that for this video. But if 6:44you use them to do that and you are on 6:46the wrong kind of page, a prompt 6:48injection attack is possible. If someone 6:50has put text on that page that instructs 6:54an LLM to do something malicious, the 6:56LLM in the browser, it's not clear that 6:59it can distinguish that. In fact, there 7:01are known vulnerabilities in other AI 7:03browsers that I expect would persist 7:06here where the browser will treat every 7:09piece of text it gets on the page, even 7:11malicious text, as part of the prompt. 7:13And then where are you? Because at that 7:15point, it just follows the prompt and 7:18the prompt injection attack succeeds. 7:20And so, it seems like the LLM browser 7:23builders expect us to just watch these 7:27things browse around the web very 7:29slowly. And that's how we protect 7:31ourselves from prompt injection attacks. 7:33But to actually have value, we need to 7:36not have to watch them. They need to get 7:38faster and we need to not have to watch 7:40them. And it's not clear to me yet how 7:42we can show and demonstrate safety. And 7:45I know the teams at Perplexity building 7:48the Comet browser, teams at OpenAI 7:50building this browser, they care deeply 7:51about security. So, I'm not suggesting 7:53they don't, but I'd like to see the kind 7:55of browser safety card development that 7:57we've had with model safety cards where 7:59we start to say, you know what, we know 8:01this browser is safe in these ways 8:03because we've tested it for these 8:05vulnerabilities. This is the known risk 8:07for this browser and this is what you 8:09should use it for. because otherwise I 8:11think there's an assumption that either 8:13the browser is default safe which is 8:15what Chrome has taught us and that's 8:17dangerous here or there's an assumption 8:18that it should never be used which I 8:20think is also an overreaction. I do 8:23think there's real value here for what 8:25I'm going to call boring web work that 8:27is low ambiguity. If I want to just set 8:29it to do something very linear like 8:32click around and triage my email for a 8:35long time in the background and I'm 8:37going to go off and do something else 8:38and I don't care and it's fairly low 8:40risk cuz maybe it's just making folders 8:41for email. Fine. It can go do that. 8:44Anything that is like that where it's 8:46like you can't screw it up. You just 8:47have to logically follow the task on the 8:49web for a long time. It's going to be 8:51great at that. And that's fine with me 8:53because we humans don't love doing that 8:54work. So if it wants to pick that up, 8:56that's great. So overall, my grade for 8:59this browser C plus B minus maybe it's 9:02not really at a point where I think it's 9:03going to overtake Chrome, but it is much 9:06much better than the web browsing value 9:09I've seen from OpenAI previously. So 9:11agent mode, I didn't get a lot of value 9:13from it. This is definitely better than 9:15that. And so I see the trajectory of 9:17this team and I could see in 6 months, 9:19this is a really interesting browser. If 9:21you want my quick take versus Comet, I 9:23still prefer Comet a little bit because 9:25I think it has some data inputs and 9:27outputs on key sites that make it 9:28useful. I use it for LinkedIn a lot 9:31because I can see pending invitations 9:32through the Comet browser and it's super 9:34helpful. It also has great plugins to 9:36calendar. I expect that will get fixed 9:38with this browser, too. But it's not 9:40there yet. And I find that the speed I 9:42get from that direct data input output 9:44is useful. I think we're going to get to 9:46a two-speed web where we're going to 9:47start to see those data inputs and 9:49outputs becoming very useful for agentic 9:52browsers where they're available and 9:53we're going to see slower service sort 9:55of off-road service where the browser 9:56has to use the UI. That's my first 9:58impression. What did you think of Atlas? 10:00I'd be curious to hear.