OpenSidebar
Connect your tools

Your browser.
Available to Codex.

Let Codex request a page review through OpenSidebar, in the Chrome browser you already use. You can watch the work and stop it locally.

Set up Codex CLI How the connection works

One account. Two connections.

Browser connection

OpenSidebar → Chrome

Sign in to the website and link the installed extension. A single-use browser link code belongs here.

MCP authorization

Codex → OpenSidebar

Authorize Codex once for your account. Codex stores its own credential; it cannot use your website login cookie or extension link code.

Already signed in for 30 days? Your website session remains valid. OpenSidebar reuses your current website session and shows a consent screen for Codex. Only a missing or expired session asks you to sign in; after that, you return to the pending connection. This does not create another account or unlink Chrome.

Set up Codex CLI

Configuration checked with Codex CLI 0.160.1. Update Codex if your version does not support these OAuth settings.

  1. Get your browser ready

    Install OpenSidebar, sign in, and link Chrome in Connections. In Security, enable remote browser work when you want to accept tasks. Keep Chrome open. Connections should show Ready for remote reading.

  2. Add the server configuration

    Merge this into ~/.codex/config.toml. If an opensidebar section already exists, update it instead of adding a duplicate. Keep your other settings. 

    [mcp_servers.opensidebar]
url = "https://opensidebar.com/mcp"
scopes = [
  "openid",
  "https://opensidebar.com/mcp/browser.devices.read",
  "https://opensidebar.com/mcp/browser.tasks.create",
  "https://opensidebar.com/mcp/browser.tasks.read",
  "https://opensidebar.com/mcp/browser.tasks.continue",
  "https://opensidebar.com/mcp/browser.tasks.approve",
  "https://opensidebar.com/mcp/browser.tasks.cancel",
]

[mcp_servers.opensidebar.oauth]
client_id = "5ncvofhmoi8mgkjpl1focdhdor"
callback_url = "http://localhost:1455/auth/callback/3MqMAmAkMrwa"
callback_port = 1455

    The client ID is public, not a secret. No client secret, API key, or browser code belongs in this configuration. Leave oauth.resource unset; Codex discovers the resource from the server.

  3. Authorize this Codex client

    Run this command in a terminal on the same computer as your browser. Chrome opens the OpenSidebar consent page. Check the account shown and choose Allow Codex. If your website session expired, sign in there first; you will return to consent. Keep any email code in the browser. 

    codex mcp login opensidebar

    Wait for the terminal to confirm successful login. This grants the listed MCP scopes; browser execution still follows your remote-work setting and local policy.

  4. Verify before starting a task

    Start a new Codex session so it loads the server, then paste:

    Use my OpenSidebar MCP connection. Call browser_list_devices and report which browsers are online and ready for remote work. Do not start a task or change settings.

    Success means Codex actually lists your browser with availability: online and remoteWork: ready. A saved server entry or website label alone is not a connection test.

Try a small page review

After the readiness check, ask Codex to use your named browser to review a page you choose. For example: “Use OpenSidebar in my Chrome browser to review the public OpenSidebar setup guide and list any unclear instructions. Do not submit forms or change settings.”

A task can make model calls under your configured provider and usage limits. Watch progress in the extension, and use Stop if needed.

If something does not connect

I am already signed in to the website

The website and Codex have separate credentials. Your current website session is reused. You should see “You’re already signed in” and a consent screen, not another email-code prompt. If a Cognito login page opens, cancel that old flow and restart the CLI connection to use the current server metadata.

Codex says authorization is saved, but tools are missing

Run codex mcp list to check the server entry, complete codex mcp login opensidebar, then open a new Codex session. The website records past authorization; it cannot confirm the credential in this terminal.

The login has an invalid redirect or scope error

Check the exact server name, URL, scopes, client ID, callback URL, and port above. Do not add a separate resource setting. Port 1455 must be available on the computer running Codex. Other callbacks require registration by the operator.

My browser is offline or remote work is unavailable

Open Chrome, confirm the extension is signed in to the same account, and refresh Connections. “Remote work unavailable” means the build has not confirmed support. “Remote work disabled” means the account permission is off.

Access is not enabled, or authorization was revoked

Hosted MCP still requires pilot access. Contact support if access is not enabled. Revoked authorization is deliberately rejected; signing in again may require operator-assisted reactivation. Do not generate browser link codes to fix MCP authorization.

I use another MCP client or a remote terminal

The service uses Streamable HTTP at https://opensidebar.com/mcp with OAuth authorization-code flow and PKCE. The public client above is registered for the shown local Codex callback. Other clients and remote-terminal callbacks need operator configuration; URL-only setup and dynamic client registration are not currently supported.

You stay in control

Stop a task in the extension or ask Codex to cancel it. Turn off remote browser work in Security to stop accepting remote work. Revoke the Codex integration in Connections to remove its account access. codex mcp logout opensidebar clears this CLI’s saved authorization.

Official Codex MCP documentation · Source code