Khazix uses a CLAUDE.md rule to have Claude direct Codex to operate the browser
Overview
Khazix says he has no Claude browser extensions installed, because he fears an account ban, and instead has Claude instruct Codex to control the browser.
The routing rules are written in his CLAUDE.md file. Small tasks go to Claude's built-in browser: previewing and checking local UI, viewing pages, reading documents or web pages, screenshot checks, and checks completable in a few clicks. Complex work goes to the local Codex app: multi-step or end-to-end flows, logged-in back-end consoles, multi-site tasks, and long or trial-and-error work. A built-in browser task that becomes complex is also handed to Codex. The Chrome extension is turned off, and any task needing a real browser with login state goes to Codex.
Written by AI from the articles below · updated Oct 28, 4:12 AM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
Khazix@Khazix0918XClaude directs Codex to operate the browser under CLAUDE.md rulesAIKhazix says they avoid Claude browser extensions to prevent account bans, and instead have Claude instruct Codex to control the browser. The rules in CLAUDE.md route login-required settings pages and multi-step web tasks to Codex in Chrome, while small checks use the built-in browser. Codex runs via a codex-browser command, and each task must specify the URL, steps, and what to return.
Heat Trend
Not enough continuous observations to show a trend yet.