Instruction
Defines the browser work Web4 should complete.
EXAMPLE TASK“Export yesterday's completed orders”Per-run task scope
AI BROWSER WORKFLOWS
Run browser tasks in natural language inside one saved profile
Web4 Browser · AI antidetect browser & multi-accounting workspace
Select a saved Web4 profile, describe the browser work in natural language, and run it with that profile's browser identity, session state, network context and execution context already attached.
HOW IT WORKSAI changes the execution surface—not the browser environment. The instruction defines the work; the selected saved profile remains the reference environment for that run.
Natural-language tasksSaved-profile contextManual · AI · Headless
AI is the control surface, not a new environment. The selected saved profile remains the reference for identity, session and network binding while run-specific browser state is created during execution.
THE EXECUTION MODEL
The instruction tells Web4 what to do. The saved profile tells it where that work belongs.
The instruction is a per-run task definition. The selected saved profile remains the browser environment for that run, so Web4 can reuse its existing identity, session, network and execution context before carrying out browser actions.
INPUT
OUTPUTS
P16
WHERE IT RUNS
OUTCOME
REVIEWABLE
WHAT TO DO
Saved Profile #16
REFERENCE ENVIRONMENTPersistent context (stays with the saved profile)
IdentitySaved
SessionAvailable
NetworkAttached
Execution contextProfile-owned
AI execution surface (happens inside the profile)
1Instruction receivedTask objective
2Profile context reusedExisting environment
3Browser actions runAI control surface
Task result
The outcome produced by this browser run.
Execution record
A reviewable record that supports later review, troubleshooting and handoff.
Instruction scope
The instruction describes the browser work for this run. It does not carry the saved profile's browser identity, session state or network routing.
Reference environment
Profile #16 remains the selected browser environment. Its identity, session, network and execution context are available to the AI workflow instead of being rebuilt for the task.
Run outputs
The task result belongs to the current run. Activity and execution records provide a reviewable trace for later review, troubleshooting and handoff.
CONTEXT REUSE
AI inherits the saved environment instead of recreating four separate layers.
The selected profile already owns browser identity, session state, network context and execution context. AI Browser Workflows reuse those profile-scoped layers; the control surface changes to AI, not the underlying browser environment.
REFERENCE ENVIRONMENT
Persistent
Saved Profile #16
One persistent browser environment
BROWSER IDENTITYIdentity
Profile-owned
SESSION STATESession
Profile-scoped
NETWORK CONTEXTNetwork
Environment-bound
EXECUTION CONTEXTExecution context
Same saved profile
Identity
Reused
Browser identity stays associated with Profile #16.
Session
Reused
Cookies, storage and login state remain profile-scoped.
Network
Reused
Per-profile routing and network context remain in the environment.
Execution context
Reused
The execution context remains with the same saved profile.
CONTROL SURFACE
AI Browser Workflow
Runs from Profile #16
Plan
Navigate
Act
Extract
AI executes tasks using the reused context.
The environment stays the same.
1Instruction
received→2Context
reused→3Actions
executed
received→2Context
reused→3Actions
executed
STAYS WITH THE SAVED PROFILE
Identity
Session
Network
Execution context
These layers belong to the profile and persist across runs.
WHAT CHANGES FOR THIS RUN
AI
Control surface: AI Browser Workflow
Only the control surface changes to AI. The environment does not.
Context reuse does not mean four new configurations are created for every AI task. The run starts from the browser environment the user already selected, while the instruction remains responsible for describing the work to perform.
TASK ANATOMY
Define the work.
Define the work.
Choose the environment. Run with AI.
A task has two independent inputs that come together for one AI browser run.
The instruction defines what to do. The saved profile defines where and how it runs.
1
WHAT TO DO
Instruction (per run)
Describe the task in natural language. Break it down into clear parts.
Objective
What is the main goal of this task?
Scope
Which sites or data should be included or excluded?
Expected Result
What output or outcome should be produced?
NATUREPer run•Can change every time
RUN STARTRUN END
AI BROWSER RUN
Plan
→
Navigate
→
Act
→
Extract
AI executes the task using the reused environment.
2
WHERE IT RUNS
Saved Profile (persistent)
Provides a ready-to-use browser environment. Context stays with the profile across runs.
Identity
PersistedBrowser fingerprint and device identity stay the same.
Session
PersistedCookies, local storage and login state are preserved.
Network
PersistedThe configured network binding is reused; route-derived IP and observable network signals follow the active connection.
Execution context
PersistedProfile-owned extensions and local configuration persist; current navigation, DOM state and run outputs remain run-specific.
NATUREPersistent•Stays with the profile
Instruction Per run
Defines what the AI needs to accomplish.
Saved Profile Persistent
Provides the environment to run the task in.
AI Browser Run
Instruction and environment come together for one run.
KEY TAKEAWAY
Change the instruction to change the work.
Change the profile to change the environment.
i
The instruction and the saved profile are independent. Many different instructions can run in the same profile. The same instruction can run in different profiles.
EXECUTION SURFACES
Choose how the browser is controlled without confusing the control method with the profile itself.
Manual browsing, AI Browser Workflows and Headless/CDP are different ways to run browser work. Skills & MCP extend repeatable steps and approved tool connections. The saved profile remains the browser environment underneath them.
| MODE | PRIMARY CONTROL | PROFILE RELATIONSHIP | NEXT |
|---|---|---|---|
| Manual Browser | A person drives the browser directly. | Opens the same saved profile and its existing context. | Profile context → |
| AI Browser Workflow | Natural-language instructions drive browser work. | Executes inside the selected saved profile. | This page → |
| Headless & CDP | Programmatic automation controls the browser. | Uses the same saved profile without rebuilding context. | Headless & CDP → |
| Skills & MCP | Reusable steps and approved MCP tools extend workflows. | Extends browser work around the profile; it is not a new identity layer. | Skills & MCP → |
One saved profile. Many control surfaces. Switching the control method never creates a new identity; it only changes how work gets done.
RECORDS & BOUNDARIES
Review the browser work clearly—
Review the browser work clearly—
without confusing records with external control.
Activity and execution records capture evidence around browser work. They support review, troubleshooting and handoff—while external platforms and their decisions remain outside Web4 control.
1BROWSER WORK HAPPENS
AI Browser Run
Workflow executes inside the selected browser environment.
Plan↓Navigate↓Act↓Extract
2REVIEWABLE EVIDENCE LAYER
Execution Record
Reviewable evidence around what happened in the browser work.
Activity & execution
Records describe work around the workflow.
Profile reference
The selected saved profile remains the environment reference.
Reviewable evidence — not a second browser identity
3POWERS REVIEW & COORDINATION
Review
Inspect records to understand what happened.
Troubleshoot
Use records as evidence when a workflow needs investigation.
Handoff
Give another authorized teammate context about what happened.
CONTROL
BOUNDARY
→
BOUNDARY
Web4 records what happens around browser work.
It does not control external platforms or their decisions.
4OUTSIDE WEB4 CONTROL
External platforms & their decisions
Outside Web4 controlBrowser identity remains the selected saved profile.
Network routing remains part of the browser environment.
AI is not the same thing as Headless/CDP.
External platform decisions remain external.
AI Browser Run
Workflow executes inside the browser environment.
Reviewable Record
Evidence around what happened.
Review, Troubleshoot, Handoff
Evidence for teams to understand and coordinate.
Control Over External Platform Decisions
External outcomes remain outside Web4 control.
i
The record layer is for evidence and coordination, not for altering external outcomes. Web4 helps you understand what happened around browser work; it does not change what external sites, accounts or services decide.
BUILD YOUR FIRST ENVIRONMENT
Start with one persistent, isolated browser profile.
Create a free account, then apply for Windows trial access when you are ready to test Web4 Browser. Trial access is by approval.
Apply for Free Trial Create Free AccountTrial access by approval.