Browser Automation
Use this page to choose how browser_control should run.
Related references:
- Tool behavior and action schema: Browser Control
- Command catalog: CLI Reference
- Global config schema: wingman.config.json
Choose a mode
Wingman supports two user-facing browser modes:
- Playwright mode (
browserTransport: "playwright"orauto)
- Agent launches and controls its own Chrome/Chromium session.
- Best for unattended automation and repeatable runs.
- Use this when you want persistent profiles (
browserProfile) and headless automation.
- Relay mode (
browserTransport: "relay"orautofallback)
- Agent controls a tab you open and attach through the Wingman Chrome extension.
- Best for controlling your live, already-open browser tab/profile.
- Use this when you want explicit user-visible tab control.
Fast decision guide
- Want reliable unattended automation? Use Playwright Setup.
- Want to control your active Chrome tab directly? Use Relay Setup.
- Unsure? Start with
browser.transport: "auto"and test both.
Shared concepts
browserProfile: persistent login/session state for agent-run browser sessions.browserExtensions: extension IDs loaded forbrowser_controlruns.browser.transport: global default transport (auto,playwright,relay).browser.relay.*: local secure relay settings for extension-based control.
wingman init pre-populates a browser-ready baseline:
- default profile mapping (
default->.wingman/browser-profiles/default) - bundled
wingmanextension mapping and files under.wingman/browser-extensions/wingman browser.defaultExtensionsincludeswingman
Minimal config example
Next steps:
- Follow Playwright Setup for agent-launched automation.
- Follow Relay Setup for extension-attached live-tab automation.
