Migrate to oh-my-webbridge

Every oh-my-webbridge command names a session, an action and a JSON object of arguments. The tables on this page map common commands of other tools to these actions. Before you move a task, check Comparison with other tools for capabilities that oh-my-webbridge does not have.

Before you startCopy Anchor Link

1. Install the daemon and the extension, and pair your browser. See Getting started.
2. Install the agent skill with omw install-skill ~/.agents/skills. Turn off the skill or MCP server of the previous tool, so that the agent uses one tool for a task.
3. Run omw status. It prints one line for each browser, for example chrome: connected (156.0.8078.80).

Changes for every toolCopy Anchor Link

• Sessions. Use one session name for each task, for example checkout. The first command opens the session. Its tabs open in the background, in one tab group. End the task with close_session. All sessions use your browser profile and its cookies.
• References. A reference has the form @e<generation>.<index> and comes from the latest snapshot of the tab. A reference that starts with @e and comes from another tool or an older snapshot fails with stale_ref. A reference without @, such as e12, is read as a CSS selector. Take a new snapshot after a navigation.
• Locators. The selector argument accepts CSS and text locators. Playwright locators map to these forms. role= matches the name exactly, while getByRole matches a substring unless exact: true is set. Chained locators and .filter() have no counterpart. See Selectors.

• JavaScript. evaluate takes an expression, not a function. Send document.title, or wrap the function in a call: (() => document.title)(). Code that uses await goes in an async function call: (async () => (await fetch("/api")).status)().
• Files. screenshot and save_as_pdf take an absolute path and return it. They do not overwrite an existing file.
• Deadlines. A command fails after 30 seconds by default. The HTTP body field timeoutMs, or --timeout-ms in omw call, sets 1 to 120000 milliseconds. A wait that runs out of time fails with wait_timeout.
• Firefox. Some actions answer unsupported in Firefox. See Firefox.

From the Kimi browser extensionCopy Anchor Link

The request format and most action names are the same. The address, the token and some arguments change.

The same navigate request to each daemon:

# Kimi browser extension
curl -s -X POST http://127.0.0.1:10086/command \
  -H 'Content-Type: application/json' \
  -d '{"action":"navigate","args":{"url":"https://example.com","group_title":"Research"},"session":"research"}'

# oh-my-webbridge
TOKEN=$(omw connection | sed -E 's/.*"token":"([^"]+)".*/\1/')
curl -s -X POST http://127.0.0.1:17373/command \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"session":"research","action":"navigate","args":{"url":"https://example.com","group_title":"Research"}}'

# oh-my-webbridge command line
omw call research navigate '{"url":"https://example.com","group_title":"Research"}'

These actions keep their names and arguments: navigate, find_tab, list_tabs, close_tab, close_session, mouse_click, fill, key_type, hover, drag, find, cdp, screenshot, save_as_pdf, upload and network. These change:

From MCP browser serversCopy Anchor Link

oh-my-webbridge has no MCP server. The agent runs omw call in a shell, as the skill describes. One tool call becomes one command:

omw call checkout click '{"selector":"role=button[name=\"Pay\"]"}'

In Chrome DevTools MCP, the page tools also take pageId, which is required by default. The table leaves it out.

• A Browser MCP call can hold several command lines. batch runs up to 64 steps in one request and stops at the first error: omw call checkout batch '{"steps":[{"action":"fill","args":{"selector":"label=Email","value":"a@example.com"}},{"action":"send_keys","args":{"keys":"Enter"}}]}'. screenshot, save_as_pdf and close_session run as separate commands.
• browser_type with submit: true becomes fill followed by send_keys with Enter.
• console works in Chrome and returns the messages logged after start. Send start before the step that logs.
• Performance traces, Lighthouse and heap snapshots in Chrome DevTools MCP, and response mocking, tracing and code generation in Playwright MCP, have no built-in action. Keep that server for those tasks. A page connection accepts the protocol domains that chrome.debugger allows, for example Fetch to intercept requests.

From agent-browser and PinchTabCopy Anchor Link

oh-my-webbridge does not start a browser, so it has no counterpart to --headed, --profile, --state, profile management or instances. Commands run in background tabs of the browser you use, with its logins. The first argument of omw call names the session. A PinchTab agent session sets identity and permissions; the closest match to an oh-my-webbridge session is a PinchTab instance or tab.

From Playwright or Puppeteer scriptsCopy Anchor Link

In extension mode, the daemon lists page targets at /json/list and serves one tab at /devtools/page/{tabId}. Its /json/version has no webSocketDebuggerUrl. Playwright's chromium.connectOverCDP and Puppeteer's puppeteer.connect with browserURL read that field to find the browser endpoint (Playwright source, Puppeteer source). There are two ways to move such a script.

Keep the script on native modeCopy Anchor Link

Native mode passes a browser endpoint through the daemon. Start Chrome with --remote-debugging-port=9222 and a separate --user-data-dir, then start the daemon with the browser URL from http://127.0.0.1:9222/json/version:

omw serve --cdp ws://127.0.0.1:9222/devtools/browser/8b0d3f7c-...

Connect Playwright with the token in headers, as shown in CDP. In Puppeteer, pass browserURL: "http://127.0.0.1:17373" and the same header in wsOptions.headers. The script then drives that separate Chrome, not the profile you use every day.

Move the script to the SDKCopy Anchor Link

The SDK drives tabs in the browser you use, through the extension.

import { connect } from "./dist/sdk.mjs";

const task = await connect("checkout");
await task.navigate("https://example.com/cart");
await task.click('role=button[name="Pay"]');
await task.close();

For raw protocol access in extension mode, send commands with the cdp action, or open /devtools/page/{tabId} with a WebSocket client that sends the Bearer header. See CDP.