Today, we launched browser use inside Codex to further close the build & verify loop for local development! Now, you can ask Codex to build your front end, and test it like a user would by clicking through the app. Codex sees everything a user sees through vision &... checks the network/console logs to help debug & fix any issues that it finds. This change brings us closer to fully autonomous coding agents that delivers high quality and tested changes. Watch Codex test my app in the browser, catch & fix a real bug, and doing that loop again with a brand new feature.show more

Browser use is also useful for pulling up reference materials like docs in the in-app browser and answering questions about them while you work!

We need to be able to auth inside codex so we can login Gmail and use like user

Tracking and working on it!

Damn this is sick Access to network & console logs is gonna be super good for it being able to debug stuff properly

Thanks Jarrod! It's really cool to see Codex self-verify and keep iterating until things work

Also... Scratchpad? 👀

👀

Being able to watch codex do this is so so satisfying

James - a few issues I had with the in app browser. When it works it works. But if you have an mcp for playwright or chrome dev tools it will often ignore the instructions to open up specifically in in app browser. Also, there are sometimes connection issues - submitted feedback.

We are trying to not make this too aggressive until it’s more tested, so it will often prefer your existing MCPs! Let me know if you prefer it over your existing tools

Definitely prefer this over other mcps. One other slight enhancement - view ports. Often the fixes are for mobile or desktop. So an easy toggle makes the annotate feature even easier. Thanks James!

how did codex only get this now 😂

Super useful!

how many "instances" of this can we have running?

I haven’t hit a limit yet with testing, try it out and let me know!

Nice 👀

I had a new idea so told codex to prototype it. Without asking for it it fired up the browser and fixed a few broken things I normally would have to add in follow up. Insane! Would be great if it remembered the expanded state of the panel though 😅

can't wait to try it out for all the UI dev

I used this today at work. Left to get food, came back everything was working. Felt like magic!

Can we log into sites with this and if so, do the logins save? This is the biggest pain point I have with Codex atm.

Damn this is soo sick Access to network & console logs is gonna be super good for it being able to debug stuff properly KEEP Going🔥

it's dope! congrats!!

You guys are cooking.

This is probably the right direction. The part that always bites is not the click through itself, it’s making failures legible when state gets weird or the UI half-loads.

Bring the app to Linux 🤞🏻

@npew 👏

I will finally fiddle with gamedev in this and convert to Electron later. I saw people doing this for vibe gaming jam and it looked beautiful. Awesome work James!

The vision + console logs combo is smart. Most agents fail at the 'does it actually work' step - this seems like a real answer to that gap.

I tried it on windows and it not working at all 😭

James, it does seem to very cool! Some feedback: it seems to swallow the downloads (or at least it puts it somewhere where codex app can’t find) on Mac. The likely root cause: download presents a system save dialog, which is not visible when using built in browser.

Please add support for a visual git tree and database viewer. That would be the greatest!

Its look like website editor

This is a very useful feature. Going to test firsthand with a multi agent runtime

is this sped up?

yep! I sped up the sections where it was writing code!

but not the browser use sections? i’m amazed by how fast codex can navigate the radio buttons. i haven’t yet tried windows browser use but fingers crossed it’s similarly adept

I think the browser use section is only 1.2x! It’s pretty fast, and we have ways to make it even faster next week :)

Didn’t know this was included until the browser popped up. Great addition and annotations. Top marks!

I would like to be able to use Apple’s Passwords AutoFill with the Codex Browser

QoL: 1. make it easier for agent to navigate with simple tool calls. the code mode/repl thing feels off and crashes some, and/or: 2. codex browser should be env default, so things like `open localhost:3000` open in codex browser (not system default)

Is there mobile /remote control yet

Codex now builds, tests, and fixes like a real user, closing the loop.

This is great thing. I tried yesterday. I will use it

For cli, is chrome devtools mcp still the best way to test the front-end

@browser_use I sense it's you under the hood? 💀👀