Symptom

The agent clicks the dropdown, then fails or loops trying to choose an option.

Evidence what you'll see

Reported as a regression: 0.5.11 worked, 0.7.x fails
Logs show 'element not found' on the second step

Cause

Many dropdowns are custom listboxes whose options only appear in the page after a click, so the element list the agent read earlier is out of date.

Fix steps

0 of 4 done

Step 1Check whether the control is a native <select> or a custom listbox.
Step 2Have the agent re-read the options after opening the dropdown, not before.
Step 3Treat 'element not found' on the next step as a sign to take a new page snapshot, not to retry the same index.
Step 4If you depend on it, pin to the last version that worked for you.

Your check marks stay in this browser only.

Verify the fix worked

The agent selects the target option on the reported form, and the form value changes.

Did this fix it?

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

browser-use issue #2867 ↗

Provided as is, without warranty. Test in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change