Tabrelay

Tabrelay / Playwright and Puppeteer with a logged-in Chrome

Puppeteer and Playwright with your logged-in Chrome: an alternative

Puppeteer, Playwright and Selenium are excellent, but they drive a separate browser. If what you want is to automate sites where you are already logged in, there is a simpler path.

Download Tabrelay - free, MIT

Chrome or Chromium, Python 3.10+, macOS and Linux. Source on GitHub.

What Puppeteer, Playwright and Selenium assume

These tools normally start a browser of their own, in a clean or dedicated profile. That is the right design for tests and for anything running on a server. For your own day-to-day accounts it means logging in again in that browser, dealing with 2FA and "new device" checks, and keeping a separate profile alive. Some sites also treat automation browsers with suspicion.

Attaching to your everyday Chrome

Puppeteer and Playwright can connect to a Chrome that was started with --remote-debugging-port. It works, but it has costs:

The Tabrelay approach

Tabrelay runs inside the browser you already use. A Chrome extension carries out jobs with chrome.debugger, only on sites on an allow-list that you edit on the extension's own options page, and only for callers that hold a local secret token. The command line talks to a small server on 127.0.0.1 that refuses foreign Host headers and web page origins.

Playwright / PuppeteerTabrelay
Browserstarts its own, or attaches to a debug portyour normal Chrome profile, via an extension
Logins and 2FAlog in again in that browseralready there
Site limitsnone by defaultallow-list in the extension
LanguageNode, Python, Java, .NET (Playwright); Node (Puppeteer)CLI, plus a Python module
Locators, auto-waitingyesno; use wait_for and JavaScript
BrowsersPlaywright: Chromium, Firefox, WebKitChrome and Chromium only
Headless, servers, CIyesnot what it is for

When Tabrelay is the wrong choice

Use Playwright or Puppeteer for tests, scraping at scale, headless runs, anything on a server, and anything that needs other browsers. Tabrelay does less on purpose: no auto-waiting locators, no browser management, Chrome and Chromium only, and a page can tell that a debugger is attached.

When Tabrelay fits

See also Tabrelay vs Playwright MCP, browser-use and Claude in Chrome. Get Tabrelay from the latest release.

Frequently asked questions

Can Playwright use my logged-in Chrome profile?

It can attach to a Chrome started with a remote debugging port, or launch a persistent profile of its own. Neither is quite your everyday Chrome profile, and recent Chrome versions restrict remote debugging on the default profile. Check the current Playwright and Chrome documentation.

Is Tabrelay a replacement for Playwright?

No. It covers a narrow case, scripting your own logged-in Chrome, and does less: no auto-waiting locators, no browser management, and Chrome or Chromium only.

Is a remote debugging port safe?

Any local program that can reach the port can control every site in that browser. Tabrelay avoids opening one: it uses an extension with an allow-list and a local token.

Does Tabrelay need Node?

No. It needs Chrome and Python 3.10 or newer, with only the standard library.

Download Tabrelay - free, MIT

Chrome or Chromium, Python 3.10+, macOS and Linux. Source on GitHub.