Chrome integration: keep Codex out of my everyday browser profile

What feature would you like to see?

Please add built-in profile isolation to Codex’s Chrome extension integration. My key requirement is simple: I do not want Codex using my everyday Chrome profile. Its browser activity should happen in a separate profile.

That could be a dedicated Codex profile, a user-configured existing profile, or a profile created for a session. I do not have a strong preference about that product decision. I want a reliable, built-in way to keep Codex’s browsing separate from my daily browsing.

Expected behavior

• Codex launches or connects to the separate profile and opens its tabs there, including when my everyday Chrome profile is already running.
• Codex does not read or manipulate tabs in my everyday profile, or use its signed-in sessions, as part of that workflow.
• The profile being used is clear. If the separate profile is unavailable, Codex reports that or helps set it up instead of silently falling back to my everyday profile.
• This separation works without custom launch scripts or repeated instructions in each task.

Why this matters

I want to keep using Chrome normally while Codex works. Its tabs, browsing history, cookies, and signed-in accounts should stay separate from my personal browsing.

Related issues

• #31540 reports the Chrome extension selecting the wrong profile.
• #43160 requests explicit task-to-profile/session binding.

This request focuses on the user-level guarantee: keep Codex’s Chrome activity out of my everyday profile, whichever separate-profile approach the product supports.

Start by tracing Codex’s Chrome extension integration and reviewing related issues #31540 and #43160. Define the supported separate-profile approach and verify that Codex never silently uses the everyday profile, including when Chrome is already running; add or run the relevant integration coverage once the entry points are identified.