Skip to content

Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.

System prompt efficiency_guidelines

Magnus Müller1596f25a5af6
diff --git a/browser_use/agent/system_prompt.md b/browser_use/agent/system_prompt.md
index ceda7ef73..83640b832 100644
--- a/browser_use/agent/system_prompt.md
+++ b/browser_use/agent/system_prompt.md
@@ -136,16 +136,17 @@ If you are allowed multiple actions, you can specify multiple actions in the lis
<efficiency_guidelines>
You can output multiple actions in one step. Try to be efficient where it makes sense. Do not predict actions which do not make sense for the current page.
-
**Recommended Action Combinations:**
- `input_text` + `click_element_by_index` → Fill form field and submit/search in one step
-- `input_text` + `input_text` → Fill form fields
-- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows
+- `input_text` + `input_text` → Fill multiple form fields
+- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows (when the page does not navigate between clicks)
- `scroll` with num_pages 10 + `extract_structured_data` → Scroll to the bottom of the page to load more content before extracting structured data
- File operations + browser actions
Do not try multiple different paths in one step. Always have one clear goal per step.
-Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, like do not use click and then go to url, because you would not see if the click was successful or not.
+Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, e.g.
+- do not use click_element_by_index and then go_to_url, because you would not see if the click was successful or not.
+- or do not use switch_tab and switch_tab together, because you would not see the state in between.
</efficiency_guidelines>
<reasoning_rules>
diff --git a/browser_use/agent/system_prompt_flash.md b/browser_use/agent/system_prompt_flash.md
index cb2bdefbe..a2f9257fc 100644
--- a/browser_use/agent/system_prompt_flash.md
+++ b/browser_use/agent/system_prompt_flash.md
@@ -133,16 +133,17 @@ If you are allowed multiple actions, you can specify multiple actions in the lis
<efficiency_guidelines>
You can output multiple actions in one step. Try to be efficient where it makes sense. Do not predict actions which do not make sense for the current page.
-
**Recommended Action Combinations:**
- `input_text` + `click_element_by_index` → Fill form field and submit/search in one step
-- `input_text` + `input_text` → Fill form fields
-- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows
+- `input_text` + `input_text` → Fill multiple form fields
+- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows (when the page does not navigate between clicks)
- `scroll` with num_pages 10 + `extract_structured_data` → Scroll to the bottom of the page to load more content before extracting structured data
- File operations + browser actions
Do not try multiple different paths in one step. Always have one clear goal per step.
-Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, like do not use click and then go to url, because you would not see if the click was successful or not.
+Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, e.g.
+- do not use click_element_by_index and then go_to_url, because you would not see if the click was successful or not.
+- or do not use switch_tab and switch_tab together, because you would not see the state in between.
</efficiency_guidelines>
<reasoning_rules>
diff --git a/browser_use/agent/system_prompt_no_thinking.md b/browser_use/agent/system_prompt_no_thinking.md
index a3038cb6d..a79cb569b 100644
--- a/browser_use/agent/system_prompt_no_thinking.md
+++ b/browser_use/agent/system_prompt_no_thinking.md
@@ -135,16 +135,17 @@ If you are allowed multiple actions, you can specify multiple actions in the lis
<efficiency_guidelines>
You can output multiple actions in one step. Try to be efficient where it makes sense. Do not predict actions which do not make sense for the current page.
-
**Recommended Action Combinations:**
- `input_text` + `click_element_by_index` → Fill form field and submit/search in one step
-- `input_text` + `input_text` → Fill form fields
-- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows
+- `input_text` + `input_text` → Fill multiple form fields
+- `click_element_by_index` + `click_element_by_index` → Navigate through multi-step flows (when the page does not navigate between clicks)
- `scroll` with num_pages 10 + `extract_structured_data` → Scroll to the bottom of the page to load more content before extracting structured data
- File operations + browser actions
Do not try multiple different paths in one step. Always have one clear goal per step.
-Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, like do not use click and then go to url, because you would not see if the click was successful or not.
+Its important that you see in the next step if your action was successful, so do not chain actions which change the browser state multiple times, e.g.
+- do not use click_element_by_index and then go_to_url, because you would not see if the click was successful or not.
+- or do not use switch_tab and switch_tab together, because you would not see the state in between.
</efficiency_guidelines>
<reasoning_rules>