How does Lightpanda Session Bridge pass logins to AI agents?

The human user authenticates normally in their desktop browser (Chrome, Comet, Edge) using their standard 2FA, passkey, or Google OAuth. An open-source Manifest V3 extension captures scoped cookies upon explicit user click and securely relays them to a local Lightpanda headless instance via CDP WebSocket without exposing passwords to the LLM.

Does the local relay store or log my passwords and cookies?

No. The local relay binds strictly to loopback (127.0.0.1) and enforces a zero-logging security policy. Cookie values never touch disk logs, chat traces, or agent prompt contexts.

What protections prevent SSRF and cookie theft?

The relay blacklists identity provider roots (accounts.google.com, login.microsoftonline.com, auth0.com, github.com), enforces mandatory DNS resolution with 60-second caching against TOCTOU rebinding, and strictly blocks private IP subnets and wildcard DNS tools like nip.io.

⚡ ZERO-CREDENTIAL SESSION TRANSFER

The authenticated bridge for
machines and AI agents.

Connect to any web service using your real Google OAuth, Passkeys or SSO in your browser, then synchronize the authenticated session to headless Lightpanda (WSL2) in a single click. No passwords typed, no credentials logged, 100% scoped to the target origin.

Get Chrome Extension Explore Architecture

$ git clone https://github.com/Raknaos/lightpanda-session-bridge

95%+

Web Coverage

Support universal for standard cookies, RFC __Host- locks and SPAs localStorage.

Secret Exposures

Identity Provider roots (Google, Microsoft, GitHub) are strictly blocked from session dump.

10×

Agent Autonomy

Agents inspect usage, read reports and execute tasks directly in the background.

12ms

Transfer Latency

Instant loopback CDP injection via persistent WebSocket transport on port 9222.

How It Works

Secure Tri-Layer Architecture

Layer 1 · Browser

Chrome / Comet

You login normally with Google OAuth, 2FA or passkeys. No agent sees your password.

Manifest V3 Extension

HTTP POST

Loopback

Layer 2 · Guard

Python Relay

Validates exact HTTPS origin, drops identity root domains, normalizes sameSite and __Host- cookies.

127.0.0.1:8765

CDP WS

Target Session

Layer 3 · Engine

Lightpanda

Isolated headless Zig/V8 browser receives cookies and localStorage in memory to perform tasks.

WSL2 :9222

Zero-Trust Guarantees

Engineered for Complete Security

🛡️

Strict Origin Locking

Rejects loopbacks, private IPs, paths, user credentials, and identity providers like accounts.google.com. Only the target SaaS service session is exported.

🍪

RFC 6265bis Normalization

Cookies with __Host- prefixes have their domain attributes automatically stripped to ensure zero rejection by the Lightpanda CDP kernel.

⚡

CDP Enum Translation

Translates Chromium's lowercase sameSite values (no_restriction, lax) into official PascalCase tags (Strict, Lax, None).

Developer SDK

Drive Lightpanda with Python

lightpanda_client.py

CDP Protocol 1.3

from lightpanda_client import LightpandaClient

# 1. Connect to Lightpanda CDP and verify the session bridge
client = LightpandaClient()
client.connect()

# 2. Attach to target domain previously synchronized via Chrome
client.attach_or_create("https://a6api.com/console/log")

# 3. Read authenticated data in background without UI overhead
result = client.evaluate("""(async () => {
    let res = await fetch('/api/user/self');
    return await res.json();
})()""")

print(f"Authenticated account: {result['data']['username']}")
client.close()
        

The authenticated bridge for machines and AI agents.