HEADLESS & CDP AUTOMATION

Run browser automation inside the same saved profile context

Web4 Browser · AI antidetect browser & multi-accounting workspace

Headless and CDP-compatible automation run inside the same saved profile, reusing its browser identity, session state and configured network context while the current run creates temporary execution state.

HOW IT WORKS Switching the control surface changes how the browser is operated, not which saved profile owns the environment. Manual browsing, AI Browser Workflows and CDP-compatible automation can all operate that same profile without rebuilding a second identity.

Explore the execution model ↓ Inspect records & boundaries →

Saved profile context CDP control Reviewable records Manual · AI · Headless continuity

Control changes; context stays. Headless/CDP changes the runtime and controller while the saved profile remains the continuity boundary for identity, session and configured network context.

WEB4 PRODUCT ARCHITECTUREThis page establishes the programmatic runtime layer: the same saved profile can be operated through Headless/CDP without rebuilding the browser identity, session state or configured network context it already carries.

Web4 Browser uses the saved browser profile as the continuity boundary across identity, network configuration, session state and browser execution context. Headless/CDP owns the programmatic runtime and control evidence for that system.

View the full Web4 capability architecture

REFERENCE SCOPE

This page is the Web4 reference for: Headless/CDP runtime; programmatic browser control; execution and record boundary; queue, recovery and handoff; reusable browser routines; saved-profile continuity across control surfaces.

CONTROL SURFACES

Choose the control surface without changing the profile foundation

Different ways to operate the browser should not silently create different identities, sessions or network bindings. The same saved profile foundation remains the reference environment.

Mode	Primary Control	Profile Relationship	Best Use
Manual Browser	A person drives the browser directly.	Operates inside the same saved profile.	Ad-hoc exploration, research and verification.
AI Browser Workflow	Natural-language instructions drive browser work.	Works inside the same saved profile.	Guided tasks and multi-step flows with human review.
Headless & CDP	Programmatic automation via a CDP-compatible control path.	Runs inside the same saved profile without rebuilding context.	High-volume routines, integrations, scheduled or API-driven work.
Skills & MCP	Reusable steps and approved MCP tool connections.	Built on top of the same saved-profile foundation.	Standardized operations, team sharing and approved tool use.

EXECUTION & RECORD BOUNDARY

Automate inside the browser context — keep external decisions outside Web4

Web4 records what happens inside the browser environment. External websites, accounts, APIs and their policies remain outside the product boundary.

Saved Profile (Foundation)

Browser identity
Session state
Proxy & network
Local environment

Context is preserved

Headless / CDP Runtime

Programmatic control executes via a CDP-compatible path inside the saved profile.

Browser Execution (Inside Web4)

Pages loaded
Interactions performed
Network requests
Data extracted

Reviewable Record (Inside Web4)

Steps & actions
Timestamps
Artifacts captured
Network context
Extracted data / outputs

Evidence you can review

Outside Web4 Boundary

External Platforms & Decisions

Websites, accounts, APIs, business logic and platform decisions remain outside our control.

Web4 records what happens in-browser.We do not control external websites, accounts, APIs or platform decisions.

QUEUE, RECOVER, HAND OFF

Queue, recover, and hand off browser work without losing context

Keep long-running or complex jobs moving. Recover, review or hand off at any step—inside the same saved profile reference.

Queued Runs

Schedule or queue headless jobs around the selected saved profile.

Queued

Headless & Resume

Retry on failure or resume from the last successful step.

Resumable

Captured Artifacts

Screenshots, logs and extracted outputs stay reviewable around the run.

Captured

Operator Handoff

Pause and assign an authorized human operator without rebuilding context.

Ready for handoff

Review & Troubleshoot

Review records, artifacts and network context before rerunning.

Under review

All steps run inside the same saved profile.Identity, session, network binding and profile-owned context remain anchored to the same profile.

REPEATABLE WORK → REUSABLE LAYER

Turn repeated browser routines into reusable structured work

What starts as repeated headless tasks can evolve into reusable building blocks, approved tools and team-shared workflows.

Repeated Runs

Run headless browser work repeatedly to solve a consistent need.

Capture patterns

Reusable Steps

Normalize successful steps into reusable building blocks.

Standardize actions

Structured Inputs

Define the inputs, parameters and expected outputs.

Make it predictable

Approved Tools & Connections

Connect approved APIs, data sources or internal systems.

Extend safely

Reusable Skills & MCP Workflows

Share with your team and run at scale inside the same saved-profile foundation.

Consistent. Reviewable. Safe.

WHAT STAYS WITH THE SAVED PROFILE

Headless/CDP automation uses the same saved profile foundation

These core elements remain anchored to the saved profile, no matter how the browser is controlled. Run-specific navigation and temporary execution state remain separate.

✓

Browser Identity

Same coherent browser/device identity reference.

UA, platform & language
Canvas, WebGL & font signals
Extensions and plugins

✓

Session State

Cookies, local storage and saved login state remain profile-scoped.

Cookies & session cookies
Local storage & IndexedDB
Service workers & cache

✓

Proxy & Network Context

Configured network binding remains with the profile; observed route state stays contextual.

Per-profile binding
DNS & network routing
Active exit remains contextual

✓

Execution Context

Profile-owned local environment and execution settings remain available.

Timezone & locale
Screen & device settings
Permissions & policies

✓

Reviewable Evidence

Execution records and artifacts stay associated with the run and profile reference for later review.

Step-by-step records
Artifacts & screenshots
Network logs & data

NEXT LAYER

Package repeatable browser work as Skills & MCP workflows

Build on the same saved-profile foundation with reusable, approved workflows that scale across your team.

Explore Skills & MCP →Back to Features

Browser Identity
& Profile Foundation→Headless / CDP
Runtime→Recorded Execution
& Evidence→Skills & MCP
Workflows

Automate confidently inside your saved profile—with records you can review.

Keep context consistent, keep control flexible, and keep the boundary around external outcomes explicit.

Request Access →