Browser Preview

Live Browser Automation

Let an AI agent drive the Browser panel you already have open — same tabs, same navigation history, same signed-in sessions. Sixteen browser_* MCP tools cover navigating, clicking, typing, reading the page, and screenshotting, all scoped to one project and tab.

Live Browser Automation

More Screenshots

Click any image to zoom in

AI terminal calling the browser_wait MCP tool while the 1DevTool Browser panel shows the page it is driving
Agent Input prompt asking the agent to use the onedevtool browser MCP tools in the 1DevTool Browser panel

Why You Need This

How this feature boosts your daily productivity

Browser automation normally means a second, empty browser: a fresh Chrome profile with no cookies, no logged-in session, and none of the state you spent the morning setting up. So the agent stalls at a login wall, or you paste credentials into a script. 1DevTool's Browser MCP points the agent at the browser already docked in your workspace. The agent opens a tab you can watch, drives the page you can see, and hands back a snapshot or a real screenshot when it needs to check its work — while typing into password fields stays blocked by policy and automation stays scoped to the project and tab you named.

How It Works

Get started in 4 simple steps

1
1

Open the page in the Browser panel

Dock the Browser panel on the page you care about. Your existing tabs, navigation history, and signed-in sessions are what the agent will work with.

2
2

Say "1devtool browser mcp" in your prompt

Mentioning 1devtool or onedevtool browser MCP routes the request to the visible Browser panel instead of an external Chrome session or a second agent terminal.

3
3

Watch the agent work the page

The agent opens and selects tabs, navigates, snapshots the page structure, clicks, types, selects options, presses keys, and calls browser_wait for text or load states.

4
4

Read the run back in Settings → MCP → Activity

Every call is retained with its status, duration, project, terminal, and a truncated input/output preview — searchable, and kept across app restarts.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Ask the agent to check the checkout
# It launches a separate, empty browser
# No cookies, no session
# Login wall on step one
# Paste a test account into the prompt
# Or click through the flow yourself

The 1DevTool Way

Say "1devtool browser mcp" in your prompt.
The agent drives the Browser panel you already have open.
Your tabs, your session, watched live.

Key Capabilities

Everything included with Live Browser Automation

Drive the Browser panel already open in your workspace, with its tabs and signed-in sessions
Open, list, and select tabs, then navigate, reload, and move back and forward
Click controls, type text, choose options, and press keys on the live page
Read the page as an accessibility snapshot with a reference for every interactive element
Wait on text appearing or disappearing and on load states instead of fixed sleeps
Capture an exact screenshot of the current tab and pull the page console logs
Stay scoped to one project and tab, with password and file inputs protected

Why It Matters

The productivity impact of having browser preview built into your workspace

Already Logged In

The agent inherits the session you have open, so a checkout or admin flow behind a login needs no test account and no pasted credentials.

You Can See It Happen

The page moves in front of you while the agent works, instead of a hidden browser you only learn about from the transcript.

Elements, Not Coordinates

A page snapshot gives the agent a reference for each interactive element, and references refresh after navigation so a stale handle cannot hit the wrong control.

Guardrails By Default

Automation is scoped to one project and tab, typing into password fields is blocked, and sensitive values come back redacted.

Ready to boost your workflow?

Download 1DevTool for free and experience Live Browser Automation along with 170 other features — all in one app.