Browser bridge (CDP)

Forgeline drives your existing Chrome through the Chrome DevTools Protocol instead of spawning a fresh headless browser. You stay logged in; the agent just borrows your session.

Start Chrome with CDP

Launch Chrome with a dedicated user-data-dir so you don't fight the security check added in Chrome 136:

# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 \
  --user-data-dir=$HOME/ChromeAuto

# Windows (PowerShell)
"C:\Program Files\Google\Chrome\Application\chrome.exe" `
  --remote-debugging-port=9222 `
  --user-data-dir=$env:USERPROFILE\ChromeAuto

Attach from the agent

{
  "method": "tools/call",
  "params": {
    "name": "cdp_attach",
    "arguments": { "endpoint": "http://127.0.0.1:9222" }
  }
}

Why CDP and not a fresh browser

You're already signed into the sites the agent needs. No OAuth churn.
Sessions persist between tasks. No re-login after every run.
You can watch what the agent does in real time, in a window you control.

Known limitation: Chrome 136+ rejects CDP on the default user-data-dir. Use a dedicated profile dir as shown above.

Next: Auth & tunnels →