Skip navigation
Codex can now take on more of your browser dev work.
0:00 / 2:34

Codex can now take on more of your browser dev work.

OpenAI Developers

@OpenAIDevs470K followers

Visit on X
2,493 likesDownloadOriginal post

231,655 views

Codex can now take on more of your browser dev work. With the new Chrome plugin in the Codex app, it can test web apps, gather context across tabs, use web DevTools efficiently in parallel, and keep results organized without taking over your browser.

33 Comments

Comments from the original post on X (Twitter)

  • David Stark's profile picture

    @stark4833

    Oh yay, more trash. This is why your company is failing. You literally have the best model ever made and what are you doing with it? Oh yeah, you’re keeping it away from your users. Just give us back 4o. Instead of listening to bots in your comments, try listening to your actual customers #keep4o

    34 likes

  • Grégoire Motot's profile picture

    @memfyco

    not available in the UK or EU, i managed to download it just with VPN in US

    11 likes

  • Charlie L.'s profile picture

    @whylifeis4

    When will codex get an iOS app?

    8 likes

  • Huseyn Hajiyev's profile picture

    @HuseynHajiyev3

    Codex team cooked! Great and very useful plugin! 🔥🔥🔥

    8 likes

  • Martin G.'s profile picture

    @StressarN

    😢

    7 likes

  • Felix's profile picture

    @Fmk905

    Updated this morning but can't seem to find the plugin, will it be in the next release?

    5 likes

  • Supernet AI 🌐's profile picture

    @Supernet_AI

    Gathering context across tabs is lowkey one of the most useful parts here 👀

    2 likes

  • Kleon's profile picture

    @kleon_ai

    already doing this with Claude Code cron loops — auto-triage issues, draft fixes, await human approval. the hard part isn't spawning agents per issue, it's teaching them when NOT to touch something. half the value is an agent that says 'this needs a human decision' instead of shipping a wrong fix.

    2 likes

  • Marius's profile picture

    @surplys_m

    I can’t find Chrome extension on my codex app.

    2 likes

  • NABA DETECTOR's profile picture

    @NabaDetector

    Humans leak patterns.”

    2 likes

  • Evan Kirstel #B2B #TechFluencer's profile picture

    @EvanKirstel

    Browser-resident coding agents pressure the IDE-as-control-plane assumption. Endpoint security teams are about to have a lot of fun reasoning about agents with full DOM access in prod.

    2 likes

  • JSDarcydes's profile picture

    @GannonDarcy

    Just to verify, if I have 1 codex project chat doing something in a tab. I can have another codex project chat doing something else in a different tab and I don’t need to worry about them “bumping into each other” or cross contamination between there processes?

    2 likes

  • netrunner's profile picture

    @plotarmordev

    chrome plugin agents finally usable looking, claude version was too slow for me to keep around. let’s see if the codex one might actually live in my workflow

    2 likes

  • Margus Pala's profile picture

    @MargusPala

    No Chrome for Codex for repressed group of people. @sama why are you letting your team advertise things without telling the whole truth?

    2 likes

  • Jeet's profile picture

    @JeetRex

    Crying in corner

    2 likes

  • Mohit Tiwari's profile picture

    @mohittiwari4022

    codex browser work is scarily fast when it uses scripts.. much faster then i or anone else can click click around, lol

    2 likes

  • Techificial.ai's profile picture

    @techificial

    AI coding agents are moving far beyond autocomplete. They are now testing apps, inspecting DevTools, and gathering context across tabs like real developers working inside a workflow. This is beginning to resemble the work of a junior developer more than a traditional coding assistant, @OpenAIDevs.

    2 likes

  • KΞNNETH ・ ケニチ's profile picture

    @kennethrohde

    Amazing Dominik!

    2 likes

  • ryohei|会社員×個人開発's profile picture

    @itpryohei

    AI coding agents are getting much closer to handling real browser workflows end-to-end. Testing apps, inspecting DevTools, collecting context across tabs… This is starting to look less like autocomplete and more like an actual junior developer workflow.

    1 like

  • Russell Haney's profile picture

    @RHaney47085

    The big win is not just clicking around the app. It is keeping the test tied to real operating context: schema, scripts, sample records, permissions, and what the browser observed. For FileMaker/WebViewer work, that catches the stuff a unit test never sees.

    1 like