What make browser tools sdk more efficient than just using playwright-cli? With playwright-cli agent typically executes code written with playwright too.
with playwright-cli, the agent makes reasoning decisions between each cli call. with browser-tools, the agent can write big playwright code blocks that execute in one go meaning less turns and the agent can select exactly what it needs from the result.
I think the code version of playwright-cli is still supported but we just use the default instructions given by the cli which push it towards per cli call usage
If you’re using a local provider, it can open browsers in headed mode so it can log in. For remote providers, you’ll need to ask the agent for the live url which will be a proxy feed of the page to log in
What make browser tools sdk more efficient than just using playwright-cli? With playwright-cli agent typically executes code written with playwright too.
Where do your sdk’s efficiency boosts come from?
with playwright-cli, the agent makes reasoning decisions between each cli call. with browser-tools, the agent can write big playwright code blocks that execute in one go meaning less turns and the agent can select exactly what it needs from the result.
I think the code version of playwright-cli is still supported but we just use the default instructions given by the cli which push it towards per cli call usage
[flagged]
Does it use the user login or open a headless broswer?
If you’re using a local provider, it can open browsers in headed mode so it can log in. For remote providers, you’ll need to ask the agent for the live url which will be a proxy feed of the page to log in
Yeah to get any serious attention, publish the 26 tasks, and compare the session and tokens before you make such claims.
As stated on the website, full methodology and results are available here: https://github.com/saffron-health/libretto/tree/main/package...
[flagged]