Module 3 · Connecting Everything
3.4 Browser Extension: Beyond the Codebase
Not every task that benefits from an agent lives in a code editor. The browser extension — available for Chrome, Edge, Brave, Opera, and Vivaldi — runs Codex directly against whatever's open in your browser: an admin console, an internal dashboard, a web app you don't have local access to but do have a login for.
The distinction worth understanding: this isn't Codex taking over your browser and driving it blind. It operates within tabs you've explicitly allowed, working alongside you rather than commandeering the screen, which matters if you're using it on anything with real account access. Think of the use case as "automate a repetitive task inside a web interface that has no API" — bulk-updating records in an internal admin tool, pulling a report out of a dashboard that only exists as a web UI, testing a user flow on a staging site by actually clicking through it the way a real user would rather than writing a separate test script for a one-off check.
This surface is worth knowing exists even if you don't reach for it often, because it covers a specific gap the other four surfaces don't: CLI, IDE extension, desktop app, and cloud tasks are all fundamentally about code. The browser extension is about the interfaces that sit on top of code but aren't code themselves — the parts of your actual job that happen in a browser tab, not a repo.
Do this before moving on
think of one recurring task you do by clicking through a web interface — an admin panel, an internal tool, a dashboard export — purely because it has no API you can script against. That's the shape of task the browser extension is built for, even if you don't set it up today.
