Codex App: Allow the in-app browser to detach into a standalone window

Open 💬 1 comment Opened Jul 16, 2026 by bowenli86

What variant of Codex are you using?

App

What feature would you like to see?

I’d like the Codex in-app browser to support detaching into a separate, standalone window.

My main use case is a dual-monitor setup:

  • Monitor 1: Codex app, task conversation, code changes, and terminal output.
  • Monitor 2: Detached browser window showing the website being developed or tested.

Currently, the browser is embedded inside the Codex app, which limits screen space and makes it harder to monitor the website while collaborating with Codex.

Requested behavior:

  • Add a “Detach Browser” or “Open in Separate Window” action.
  • Preserve the current URL, session, authentication, and browser state.
  • Allow the detached window to be moved to another monitor and resized independently.
  • Keep Codex browser automation connected to the detached window.
  • Allow the window to be reattached to the main Codex app.
  • Remember the detached window’s size and position when practical.

Why this would help:

It would make frontend development and visual debugging substantially easier, especially when Codex is editing code while the user watches the website update on a second monitor.

Suggested acceptance criteria:

  • The in-app browser can be detached without losing its current state.
  • The detached browser remains controllable by Codex.
  • It can be moved and resized like a normal desktop window.
  • It can be reattached without reloading or losing the session.
  • Closing the detached window returns the browser to a predictable state in Codex.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗