Getting started

Chrome and Firefox can run side by side, and each browser is paired on its own.

RequirementsCopy Anchor Link

• Chrome 156 or later, or Firefox 153 or later.
• macOS or Linux, on the same computer as the browser.
• zstd to unpack a release archive.
• Go 1.27.3, Node 24 and pnpm 11 to build from source.

Install the daemonCopy Anchor Link

zstd -dc omw-<version>-darwin-arm64.tar.zst | tar -xf - -C "$HOME/.local"

Install the extensionCopy Anchor Link

Set up the browserCopy Anchor Link

Installing the extension opens the setup page. The popup reopens it with Open setup when the browser is not paired, the daemon is not running, or the daemon refuses the connection.

Firefox adds a step of its own before the last one, Allow scripts, whose button carries the same label. The evaluate action needs the optional user script permission; you can grant it there, or later under Settings, then Pages.

The extension pages, the popup and the toolbar tooltip use the language of the browser. To choose another language, open the language menu at the bottom of the side rail on the setup or settings page. The extension has English, Traditional Chinese (Taiwan, Hong Kong and Macau) and Simplified Chinese.

Start at loginCopy Anchor Link

Move the binary to the path you intend to keep, then run:

omw service install

On macOS the command writes ~/Library/LaunchAgents/app.oh-my-webbridge.plist and loads it with launchctl. On Linux it writes ~/.config/systemd/user/oh-my-webbridge.service and enables the unit with systemctl --user. The unit runs omw serve with the configuration directory used by the install command. Stop a daemon that omw start launched before installing the service, because the service starts its own. Stop the service through its manager:

launchctl bootout gui/$(id -u)/app.oh-my-webbridge

systemctl --user disable --now oh-my-webbridge.service

omw stop asks a running daemon to exit and leaves tabs open. With the service installed, use the service manager so the daemon does not start again.

Install the agent skillCopy Anchor Link

omw install-skill DIR writes DIR/oh-my-webbridge/SKILL.md and copies the guide built into the binary. It refuses to overwrite an existing file, so delete the old one before installing again. omw skill prints the same guide. The guide tells an agent which commands to run, how sessions and tab ownership work, and which errors to expect.

First commandsCopy Anchor Link

omw call research navigate '{"url":"https://example.com","group_title":"Research"}'
omw call research snapshot
omw call research evaluate '{"code":"document.title"}'
omw call research close_session

The first argument after omw call is the session name; keep one name per task. Each command prints JSON on stdout.

• navigate opens a background tab in a new group titled Research and returns the tab id. Later navigations in the same session reuse that tab; pass newTab to open another.
• snapshot returns the accessibility tree with @e references that click and fill accept.
• evaluate returns the value of the expression.
• close_session closes the tabs the session owns and releases any borrowed tab.

The third argument is a JSON object. Pass - to read it from stdin, which avoids shell quoting:

omw call research evaluate - < request.json

When both browsers are connected, name one right after omw call:

omw call --browser firefox research snapshot

Check the connectionCopy Anchor Link

omw doctor prints the config path on stderr and the status JSON on stdout, then one line per browser on stderr:

chrome: connected (VERSION)
firefox: not connected

omw status prints the same status JSON and browser lines without the config path. Both exit nonzero when the daemon does not answer.