Helping Codex's new Chrome plugin work across browsers and channels.
Codex's new Chrome plugin currently only supports Chrome Stable. Browser Control fills in the gap for Edge and for the Beta, Dev, and Canary channels.
Browser Control teaches Codex about the browsers and channels:
| Browser family | Supported channels |
|---|---|
| Google Chrome | Stable, Beta, Dev, Canary |
| Microsoft Edge | Stable, Beta, Dev, Canary |
You can invoke it directly:
@browser-control open the dashboard I was just using
You do not have to name a channel every time. If you do not specify one, Browser Control is instructed to infer the best available browser from your context, connected browser, frontmost browser, and recent browser activity.
When it matters, you can name the browser, channel, or profile:
use my work profile to check the staging login
open the billing portal in Edge Dev
use Chrome Dev to test this localhost page
check the Microsoft admin center in my Edge work profile
open the beta site in Chrome Canary
use my personal Chrome profile for this checkout flow
The goal is simple: when you ask Codex to use a browser, it should use the right one.
codex plugin marketplace add novotnyllc/browser-controlThen enable it in Codex config if needed:
[plugins."browser-control@browser-control"]
enabled = trueRestart Codex after changing plugin config.
codex plugin marketplace upgrade browser-controlMIT. See LICENSE.