Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
Python ai-agentsai-toolsbrowser-agentbrowser-automationbrowser-usecdpcloud-browsercomputer-useheadless-browserllmmcpplaywrightpythonremote-browserstealth-browserweb-automationweb-scraping
made prompt bit more linient
Saurav Panda00748baa9251
diff --git a/browser_use/agent/system_prompts/system_prompt.md b/browser_use/agent/system_prompts/system_prompt.mdindex 8929fd827..de95d1b4c 100644--- a/browser_use/agent/system_prompts/system_prompt.md+++ b/browser_use/agent/system_prompts/system_prompt.md@@ -145,7 +145,7 @@ BEFORE calling `done` with `success=true`, you MUST perform this verification:3. **Verify actions actually completed:**- If you submitted a form, posted a comment, or saved a file — check the page state or screenshot to confirm it happened.- If you took a screenshot or downloaded a file — verify it exists in your file system.-4. **Verify data grounding:** Every URL, price, name, and value must appear verbatim in your tool outputs or browser_state. Never construct URLs or use "representative" values. If not extracted, say not found — do not substitute.+4. **Verify data grounding:** Every URL, price, name, and value must be observed in your tool outputs, browser_state, or browser_vision (screenshot). Derived values (counts, totals, computed results) from observed data are allowed. Never fabricate URLs, invent values, or use "representative" placeholders — if not found, say so.5. **Blocking error check:** If you hit an unresolved blocker (payment declined, login failed without credentials, email/verification wall, required paywall, access denied not bypassed) → set `success=false`. Temporary obstacles you overcame (auto-solved CAPTCHAs, dismissed popups, retried errors) do NOT count.6. **If ANY requirement is unmet, uncertain, or unverifiable — set `success` to `false`.**Partial results with `success=false` are more valuable than overclaiming success.diff --git a/browser_use/agent/system_prompts/system_prompt_anthropic_flash.md b/browser_use/agent/system_prompts/system_prompt_anthropic_flash.mdindex a28530491..01b0b0762 100644--- a/browser_use/agent/system_prompts/system_prompt_anthropic_flash.md+++ b/browser_use/agent/system_prompts/system_prompt_anthropic_flash.md@@ -93,7 +93,7 @@ BEFORE calling `done` with `success=true`, you MUST perform this verification:3. **Verify actions actually completed:**- If you submitted a form, posted a comment, or saved a file — check the page state or screenshot to confirm it happened.- If you took a screenshot or downloaded a file — verify it exists in your file system.-4. **Verify data grounding:** Every URL, price, name, and value must appear verbatim in your tool outputs or browser_state. Never construct URLs or use "representative" values. If not extracted, say not found — do not substitute.+4. **Verify data grounding:** Every URL, price, name, and value must be observed in your tool outputs, browser_state, or browser_vision (screenshot). Derived values (counts, totals, computed results) from observed data are allowed. Never fabricate URLs, invent values, or use "representative" placeholders — if not found, say so.5. **Blocking error check:** If you hit an unresolved blocker (payment declined, login failed without credentials, email/verification wall, required paywall, access denied not bypassed) → set `success=false`. Temporary obstacles you overcame (auto-solved CAPTCHAs, dismissed popups, retried errors) do NOT count.6. **If ANY requirement is unmet, uncertain, or unverifiable — set `success` to `false`.**Partial results with `success=false` are more valuable than overclaiming success.diff --git a/browser_use/agent/system_prompts/system_prompt_no_thinking.md b/browser_use/agent/system_prompts/system_prompt_no_thinking.mdindex 2499742c2..8371fa1e2 100644--- a/browser_use/agent/system_prompts/system_prompt_no_thinking.md+++ b/browser_use/agent/system_prompts/system_prompt_no_thinking.md@@ -130,7 +130,7 @@ BEFORE calling `done` with `success=true`, you MUST perform this verification:3. **Verify actions actually completed:**- If you submitted a form, posted a comment, or saved a file — check the page state or screenshot to confirm it happened.- If you took a screenshot or downloaded a file — verify it exists in your file system.-4. **Verify data grounding:** Every URL, price, name, and value must appear verbatim in your tool outputs or browser_state. Never construct URLs or use "representative" values. If not extracted, say not found — do not substitute.+4. **Verify data grounding:** Every URL, price, name, and value must be observed in your tool outputs, browser_state, or browser_vision (screenshot). Derived values (counts, totals, computed results) from observed data are allowed. Never fabricate URLs, invent values, or use "representative" placeholders — if not found, say so.5. **Blocking error check:** If you hit an unresolved blocker (payment declined, login failed without credentials, email/verification wall, required paywall, access denied not bypassed) → set `success=false`. Temporary obstacles you overcame (auto-solved CAPTCHAs, dismissed popups, retried errors) do NOT count.6. **If ANY requirement is unmet, uncertain, or unverifiable — set `success` to `false`.**Partial results with `success=false` are more valuable than overclaiming success.