Silent co-pilot: join a meeting with your own Google account (Camoufox/stealth)

[YJack0000]

Goal

Join a given Google Meet URL via a locally-driven browser signed in with the user's own Google account (not a separate "bot" account). The user appears as a normal participant; Parley observes via captions and the user can step away or jump back in.

Headless is not required — a visible / anti-detection browser is fine (and probably better). Evaluate Camoufox (anti-bot Firefox, Playwright-controllable) vs Playwright Chromium with stealth. Since it's the user's real, aged account on a residential IP, detection risk is already low; the anti-detect browser just removes any "automation detected" friction.

Tasks

• Pick the engine: Camoufox (anti-detect Firefox) vs Playwright Chromium stealth vs attaching to a real browser profile. Spike + decide.
• One-time login of the user's own Google account; persist the session locally and reuse on later joins.
• Join flow for a given Meet URL: mic + camera off, correct display name, handle waiting room / "ask to join".
• Session lifecycle: start / stop, detect leave/removed, reconnect; allow the browser window to be shown or hidden.

Notes

• It's the user's real account → "automation logs me in and joins on my behalf", not a bot identity.
• Local-only; nothing transits a Parley server.

Part of the "Silent co-pilot & catch-up mode" epic.

[AminDhouib]

@YJack0000

The session persistence side of this is exactly what we built into our stealth browser MCP server. It uses a master/snapshot/clone profile strategy so your Google login carries over between sessions without re-authenticating each time:

persistent-sessions.mp4

Session persistence demo on YouTube

It is also fully undetectable by anti-bot systems (Cloudflare, DataDome, etc.).

pip install stealth-chrome-devtools-mcp

https://github.com/DevinoSolutions/stealth-chrome-devtools-mcp