Quay

Quay's niche: Full Chrome accessibility tree + your existing authenticated sessions.

Install Quay via pip:

$ pip install quay

With the MCP server (for Claude Code, Codex, OpenClaw):

$ pip install "quay[mcp]"

Or from source:

$ git clone https://github.com/sidonsoft/quay
$ cd quay
$ pip install -e .

Chrome must be running with remote debugging enabled:

# macOS
/Applications/Google\\ Chrome.app/Contents/MacOS/Google\\ Chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.quay/chrome-debug-profile"

# Linux
google-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.quay/chrome-debug-profile"

# Windows
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%USERPROFILE%\.quay\chrome-debug-profile"

⚠️ Chrome 136+: the --remote-debugging-port flag is ignored on the default profile — you must pass a separate --user-data-dir. Sign in once in that debug profile and your session persists.

⚠️ Chrome 144+: Google added a consent prompt when attaching to a running Chrome. If you attach to a normal running Chrome (without the flags above), enable remote debugging at chrome://inspect/#remote-debugging and approve the per-connection prompt — it currently can't be persisted. Launching Chrome with the flags above skips the prompt entirely.

Or use the included launcher (uses a persistent ~/.quay/chrome-debug-profile by default):

$ ./scripts/chrome-debug.sh

Python API

from quay import Browser

browser = Browser()
browser.goto("https://gmail.com")  # Uses your logged-in session

tree = browser.accessibility_tree()
print(tree.to_tree_str())

browser.click_by_text("Sign in")
browser.fill_form({"Email": "user@example.com"})

CLI

# List tabs
$ quay list

# Open new tab
$ quay new https://example.com

# Get accessibility tree
$ quay snapshot

# Take screenshot
$ quay screenshot

# Click by text
$ quay click "Submit"

Expose Quay to MCP-capable agents (Claude Code, Codex, OpenClaw, …) driving your real logged-in Chrome over stdio:

$ pip install "quay[mcp]"
$ quay mcp --port 9222   # serves over stdio

10 tools: browser_status, open_tab, navigate, snapshot, click_text, click_ref, fill_form, evaluate, screenshot, close_tabs. The server instructions teach agents the status → snapshot → act-by-ref → verify loop.

Example Claude Code config entry:

{
  "mcpServers": {
    "quay": { "command": "quay", "args": ["mcp", "--port", "9222"] }
  }
}

See the MCP guide — including the five-minute Quay + OpenClaw setup guide — and the v0.2.8 release notes.

• ✓
  Accessibility Tree

  Navigate pages using AX nodes like agent-browser
• ✓
  Session Reuse

  Uses your existing Chrome session (no separate browser)
• ✓
  Connection Pooling

  WebSocket reuse across operations for speed
• ✓
  Auto-Reconnect

  Automatically reconnects on connection drop
• ✓
  Session Recording

  Record and replay browser actions
• ✓
  Form Filling

  Fill forms by label text
• ✓
  Click by Text

  Click elements matching visible text
• ✓
  JavaScript Eval

  Run arbitrary JavaScript
• ✓
  MCP Server · new in v0.2.8

  quay mcp — drive your real Chrome from any MCP agent (10 tools, stdio)

Quay automatically detects dropped connections and reconnects:

from quay import Browser

browser = Browser(reconnect=True, reconnect_max_retries=3)

# If connection drops during operation,
# Quay will attempt to reconnect automatically
tree = browser.accessibility_tree()  # May auto-reconnect if needed

Monitor reconnection with a callback:

def on_reconnect(msg):
    print(f"Reconnecting: {msg}")

browser = Browser(reconnect_callback=on_reconnect)

Quay uses a mixin-based architecture for maintainability:

See docs/internals/ARCHITECTURE.md for details.

Quay is open source and available under the Apache 2.0 License. Current release: v0.2.8 (Oct 2026) — see the full changelog.