You ask Codex to check a page behind a login, and it stops at the sign-in form. Codex has more than one way to avoid that, and most of them are free. This post goes through them in order. I build Hronaut, the paid option at the end, so the free routes come first and get a fair description.

Free route 1: the built-in browser in the ChatGPT desktop app

If you run Codex in the ChatGPT desktop app, it already has a browser. Open a tab with New tab or Ctrl+T (Cmd+T on macOS) and point the agent at it with @Browser.

OpenAI's documentation describes it as a browser profile separate from your regular browser. It does not share your existing tabs or sign-ins, you can sign in directly when a task needs an account, and it keeps its own profile and browsing history. Settings › Browser is where you clear that data.

For one app and one account this is the simplest answer: sign in once in the built-in browser and let Codex work there.

Free route 2: the Chrome extension

The ChatGPT browser extension lets Codex work in an existing Chrome, Edge, Brave, Opera or Vivaldi tab with your regular browser profile, invoked with @Chrome. Everything you are already signed in to is available at once.

That is also its cost. The agent acts inside the browser that holds your email, your bank and your other accounts. Use it for tasks where that is what you want, and keep it away from tasks that do not need your identity.

Free route 3: Playwright MCP in Codex CLI

In the terminal, Codex CLI has no built-in browser, but it speaks MCP. Add Microsoft's open-source Playwright MCP server:

codex mcp add playwright npx "@playwright/mcp@latest"

Playwright MCP keeps a persistent profile by default, so cookies and sign-ins survive between Codex sessions. The profile folder is named after a hash of the MCP client's workspace root. To be sure each repository gets its own sign-ins, pass a profile per project:

codex mcp add playwright-myapp -- npx "@playwright/mcp@latest" --user-data-dir="$HOME/.codex/browser-profiles/myapp"

--isolated keeps the profile in memory for tests that must start clean.

Where the free routes stop

  • One identity per profile. The built-in browser has one profile, and a Playwright profile holds one set of sign-ins. Checking a page as an admin and as a regular member at the same time, or keeping two clients' accounts apart in one project, needs two profiles you set up and keep track of yourself.
  • Your everyday profile, or nothing. The extension shares your real sign-ins. The other two start empty. Neither gives you a middle ground of named, separate profiles you can see and manage in one place.
  • The browser belongs to one tool. The built-in browser lives in the ChatGPT app, and a Playwright MCP browser closes with the Codex CLI session that launched it, along with its tabs and console. A sign-in made there is not available to Claude Code or Cursor.
  • No pause. You can watch, but nothing stops the agent's next action while you type a password or a 2FA code.

When Hronaut is worth it

Hronaut is a desktop browser that runs as its own app, next to Codex. Codex CLI and the ChatGPT desktop app connect to it as an MCP server.

  • Named workspaces. One per project, client or role, each with its own cookies and sign-ins, managed in one window. staging-admin and staging-member can be open side by side.
  • Your everyday browser stays out. Hronaut never touches your Chrome profile.
  • The browser outlives the session. Close Codex and the workspace stays open with its tabs and page state. The next session resumes it with its ID and private resume key, and Claude Code or Cursor can resume the same workspace without signing in again.
  • Pause and take over. Pause agent access, sign in or pass 2FA yourself in the same tab, and hand it back. The agent can ask for your attention on a tab when it reaches a human-only step.

It costs $4 a month or $24 a year per named user after a 10-day trial, which needs no card and never charges you. It is one more desktop app to keep updated, and it drives Chromium only.

Try it

Install Hronaut from the download page, then add the plugin in a terminal:

codex plugin marketplace add hronaut/hronaut-codex-plugin
codex plugin add hronaut@hronaut

Start a new Codex session and give it a task that needs a sign-in:

Create a Hronaut workspace named staging-admin with scratch storage.
Open https://staging.example.com and stop at the sign-in form.
Ask for my attention on that tab, wait for me to sign in,
then open Settings and report what you see.

The Codex setup guide covers manual configuration and checks, and the Claude Code version of this post has more on what Playwright MCP keeps.

Sources: ChatGPT desktop browser documentation (separate profile, sign-in, Settings › Browser, @Browser and @Chrome), Playwright MCP README (Codex command, persistent profile, --user-data-dir, --isolated), Hronaut README (workspaces, pause and takeover, resume), hronaut.dev/pricing, Codex setup guide (plugin commands).

Written with the help of AI.