This is a problem I discovered after recently using various browser uae heavily.
I plan to make a lightweight tool to try to solve these problems.
If it is mature and effective, it will be open sourced: browser use The current main problems are: Fragmentation of the control plane: Extension, Computer Use, CDP, Playwright, browser-use, browser-harness each maintain different connection and profile states.
Missing Browser Identity Binding: There is both "Logged in regular Chrome" and "Controllable but not logged in Isolated Chrome" on the same machine.
After the connection fails, the wrong profile is automatically switched, resulting in deterministic failure and repeated execution.
Each rerun will re-feed the complete tasks, skills, history and page status into the large model.
Fixed waits, wide selectors, coordinate operations, and complex contenteditable overlays.
Lack of cross-run circuit breaker: Confirmed auth_missing and cdp_unreachable are still going through the complete process in the next round.
The core thing is that most of the current browser use solutions rely too much on UI control, which is wrong from the beginning and very limiting.