Browser-use: use Chrome accessibility tree instead of screenshots
Replacing screenshot-based perception with the accessibility tree cuts token costs and makes element targeting deterministic, a practical swap for anyone building browser agents. Developers can replicate the CDP call chain or adopt browser-use's Browser Harness directly. The approach works with any Chromium-based browser, including Chrome and Edge, without extra dependencies.
