I let Codex control my browser so I don't have to

1. 0:00 – 1:46

   Intro

   1. CVClaire Vo0:00

      One of my favorite guests ever, Jesse Genet, said that AI was great for moms because moms' hands are always busy. We're always doing something with our hands, and we do not have time to talk. Now, in that episode, she was talking about the benefits of chatting with AI. But in this episode, which I'm gonna lovingly call Look Ma, No Hands, I'm gonna talk about browser and computer use, the way that you can let AI navigate your computer and navigate websites to get work done on your behalf. Browser and computer use have gotten exceptionally good recently, especially in my experience with Codex and the GPT 5.6 models, and I'm gonna show you a builder use case, a productivity use case, and a personal fun use case that I found super useful in using computer and browser use. Let's get to it. This episode is brought to you by Runway, a new kind of creative platform that has everything you need to generate any image, video, or piece of content you want, all in one place. With Runway, it's now possible to go from initial idea to a finished deliverable in a matter of minutes. From turning low-fidelity product shots into campaign-ready imagery all the way through putting together big brand films, Runway can help your team scale your creative ambitions while keeping your budgets and timelines from doing the same. Runway brings together the world's most advanced AI models, which is why enterprises like Microsoft, Robinhood, Amazon, and Adobe, along with studios like Lionsgate and Legendary, all use Runway to ship real work every day. Try it yourself at runwayml.com/howIAI. Promo code HOWIAI.

2. 1:46 – 3:08

   What browser use and computer use actually are

   1. CVClaire Vo1:47

      Okay. Before we dive into how I use computer use, just a refresher for anybody who's new. In case you missed it, these LLMs, your AI chatbot, can control your computer and can control your browser. Now, there have been a class of AI native browsers that have come out in the last year, thinking about Perplexity's Comet or ChatGPT's Atlas, but I like to use browser and computer use directly through Claude, or in this instance, Codex. Why have I used Codex, specifically the Codex desktop app, or I guess we're calling it the ChatGPT desktop app, these days? Well, it is just the best at controlling my computer. And if you didn't know, it can control the mouse, it can control the keyboard, it can do all sorts of things. So imagine you have a virtual coworker, and that coworker can put its hands on your keyboard and get stuff done on your computer. That is what browser and computer use can do. Now, this sounds really scary, but in fact, it has been one of the most life-changing [chuckles] features of AI. Certainly professionally changing, but has also reduced so much personal toil and personal digital toil that I had to tell you about a couple of the use cases that I use because I literally use this every minute of every

3. 3:08 – 4:15

   Why I use Codex specifically and how the desktop app plus Chrome extension works

   1. CVClaire Vo3:08

      day. Now, invoking browser or computer use is pretty simple. First, you have to have those desktop apps installed on your computer. So whether those are the ChatGPT desktop app or the Claude desktop app, you need those installed. If you wanna use the browser, you need to have the browser extensions installed inside Chrome. I don't know if they work for these other browsers. I just use Chrome, and I know they have browser extensions. So you can just search for, for example, Codex browser extension or Claude browser extension, make sure they, they're the official ones, and then install those, and then these two things together, the desktop app plus the Chrome extension, can really allow your computer plus AI to do a lot of work on your behalf. Now, it sounds really simple. Let your AI use your computer. But the trick, and this is the How I AI sort of mantra, is you have to find a good use case for browser use. And having used browser and computer use for a while, I think I've come up with a couple unique and interesting use cases that maybe will inspire you and give you some ideas about how you can use it

4. 4:15 – 10:41

   Use case 1: QA testing my onboarding flow

   1. CVClaire Vo4:15

      in your work and life. We're gonna start with a use case out there for all the coders and all the vibe coders and all the professional software engineers, which is using browser use alongside a coding agent to validate changes. Now, this is very simple, but one that I use quite a bit. So what I'm showing here is the ChatPRD onboarding flow. It's just a step-by-step where you fill out your profile. Let's say I was working on some enhancements on this feature and really wanted someone, and by someone, I mean GPT 5.6 Soul, to validate that all those features work really well. Now, I could write what AI loves, a smoke test. I can definitely test things on the back end. I can definitely write tests for the front end. But what I really wanna know is, is it usable? Can we use it? And so what I might do here is say, "Use browser," and there are three ways you can invoke kinda computer use in Codex. You can do @browser. That will pull up use of this side browser window. There is @chrome, which will use the Chrome extension to manage Chrome. And then there's @computer, which lets it manage the whole computer, just, just so you know. But I'm gonna say use browser 'cause I'm already logged into my localhost over here on the browser. I'm gonna say, "To test the open onboarding flow for usability and mobile responsiveness. Please screenshot as you go and make a Google spreadsheet of any issues you identify." Okay, so I'm gonna click Submit and let that run, and what that's gonna do Is spin up the browser skill, which is embedded in Codex, and you'll actually see this little cursor start to go over to the browser side and walk through the onboarding flow. Why I think this is useful is this is how I would test if this is working. You know, I would go through, I would click, I would test all the dropdowns, I would change the viewport sizes. And what's really nice about browser use in this instance is all of that can happen automatically. I can just sit back and watch it go. And I will tell you, it's really fascinating to watch these things go. If you have looked at that little glowy cursor and watched it bop around your website, click things, test things, you know the magic feeling of this particular AI feature. Now, what I love about using browser use specifically for QA purposes is it is exhaustive, or it is more exhaustive and organized than I as a human would be. I don't know about you all, but when I am QA-ing things, I like to do the happy path QA, where it's like, yes, I fill out all the form fields, everything's required, I click next, I don't get tired, I don't go back. But you can see here my little glowy Codex browser icon, it's gonna be exhaustive. It's gonna test signing up with a team, it's gonna test signing up as an individual, it's gonna fill out form fields, it's gonna try for error states. It's gonna do all these things that you wouldn't probably have the stamina or organization to do if you're like me, a little late in the afternoon after coding and asked to sort of manually test your web app. And so what I really like about this is its ability to be exhaustive. Now, if I were being a little bit more organized, I would probably have it come up with a suite of test cases based on the code, then go through those test cases kind of specifically over time so I knew it was being exhaustive. That being said, you know, side tip for some of these newer models, I actually found that under-prompting these models gets you a much better effect than over-prompting them. And so because they're so intelligent, you can literally just tell them, "QA the onboarding flow," and it will do a much better job than saying, "QA these 25 things in the onboarding flow." So a little tip, under-prompt your frontier models. Let them use their... that intelligence to come up with their own plans and do what it wants to do. Now, we're gonna watch this a little bit, and what I like about what I've told it to do is it also is being asked to look at responsive design. And even seeing here, I see an issue with the, um, right hand of the browser. I'm curious if that's actually an artifact of how this responsive browser inside Codex works, or if it's an issue with my responsive design. We will see. But you can also see that it's changing the dimensions of the viewport, so the size of the monitor, to match laptop size. It's gonna show matching a phone size, all those things. Again, things that I could technically do manually that I really don't wanna do. I'm gonna let this run, and then I'm gonna show you one other use case as a builder that I think is a little bit more unique that you might find inspirational. Okay, so something interesting here. It did find an issue. Now, I'm a little embarrassed because this onboarding flow has been here for a while. Um, it surfaced one blocking issue, which is if you don't select anything on this page, you can still click Continue, but it won't move forward because one of these fields is required, but there's no validation code in here. Now, again, the reason why this bug exists is because I always tested this flow as a human, and I always clicked the required buttons. So again, these benefits of having AI test your flow is it will test failure states as well as success states and actually bubble up edge case bugs that you might not have thought of. And so it's gonna continue through and actually work and go to the next screen. I'm curious if it will spin up mobile testing next. Okay, you can see now it's also switched to mobile testing. Again, this is something I would probably give a cursory glance to, like I would make the browser smaller and then kind of click through stuff and make sure it works. But what I really love about browser use is, again, it's going to be just a lot more exhaustive. It's going to look at things like accessibility, it's gonna look at overflow, it's gonna look at touch targets, all that kind of stuff, and just has a much more organized sense of what makes for good mobile testing.

5. 10:41 – 12:10

   Results: 11 issues, one high-severity blocker, one Google Sheet with screenshots

   1. CVClaire Vo10:42

      Okay, so it wrapped up. It found 11 items, including one high-severity navigation blocker, the one we talked about. And now this is one of my favorite things that I do with AI, is I just have it make me a Google Sheet or a Google Document, and it's gonna make me one with this prioritized, and then what I can do is use that Google Sheet as a tracker to kick off a bunch of fixes and track the status of them with sub-agents. So again, this is a very comprehensive QA that was done. I get this beautiful list of issues that came out. I can get those fixed ASAP, and it ends up in a sheet. Okay, so it wrapped up, and it did everything I asked it to. It tested it in desktop and mobile. It gave me these beautiful screenshots telling me it would work, and it even made a spreadsheet. Let's see if this spreadsheet is actually... If I can pull it up. So I love this flow, this workflow, which is to have Codex make you a spreadsheet of issues that then it's gonna go fix. And so it has this nice summary. It found 11 issues, one that was high severity. It listed out all the issues. Again, this is really useful for agents because it has all the information it needs to reproduce the issue, the viewport, what the issue was. What the steps are to fix it, and then how to remediate it, and then look at this. It put all the screenshots here in the spreadsheet so I could reference them and even compare them to fixes. So this is just a very practical use case of browser use that

6. 12:10 – 18:20

   Use case 2: persona testing

   1. CVClaire Vo12:10

      I think is really nice. But what I wanna show you is the same thing, but a slightly more fun use case. So I'm gonna go in here, I'm gonna go to the core of ChatPRD, and I'm gonna show you a use case that my husband came up with. I have to give him credit, my husband, EJ Lawless, [lip smack] and he uses browser use to impersonate specific personas of his applications and then give feedback as the persona. So let me just give an example of what this might look like, and I'm gonna pull up Monologue and just speak my prompt. I want you to go through the core of ChatPRD's chat and document creation mode as two different personas. Actually, three different personas. I want you to do one as a product manager trying to quickly create PRD for a feature that they just got out of a meeting, um, about. The second thing I want you to do is impersonate a engineer who is taking that already created PRD and trying to make a technical spec out of it, and eventually a prototype. And the third thing that I want you to do is, as a team leader, try to figure out how your team is using ChatPRD. I'm gonna give you no more instructions than just that. I want you to go through those three persona use cases and flows, and then I want you to create a doc providing research style critique about the overall experience, including friction points, places of delight, and improvements you think we can make to serve those three personas better. Okay, so I got that prompt in. I'm gonna click enter. So just to, like, reiterate what this is, if you have personas and you want to test against those personas... Now, like, I'm not a big synthetic user girl, but I do kind of like this framework. We used to always do this with our prompting, where we're like, "You are a genius product manager," or, "You are the best software engineer in the world." Now I'm using that, but I'm using browser use and saying, "You are a persona type. Use my application as that persona, and then give me research as you go through the browser experience about what you like and don't like." So I'm gonna let that run a little bit, and then I will show you what we come up with when it's done. As you can see here, it's going down the PM path. It just put a fake prompt in that says, "Hey, I just got out of a customer design meeting about a decision digest feature in ChatPRD. Here are the problems. Here's, like, kind of what I want. Here are some open questions." And now it's watching ChatPRD create the document. I'm really curious if it will actually analyze the quality of the document itself or not. You know, it's giving me good positive feedback as we go, but we're gonna watch this. We're kind of like speed through some of the, the browser use. I will say one downside of browser use is it's kind of slow. So honestly, when this is running, I typically open up something else on the side and, like, work on something else as the browser is, is running its flow. But it's gonna go through and give me an analysis as that first persona, and then we're gonna see it work through the rest of them. This episode is brought to you by Hyperagent, the platform for deploying always-on agents that actually run your business. With Hyperagent, you build agents in the cloud and deploy them where your work already happens, like Slack, Telegram, or email. An agent will scan your inbox and draft replies to vendor follow-ups. Another monitors competitors and spins up rich ad kits and landing pages. A third notices a deal going cold in Salesforce and writes the save email with full account context. These aren't chatbots waiting for a perfect prompt. They're proactive, learning your preferences, retaining your playbooks, and getting better with every run. One user built four agents to run an outbound sales pipeline, prospecting, outreach, follow-ups, CRM updates, all in a single afternoon. No local setup, no VPS bills, no fragile permissions on your laptop, just powerful agents with full control over skills, tools, and guardrails. Hyperagent was built by the team behind Airtable, and How I AI listeners get $1,000 in free inference to start building. Claim yours at hyperagent.com/howiai. Okay, so I love this internal kind of like chain of thought that you get with browser use. So what it tried to do was do the handoff from PM to engineering. And what you see here is that the engineer handoff exposed a structural break, which is a real issue in ChatPRD, which is you can create one document, but you can't like @ mention or reference it in another thread. It's something that we're working on or thinking through how we wanna reference. It works in a specific way, but obviously the agent here, the Codex agent, thought, reasoned, um, that this feature would work a different way. And so it's really interesting when you, you combine browser use with sort of this AI chatbot, how you start to inhabit the mindset of a persona or a type of user and actually identify really obvious but kind of like hard to get your head wrapped around friction points where someone with fresh eyes, again, these are agent eyes, I'm sorry, I don't know a better metaphor, um, might have a challenge. And so it went back to the document and said, "I'm the engineer picking up this PRD. Turn it into an implementation ready technical spec. We'll see what the experience is and if the agent is happy." Okay, it called out something really interesting here, which I don't know if it's an artifact of this running locally and something weird being happening locally, but it did call out that the loading screen was super slow and opaque, and the interface didn't really make it clear what was happening when it was writing. I think we hit an error, but this is really good feedback for me because again I wanna make sure even if we have a failure state, it's going to make sense, quote unquote, "To the user." So just to take a step back, I really love this use case of coming up with a persona that kind of inhabits the mind and, in this world, the body of your user, and then have them going through your website using browser use and giving you a report of

7. 18:20 – 20:37

   Use case 3: LinkedIn inbox, hands-free

   1. CVClaire Vo18:20

      what works and what doesn't. Okay, so those are my building use cases. I'm gonna zip through a couple other use cases that I think are kind of fun. So my favorite one, I've talked about this a little bit briefly before, which is browser use for LinkedIn. LinkedIn, close your eyes, close your ears, do not pay attention. But I like to log in to LinkedIn here in my sidebar, and then I like to say, "Please use browser to go through my recent unread messages and, um, reply to any that are super critical," can't type, "for ChatPRD or the podcast. Leave me notes here on the others about how I should reply. If this is just a friendly thank you note, reply in a friendly way." So this is just, like, the easiest way to go through the pile of LinkedIn requests I get. I love you all. Thank you for connecting with me on LinkedIn. I'm happy to be connected, but I get hundreds of these. And so I love to use browser use to just go through LinkedIn, click through stuff, read it. Again, LinkedIn doesn't have an MCP or an API that's official, so we're using unofficial channels here to go through stuff. One of the other things that I noticed is I am using high effort on 5.6 Sol for this. I probably can use Terra on medium effort, and it might be a lot faster. And so again, you can calibrate your browser use effort and level of intelligence to whatever you need. I was definitely overusing it for LinkedIn replying. Um, but again, you know, maybe it requires a little bit of work. All right, so as you can see, it's pulling up LinkedIn. It's going through my messages. Christie is my friend. We used to be, um, colleagues. She's asking me to meet with her CEO. We're gonna see it reply back a message, go to unreads, um, and then actually filter through this. So if you're like me, if you have tons of LinkedIn connections, LinkedIn comments, need to figure out how to get through this stuff, I love using browser use to go through those use cases.

8. 20:37 – 23:47

   Use case 4: AI personal shopper

   1. CVClaire Vo20:38

      Gonna wrap this up with a browser use case for the girls. Um, gents, others, if you want to use this one, please do, but I am going to use @Chrome. So I'm gonna show you how you use the computer use, but specifically for Chrome. So I've been using @Browser, which is the side, um, window of Codex. I'm gonna use @Chrome, and I'm gonna say, "I'm going to Hawaii this weekend, and I need new clothes. Good news!" Exclamation mark. "Free People has 25% off their sale. I would love for you to go through using Chrome browser use and pick out 10 items in my size. You can pick size medium that would be great for Hawaii. Remember, I'm a breastfeeding mom. I just had a baby six months ago, so pick things that are comfortable, that are breastfeeding-friendly, um, and that would be great for the weather in Hawaii in late July. What I want you to do is end up with 10 things in my cart that I can pick from and buy. Thanks." Always say thank you to your AI. Okay, so I'm gonna put that in. It should spin up. It's gonna use Chrome to curate 10 medium sale eligible pieces that are breathable, comfortable, and easy to nurse in, and then add them to my cart without checking out. And so again, this is something that can be happening over on the side. I do not need to think about it. I do not need to manage it or monitor it. It is... As you can see here, this little browser window will pop up and actually show you what it's doing. I think this is such a cool feature of Codex, is that it will actually show you what it's browsing. It's gonna go through the sale, and it's gonna pick out outfits for me. Now, we're off to a bad start because I did say that I was a relatively new postpartum mom, and it did pick a miniskirt. So I'm not quite sure we'll see what good fashion sense that 5.6 Terra has. TBD. But again, just, like, think about these kind of, like, annoying shopping use cases that you have to use a browser for that require a lot of, like, filtering and interaction, and you can just go through and have it shop for you. And now I'm gonna pull up this browser and show you... Oh, uh-oh. Bad news bears. Look, it thinks that I'm an agent, which I am. Sorry, this is much cuter. So you might have to be the hands for your AI. I tell people this all the time. Sometimes we put AI to use for us, and then sometimes we need AI to put us to use, and so sometimes I am just the human verification layer on top of ChatGPT browser use. So again, this is gonna shop. We will see how successful it is, if it adds stuff to the cart that I would really like. But again, I hope this is getting your mind open on what browser use and computer

9. 23:47 – 26:50

   Rapid-fire uses: forms, iPhone mirroring, router access from out of state, Google Docs

   1. CVClaire Vo23:47

      use can do for you. Okay, I'm gonna list just a couple other things that I use browser and computer use for that you might find interesting. One, filling out really, really annoying forms. So if you ever have to do procurement forms, if you have to ever, ever have to register your kid for camp, if you ever have to fill out an old, old, old website, um, browser and computer use is really great for you. Second one, browser and computer use can actually run your phone. I did this the other day. So if you're on a Mac, you have something called iPhone mirroring, where you can actually pull up a version of your phone on your desktop. Computer use can use iPhone mirroring. So your computer can technically use your phone. How did I use this recently? Well, I was out of state and my Mac Minis were sitting here on my desk here in California, and I needed to hack into my Wi-Fi, so I needed to open up some firewall gateways so I could remotely SSH in... Sorry, I'm just getting really nerdy. So I could r- like remotely SSH into my MacBooks and, like, revive the open clause, 'cause it wasn't on the same network. My Wi-Fi management software is on my phone, so I opened up Codex, I opened up screen mirroring, and I had Codex use computer use to set up the right settings on my home Wi-Fi, update my router, SSH into my MacBooks, and then close all the ports when it was done. It was pretty amazing. It was really good. So you can definitely use computer use to use your phone. And then the last thing that I do is I use computer use a lot to make, like, Google Documents and Google Sheets. So sometimes I'm just not happy with what is being used with, like, the MCPs and the plug-ins in Codex. So if it hits kind of, like, access use or it can't do something via an MCP, if you are permissive enough, you can just say like, "Please just open up my browser and do it in the browser," and it will do a very, very good job. So look, now my Free People cart has 10 sale items, all size medium, totaling $352 before sax- tax. The extra 25%. Um, what did it give me? A maxi dress, great. A skirt set, great. Loosey-goosey pants, amazing. Shorts, great. A T-shirt. Oh, look at this tag. Perfect. Perfect, perfect. A blouse, a button ne- a couple button-downs, a little V-neck. It did a [laughs] really good job. So this turned-- this started with, um, browser use as a, a debugging tool and ended with browser use as your personal shopper. Again, this is my favorite feature, y'all. If you have not tried it, especially with Codex, it is 100 out of 10. Everything is computer, and I really think that this is gonna change how we interface with our digital lives. And again, my goal for most of AI is I can be not on my computer and stuff can still get done, so I can enjoy my Hawaii vacation.

10. 26:50 – 27:40

    Wrap-up

    1. CVClaire Vo26:50

       This has been a very fun mini episode on browser use and computer use. If this is something you find interesting, let me know in the comments. I would love to hear how you use computer or browser use, what questions you have about privacy, what questions you have about security, and other things I can show you about how I AI. Thanks for joining this week, and I'll see you all soon. [upbeat music] Thanks so much for watching. If you enjoyed the show, please like and subscribe here on YouTube. Or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. Please consider leaving us a rating and review, which will help others find the show. You can see all our episodes and learn more about the show at howIAIPod.com. See you next time. [upbeat music]

Episode duration: 27:40