Skip to content
Codex DesignBETA

The Codex in-app browser.

The Codex desktop app has a built-in browser for previewing your site or app, leaving visual feedback right on the page, and letting Codex click through it to test a change. Here is how to open it, how annotations work, which settings matter, and what to check when the browser is missing or Codex cannot use it.

Updated November 8, 2026 · 6 min read

The short answer

  • Where it is: in the Codex desktop app (part of the ChatGPT desktop app). It is installed with the app. It is not available in the Codex CLI or the IDE extension.
  • What it opens: local apps such as http://localhost:3000, file-backed pages, and public websites.
  • How to open it: select New tab and enter a URL, open a link from the chat, or press Cmd+T (Ctrl+T on Windows and Linux).
  • How Codex uses it: mention @Browser in your message to have Codex open, click through, and check a page.
  • How to give feedback: select Annotate, click an element or drag over an area, write a comment, then ask Codex to address your comments.

This guide follows OpenAI’s Browser documentation, as of November 8, 2026.

Open a page

  • New tab: select New tab and type a URL. Typing in the address bar also matches your history, and anything else searches Google.
  • From the chat: select a URL Codex gives you, such as the address of a dev server it just started.
  • Keyboard: Cmd+T on Mac, Ctrl+T on Windows and Linux.
  • Layout: choose Enter full view or Enter split view. Cmd+Shift+B (Ctrl+Shift+B) switches back from full view or toggles the tabs beside the chat.

For a local app, ask Codex to start the dev server first and tell you the address, then open it. After Codex makes a change, look at the page again before you move on.

Let Codex use the browser

Mention @Browser when you want Codex itself to work in the page: open it, click through a flow, reproduce a bug, or check that a fix works.

Check a change in the browser
@Browser Open http://localhost:3000/settings, change the email address in the form, save, and confirm the success message appears. Then check the same page at 390px wide and tell me anything that breaks.

@Chrome is different: it controls your own Chrome through OpenAI’s extension, which needs a separate setup. The built-in browser keeps its own profile, separate from your regular browser, so it does not share your tabs or sign-ins. You can sign in inside it when a task needs an account.

Leave feedback with annotations

Annotations are the fastest way to tell Codex exactly what to change on a page.

  1. Select Annotate in the browser toolbar to enter Annotation mode.
  2. Click an element, or drag to select an area.
  3. Write your comment and save it. Add as many as you need.
  4. Send a chat message asking Codex to address the comments.

Use Adjust, next to the comment field, for style changes: font, text, spacing, and color. You see a preview of the change before you send it, which is quicker than describing “a little more space above the heading” in words.

Address annotations
Address all my comments on this page. Keep everything I did not comment on exactly as it is, and use our existing spacing and color tokens for any style changes.

Settings that matter

  • Settings > Browser > Agent permissions: defaults for browsing, downloads, and uploads, plus exceptions for specific sites. Removing a site’s custom permissions restores the defaults. Organizations can restrict these controls.
  • Sensitive actions: Codex asks you to confirm before it submits information or makes a purchase.
  • Downloads: they go to your Downloads folder unless you choose another location or turn on Ask where to save downloads.
  • Clear browsing data: in Settings > Browser, choose a time range and the kinds of data to remove.
  • Developer mode: turning on Enable full CDP access gives Codex controlled access to the Chrome DevTools Protocol, for deeper debugging. Codex asks before using it on a site, and admins can turn it off.

Codex cannot automate file uploads in the built-in browser. Upload files yourself when a flow needs one.

In-app browser not working?

Not in the CLI or IDE extension. The built-in browser is not available there. In the terminal or your editor, ask Codex to use a tool such as Playwright instead, or open the page in the desktop app.

The page will not load. For a local app, check that the dev server is running and that the port in the address is the one it printed. Ask Codex to start or restart it.

Codex cannot click or type in the page. Check that you mentioned @Browser, and that Agent permissions allow browsing that site, then try again in a new thread.

Browser shows as unavailable, especially on Windows. On the openai/codex GitHub tracker, Windows users have reported the Browser plugin showing as unavailable in Settings, the error “Browser is not available: iab”, and the browser opening but not responding to Codex. The workarounds reported there are to update or reinstall the app from the Microsoft Store, then use Windows’ Repair or Reset for the app, and restart. Results vary, so check the GitHub issues for your version.

Annotations do nothing. Make sure you saved each comment and then sent a chat message asking Codex to address them. Comments are not sent until you do.

Your organization disabled something. Admins can restrict browser permissions and full CDP access. If a setting is greyed out, ask your workspace admin.

Where Codex Design fits

The in-app browser shows one page at a time, which is ideal for checking and fixing the screen you are building. When you want to compare several directions for a screen side by side before choosing, Codex Design adds a canvas to Codex where each direction is a live HTML page you can select and edit. See Codex canvas for how the two fit together.

Frequently asked questions

Is the Codex in-app browser available on Windows?

The browser is part of the desktop app, which runs on Mac, Windows, and Linux. Some Windows users have reported it showing as unavailable; the workarounds above have helped some of them.

Can the in-app browser use my Chrome logins?

No. It has its own profile and does not share sessions with your regular browser. Sign in inside it, or use @Chrome with OpenAI’s Chrome extension to work in your own Chrome.

What is the difference between Annotate and Adjust?

Annotate adds comments to an element or an area. Adjust changes the font, text, spacing, or color of an element with a live preview, so Codex gets the exact values you want.

Keep reading

An independent plugin for Codex. Not affiliated with or endorsed by OpenAI.