We thought AI agents were smart, but what if they could truly see the world like we do? We dive deep into the fascinating (and sometimes frustrating) world of AI browsers like Comet and the groundbreaking operating system, Warmwind. Discover why some AI is better at background tasks and why others struggle with simple web forms. It's a proper peek into the future of how AI sees the internet!
Discussion in this weeks news in AI, web and design with @Kabarza and @0x5am5
Try Flowbase.co and use CMDFLOWBASE for 20% off
🎙️ New to streaming or looking to level up? Check out StreamYard and get $10 discount! 😍 https://streamyard.com/pal/d/4597668583964672
#AIAgents #WarmwindAI #CometBrowser
Transcript
But I actually spoke to the AI agent in read and asked the AI a it's the AI that asked AI to like make that change sort of thing. Comet has finally launched. This is uh an AI browser and it does the job of which I I think is something that deer is not launched with which I was particularly excited about is the agentic thing. You can actually ask it to do stuff and it will go off and it will respond to emails and this and that and the other. We have Max here. We talk about warm wind and the opposite side of it which to give an insight into those who don't haven't heard or whatever. Warm wind is like an operating system. Is that right Max? Like it's it's not browser. It's actually a layer up from that. Yeah. Yeah. Well, well, the community is still debating if we can call it a operating system. But for everything except a custom kernel, this is a operating system. And yeah, we basically one layer path as you told and yeah, we're doing it um in a more general way. Basically, the thing that I like that Comet cannot do is this idea that you used an example of a like an old um real estate app that is just looks awful and Warmwind can actually go in and use that system because it's it can see the interface or whatever. It's not restricted by what's in the browser. Yeah, I mean definitely. I mean, not not I don't want to give you a feeling I want to trash on Comet because I I think it's a phenomenal product and I probably going to use it myself in the future, but I think it's like a completely different use case from from my from my perspective because obviously Comet a Comet is is something you would use if you have an like demand now. So you you would like to have your emails answered or whatever and it's highly dependent on your machine. So your laptop has to be on and while while that's on and you have the browser open it's it's working. I guess that's I think that's how how it goes, right? Yeah, pretty much. And and the whole thing that or how I like to discriminate what what we are doing is everything that's not on demand. So basically background tasks you set it up once and then just it it goes off and do thing does things for you in the background while you're not even there. Typical tasks are more like whenever an email comes in, whenever a new order gets created, every day at seven o'clock, every day at nine o'clock and because it's a completely independent operating system and it's spun up on its own server. So we have these microservers and for every instance like we call them spaces, uh a microserver gets created. Um you get the ownership of the this microserver and then it's doing things for you even while you're not online. So you would basically be able to shut off your uh PC because it's basically it has its completely own machine in in which it can operate. I've been I've been using um Comet the last like day or so like as soon as the email came in I started using it and what I did do is I was I had I was updating a CMS in uh web flow. I was like put the information from this web page and put it into the CMS in web flow. And what I found was is that the it it's reasoning about the web page. So it doesn't know which buttons to press. Long story short, it couldn't figure out how to insert the information into Web Flow, but it did it tried a bunch of stuff and ultimately failed, which then led me on to this idea that it it feels like it would be very good for background tasks as well. Uh, I I just found that because it just doesn't know the web pages and it's trying to just again just figure out the whole picture and and whatever and click certain buttons or whatever that it's like it's not it's it's not going to save you time in the immediate future. It's just again it's a background thing. One thing that was really interesting that happened was I was doing some of the shorts that we were making for this show and I was using V, which adds subtitles, and I just said, "Can you make all of the because it did it in American English, so zeds instead of s's and things like that. Uh, can you do that?" And I thought it was just going to go in and click the words and do a spell check or whatever, but I actually spoke to the AI agent in Vid and asked the AI, it's the AI that asked the a AI to like make that change sort of thing. So, it was really funny. But all that to be said, the background thing is certainly I think the way that these sort of sort of things go. Well, actually I I think we are also very very um hyped about this AI layering because what what is super interesting is um obviously when you just want to get some information web search is much faster than like the agent going into browser and searching individual websites. So what we see a lot of users which are currently testing it is doing also installing the offline app or not not offline but the like a PC app for uh for for JBT and and that this is like the best way to get a lot of informations um quickly because web search is always a lot lot a lot slower and what I think will will happen in the very near future um that something like arc or the dia browser will also be just used inside our system. So AI is to talk to AI. What would interest me in that aspect is do you guys only evaluate the visual aspects or do you guys also let's say if you have a browser you always also import the entire HTML into the context. Yeah, I think that that's one of the biggest um differences. So we we actually only use completely vision based interaction. So there's no because we we don't work with with a spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe specific browser or anything. So we are not so deeply integrated in the browser. We are not only supporting web apps. We support everything that runs anywhere. So um to be this general you have to go to a to the layer where humans work. So completely visually uh basically and this this this allows for for a lot more met data and and understanding to to to transfer over to the AI brain basically. Um, but I think what what happens for for Comet right now when you talk about the CRM test is because one and a half years ago we also tested with HTML context or or the DOM tree uh and looked at um the the HTML elements and how how we could click on them. Um but but as it as it turns out the the HTML page um this information lacks a lot of context because only once you simulate the whole whole JSON JavaScript uh code the whole HTML buildup and rendering process then the website gets created and only after this whole creation process things get into context. So you see okay this button is slightly over this image. So this means probably when I click this this will open the image and not the thing below that. So there are a lot of clues which which happen on a vision base um which you could not do uh just with with a browser or or with with a code code examination. Basically this is part of a larger conversation on my show command AI which we stream live every single week. We discuss the news and all things related to AI in the world of design and web.