yesterday i showed claude code using codex's computer use, today i got some more fucking fire for you claude can also drive codex's official chrome extension, and it controls chromium browsers beautifully all in the background, without the "allow" popup chrome devtools mcp throws at you every time a... new agent connects it even handles more than one browser: each install of the extension gets its own instance id, so claude knows which is which i have helium as my main and chrome for work, and claude code now uses both first, install the chrome plugin in the codex app and add openai's chatgpt extension to your chromium browser (or all of them, if you have a few) then give this to your claude: "Set up Codex's Chrome extension for you on my Mac. I've installed the Chrome plugin in the Codex app and the extension. Use Codex's computer use MCP server as user MCP "codex-cu": keep it if it's already registered, otherwise copy the "cua_repl" entry from ~/.codex/plugins/cache/openai-bundled/unified-computer-use/ /.mcp.json. Its browser side rejects calls without Codex turn metadata, so put a small stdio proxy in front that adds _meta["x-codex-turn-metadata"] (session_id and turn_id as a JSON string) to every tools/call. Add a Stop hook that tells this session's proxy to call the hidden turn_ended tool and start a new turn_id, so your tabs get released without touching other sessions. Test it by opening a tab straight at a URL in each browser with cua.createBrowserTab(browserId, url). Browsers can all report as "Chrome", so if I have several, ask me which test tab showed up in which browser." got more than one browser and ok with it touching your claude.md? give it this too: "Write each browser's name and metadata.extensionInstanceId into my global CLAUDE.md, with a note to pick browsers by that id and open tabs straight at a URL."show more

brother you do not even need multiple browser apps. you can use multiple independent instances / profiles of chrome. when they launch into that instance / profile, they can be used simultaneously.

not how i want it to work

as in, you have specific reasons for using two different browser apps, then? if so, that's fine -- just was clarifying that it isn't necessary for simultaneous use

I got Claude Code, Codex, and OpenCode working together in the web. Not in parallel but in multiplayer. M9R also has native capabilities such as Claude and Codex communicating across their desktop apps and terminals.

dude adding codex's computer use to claude was a game changer! Thank you!

if you want the best in class computer use: I’ll collison-install cua driver for you and find the local optimum for your harness / model configuration

Thank you

seems like the capabilities of these AI models can't be fully explored atp this is amazing setup btw

does it reuse your existing logged-in chrome session?

yes it can

Driving the browser in the background without the allow popup is the part that makes Claude Code feel like a real unattended agent.

claude code using codex computer use, the agents are unionizing

Claude ain't never gonna get mass market adoption if small business owners have to do this s...tuff.

Keep em coming bro. Very helpful and efficent stuff

pffffuuu it didnt want to do it for the first time, thats awesome

后台跑还不用反复点允许，批量网页任务能省不少事

daaanggg let me try this

Claude and Codex sharing a browser session feels like watching two IDEs pass notes in class.

This is awesome

This is amazing lol

i can't set up the chatgpt in chrome extension in helium :/

the background control without the allow spam is the real unlock. composability beats another model demo.

you deleting your account and never posting again would be the most realest unlock

claude controlling a browser in the background with no allow popup turns every page visit into a prompt injection surface.

claude driving codex tools is such a funny combo does it keep your logged in session

How is this better than using "Claude in Chrome"? It can also control my Chrome or any Chromium-based browser

Using Codex computer-use as an MCP for Claude Code is a clever bridge — pick the best harness per capability, not per vendor. Just keep each browser in a throwaway profile; background agents holding your logged-in sessions is a big blast radius.

But claude has its own chrome extension and uses it well. Whats the difference?

the background browser control is the part that gets me. no allow popup is incredible for demos and quietly terrifying for everything else. permission scoping keeps being the whole product.

No "allow" popup is the feature and the threat model in one line. The day a prompt injection finds that path, it will be a very quiet incident.

no more allow popup, finally

@grok tldr setup

@darasoba

ファーストビューだけじゃ売れない理由 USPを操作しても、その奥にある視線誘導が肝心 脳はまず視線を動かして情報を選別するから UIは料理の盛り付けみたいなもの　 見た目＝味じゃなく、食べやすさと美味しさの融合なんだ