Nextbrowser
Download
Installation1:53 watch

Set up NextBrowser on macOS with Codex

Install NextBrowser on macOS, pair your account, connect Codex and verify a first browser session from the desktop workspace.

About this reference video

This is a reference recording of standalone Clawbrowser installation on macOS, not a walkthrough of the NextBrowser installer. The current instructions below use NextBrowser browser pairing and its managed browser tools. Do not repeat the API-key prompt or standalone installation commands from the video as NextBrowser setup.

Go to the NextBrowser workflow ↓
Published · @next_ossaiWatch on YouTube ↗

Overview

NextBrowser combines a managed browser session with a local agent. On macOS, the setup has three separate checks: the NextBrowser account is paired, the browser profile can open a page, and Codex can inspect that page. Passing one check does not establish the others.

What happens in the video

The operator copies the installation prompt into Codex on macOS. Codex checks the Apple Silicon host, installs the standalone tooling, and asks for an API key. The browser then opens its verification page, and the final frames show passing fingerprint and proxy checks.

Before you start

  • A macOS machine supported by the current NextBrowser release
  • A NextBrowser account and browser access to approve pairing
  • Access to the service used by Codex and permission to install its local runtime

Run this in NextBrowser

Follow these steps in your own NextBrowser workspace. The video summary records the source demonstration; your result needs the checks below.

  1. Install the macOS desktop app

    Open the NextBrowser documentation and follow its latest-release link. Choose the macOS build for your machine, install it and launch NextBrowser. Use the release assets rather than the standalone runtime installer shown in the recording.

  2. Pair your NextBrowser account

    Choose Sign in to NextBrowser, continue in your browser and approve the pairing request. Return to the desktop app and check account status. The app configures its local browser-control credential; you do not need to paste an API key into Chat or the desktop UI.

  3. Connect Codex

    Install the ChatGPT desktop app and authenticate its Codex agent. NextBrowser uses the Codex executable bundled with that app; a separate Codex CLI installation is not required by this setup. Select Codex in NextBrowser and confirm that it is available and authenticated before assigning a browser task.

  4. Start and inspect the browser profile

    Create or select the intended profile in the sidebar and start its session. Complete the runtime download prompt if one appears. Open https://example.com/ and confirm the active tab and page in Live View. Verify identity if country or proxy consistency matters.

  5. Run a read-only first task

    Send the prompt below to Codex in NextBrowser Chat. Compare the reported URL and page title with Live View. If the task fails, check account connection, traffic, session, active tab and then agent authentication in that order.

Send this prompt in NextBrowser Chat

Suggested prompt

In NextBrowser, confirm the intended profile [profile name] and its running session. Open https://example.com/ if it is not already open. Report the active page URL and title, and leave it visible for me to check in Live View. Do not submit forms or change account settings.

Replace the placeholders, then send this in NextBrowser Chat with the intended profile and agent selected. This is a suggested task, not the recording transcript.

What to verify in your run

  • A paired NextBrowser account and an available Codex runtime
  • A running profile with a visible page whose URL and title match the agent report

Questions about this workflow

Should I follow the API-key instructions in the recording?

No. The recording covers standalone browser tooling. For NextBrowser, use Sign in to NextBrowser and approve browser pairing; the app configures its local credential.

How does NextBrowser connect to Codex?

Install the ChatGPT desktop app and authenticate its Codex agent. NextBrowser uses the Codex executable bundled with that app; a separate Codex CLI installation is not required by this setup.

What if the agent cannot see the page?

Check the actual selected profile, running session, active tab and page state before changing agent configuration. Profile selection is context for the agent, not technical containment. Use the troubleshooting guide if the mismatch persists.

Keep exploring

NextBrowser documentation

NextBrowser documentation ↗Product guide: profiles, agents and sessions ↗NextBrowser session and agent troubleshooting ↗

From the blog

Self-Hosted Browser Automation: The Complete Guide for 2026 ↗

Read about preparing and operating a browser automation environment.

Related use cases

AI Agent Browser Automation ↗

NextBrowser workflow adapted . Recording reviewed . Video source: published video and description.

More workflows to explore

← Browse all demos