Agent Settings
Learn how to configure the agent
Overview
The Agent
class is the core component of Browser Use that handles browser automation. Here are the main configuration options you can use when initializing an agent.
Basic Settings
Required Parameters
task
: The instruction for the agent to executellm
: A chat model instance. See Supported Models for supported models.
Agent Behavior
Control how the agent operates:
Behavior Parameters
controller
: Registry of functions the agent can call. Defaults to base Controller. See Custom Functions for details.use_vision
: Enable/disable vision capabilities. Defaults toTrue
.- When enabled, the model processes visual information from web pages
- Disable to reduce costs or use models without vision support
- For GPT-4o, image processing costs approximately 800-1000 tokens (~$0.002 USD) per image (but this depends on the defined screen size)
save_conversation_path
: Path to save the complete conversation history. Useful for debugging.override_system_message
: Completely replace the default system prompt with a custom one.extend_system_message
: Add additional instructions to the default system prompt.
Vision capabilities are recommended for better web interaction understanding, but can be disabled to reduce costs or when using models without vision support.
Reuse Existing Browser Context
By default browser-use launches its own builtin browser using playwright chromium.
You can also connect to a remote browser or pass any of the following
existing playwright objects to the Agent: page
, browser_context
, browser
, browser_session
, or browser_profile
.
These all get passed down to create a BrowserSession
for the Agent
:
For example, to connect to an existing browser over CDP you could do:
For example, to connect to a local running chrome instance you can do:
See Connect to your Browser for more info.
You can reuse the same BrowserSession
after an agent has completed running.
If you do nothing, the browser will be automatically closed on run()
completion only if it was launched by us.
Running the Agent
The agent is executed using the async run()
method:
max_steps
(default:100
) Maximum number of steps the agent can take during execution. This prevents infinite loops and helps control execution time.
Agent History
The method returns an AgentHistoryList
object containing the complete execution history. This history is invaluable for debugging, analysis, and creating reproducible scripts.
The AgentHistoryList
provides many helper methods to analyze the execution:
final_result()
: Get the final extracted contentis_done()
: Check if the agent completed successfullyhas_errors()
: Check if any errors occurredmodel_thoughts()
: Get the agent’s reasoning processaction_results()
: Get results of all actions
For a complete list of helper methods and detailed history analysis capabilities, refer to the AgentHistoryList source code.
Run initial actions without LLM
With this example you can run initial actions without the LLM. Specify the action as a dictionary where the key is the action name and the value is the action parameters. You can find all our actions in the Controller source code.
Run with message context
You can configure the agent and provide a separate message to help the LLM understand the task better.
Run with planner model
You can configure the agent to use a separate planner model for high-level task planning:
Planner Parameters
planner_llm
: A chat model instance used for high-level task planning. Can be a smaller/cheaper model than the main LLM.use_vision_for_planner
: Enable/disable vision capabilities for the planner model. Defaults toTrue
.planner_interval
: Number of steps between planning phases. Defaults to1
.
Using a separate planner model can help:
- Reduce costs by using a smaller model for high-level planning
- Improve task decomposition and strategic thinking
- Better handle complex, multi-step tasks
The planner model is optional. If not specified, the agent will not use the planner model.
Optional Parameters
message_context
: Additional information about the task to help the LLM understand the task better.initial_actions
: List of initial actions to run before the main task.max_actions_per_step
: Maximum number of actions to run in a step. Defaults to10
.max_failures
: Maximum number of failures before giving up. Defaults to3
.retry_delay
: Time to wait between retries in seconds when rate limited. Defaults to10
.generate_gif
: Enable/disable GIF generation. Defaults toFalse
. Set toTrue
or a string path to save the GIF.
Memory
Memory management in browser-use has been significantly improved since version 0.3.2. The agent’s context handling and state management are now robust enough that the previous memory system (mem0
) is no longer needed or supported.
The agent maintains its context and task progress through:
- Detailed history tracking of actions and results
- Structured state management
- Clear goal setting and evaluation at each step
The enable_memory
parameter has been removed as the new system provides better context management by default.
If you’re upgrading from an older version that used enable_memory
, simply remove this parameter. The agent will automatically use the improved context management system.