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?
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]