Setup Get Started
xAI Grok: Booking flights via Google Flights

Give each agent
secure, visible control.

Wingman turns your browser into a supervised workspace. Watch xAI Grok and other agents book flights, navigate apps, and execute tasks safely.

Warm browser workflow One profile per agent Separate extension install Shared machine, isolated state
Install first, then run wingman setup to wire Claude, Codex, and Gemini automatically.
Assign an agent to a profile
Each profile keeps its own cookies, tabs, downloads, and extension state.
Click to see how Wingman assigns a profile to Claude, Codex, Gemini, or Cursor.
AI can make mistakes. Wingman keeps execution visible by focusing the profile's browser and outlining the active tab so you can supervise, pause, or take over.
Profile isolation Each Chrome profile keeps its own cookies, logins, and tabs.
Separate extensions Give each agent its own Wingman install and local bridge.
One machine, many agents Run Claude, Gemini, Codex, and Cursor side by side without collisions.
wingman.app/session/codex
Live profile matrix
Profile A Claude + Wingman
Profile B Gemini + Wingman
Profile C Codex + Wingman
Profile A
LinkedIn
Apollo.io
Profile B
Github
Stack Overflow
> Thinking...
Checking which Chrome profile is assigned to this agent.
Focused profile: Profile A
Ready: separate extension, separate session, visible handoff.
|
The Registry

Ready-to-Run Automations.

Skip the setup. Use built-in recipes for the most common agent tasks, then import or export packs as JSON.

Inspect

Inspect Current Tab

Read the active tab, capture the visible text, and take a screenshot in one shot.

Built-in
Batch

Open Multiple Pages

Open a small list of URLs in parallel tabs and keep them in the same Wingman session.

Built-in
Compare

Compare Two Tabs

Read two tabs side by side in one shot, useful for research, QA, or side-by-side checks.

Built-in
Browse recipes, import packs, export JSON
Advantage

Separate profiles over shared browser state.

Wingman keeps each agent in its own Chrome profile, with its own extension and browser state.

The Cold Sandbox (Playwright)

  • Starts at about:blank every time
  • Fighting MFA and Login walls
  • Headless: Impossible to "help" if it fails
  • 10 instances = 10 separate login sessions

The Profile Workspace (Wingman)

  • One Chrome profile per LLM agent
  • Separate extension and local bridge per profile
  • Each profile keeps its own cookies & sessions
  • No collisions when multiple agents run side by side

Managed Chrome Profiles

Give each assistant its own profile so sessions, cookies, and browser state never collide.

Native Interaction

Precise clicks, form filling, and drag-and-drop that mirrors real human behavior inside your actual browser.

Local-First Privacy

Keep automation inside the assigned profile, with optional cookies and downloads permissions plus privacy mode controls.

Parallel Profiles

Run multiple agents at the same time across different profiles without sharing browser state.

Smart Downloads

Managed download handling that works inside the active profile with Chrome's native filesystem.

Offline Licensing

Pro users get signed offline keys. Each profile stays licensed even if you go off the grid.

Security Model

Local by design. Controlled by policy.

Wingman keeps browser actions on your machine and uses the cloud only for auth, licensing, and billing.

Local bridge

The MCP server talks to the extension over a localhost WebSocket, with a token and extension handshake.

  • 127.0.0.1 bridge only
  • Extension handshake required
  • Protected status and setup endpoints

Session isolation

Each assistant can run in its own session and tab group so workflows don’t collide.

  • Session IDs per assistant
  • Tab group separation
  • Multi-instance friendly

Privacy mode

Allowlist and denylist controls let customers decide exactly where automation can run.

  • Allowlist per domain
  • Denylist always wins
  • Sensitive actions can require unlock

Optional permissions

Cookies and downloads are opt-in Chrome permissions, not assumed by default.

  • Cookies permission optional
  • Downloads permission optional
  • Granted from the popup only

Restricted surfaces

Dangerous browser surfaces and URL schemes are blocked before they can be used.

  • No `chrome://`, extension, or devtools pages
  • No `javascript:`, `data:`, `blob:`, or `file:` navigations
  • Security checks before sensitive tools

Cloud boundary

Azure handles login, plans, and billing. Your browser session stays local unless you intentionally export data.

  • Auth and entitlements in Azure
  • No browser cookies stored in cloud
  • Local browser remains the source of truth
Supervised by default

Wingman does not hide the work from you. Each tool call brings the browser forward, highlights the active tab, and keeps the loop visible so users can catch hallucinations, unexpected steps, or risky actions before they go too far.

Install

Give each profile its own install.

Install Wingman in every Chrome profile you want to assign to a different agent, then run the one-command setup to connect the local MCP server and client.

1

Install in each profile

Add Wingman to every Chrome or Brave profile you want to dedicate to an agent.

2

Start the local server

Run wingman setup from your terminal. It starts the MCP server, writes client config, and connects each profile on localhost.

3

Assign an agent

Use the setup page to map Claude, Cursor, Gemini, Codex, Windsurf, Cline, or Zed to a profile. No account is required to begin.

Setup Guide

Map each agent to a profile.

Use this flow so your IDE, local server, and browser extension all point at the right Chrome profile.

Step-by-step setup
What to do in order
No shared browser state required
  1. Install Wingman. Add the extension to the Chrome or Brave profile that will belong to one agent.
  2. Run the bootstrap. Run wingman setup or npm run wingman:setup in a terminal.
  3. Open the setup wizard. Click Setup in the extension popup to detect your IDE clients for that profile.
  4. Connect your client. Follow the generated config for Claude, Cursor, Gemini, Codex, Windsurf, Cline, or Zed.
  5. Run the test. Use the built-in test button to confirm the MCP server, extension, and browser profile are connected.
Supervised execution is on by default. Wingman brings the assigned profile forward so you can watch the agent work and take over if it goes off course.
Quick commands
CLI and MCP entry points
Same engine, many profiles
wingman
wingman run tabs_context
wingman run navigate '{"tabId":1,"url":"https://example.com"}'
wingman recipe ./recipe.json
First-run path: wingman setup
If you prefer an IDE workflow, add Wingman as an MCP server. If you prefer batch jobs, use the CLI. Both hit the same browser bridge and profile map.

Simple, transparent pricing.

Start free, upgrade when you need more.

Free
$0

Perfect for trying out.

billed monthly
  • 50 Operations / day
  • 20 Screenshots / day
  • 2 Managed Tab Groups
  • Core Browser Tools
Get Started
Popular
Pro
$20/mo

For professional developers.

billed monthly
  • Unlimited Operations
  • Unlimited Screenshots
  • Parallel Execution
  • Offline License Key
  • Download & Cookie Tools
Subscribe
Max
$100/mo

For power users and teams.

billed monthly
  • Everything in Pro
  • Multi-instance support
  • Team profile control
  • Priority support
Subscribe

Ready to give your agent hands?

Get Started See Setup Flow