Playwright and browser security reminder.
We saw a post suggesting that you delete Playwright because it bundles browsers with CVEs. That is a misconception. Do not delete Playwright๐. Here is how it works and what you should do.
No Playwright package bundles a browser. Agents on Playwright MCP or CLI run your stable Chrome, which gets Chrome's security updates, with the sandbox on.
๐ค If you use Playwright MCP or the Playwright CLI
They use the stable Chrome / Edge on your machine, so it gets its normal updates. No config edit is needed.
๐งช If you use the test runner
When you run npx playwright install, Playwright downloads Chrome for Testing, pinned to the build we tested that release against. The pin is on purpose. Your tests run on the same browser on every laptop and CI machine, and a browser
update cannot suddenly break your suite. You choose when to move by upgrading Playwright. New releases usually pin a build ahead of stable Chrome, so you see breakage before your users do.
We recommend this for full e2e test suites on your own trusted app. This build can miss Chrome security fixes until the next Playwright release, and by default it runs with the sandbox off. Do not use it on the hostile web.
๐ If you use the library API
chromium.launch() has the same defaults: the pinned build with the sandbox off. If your code visits pages you don't control (scrapers, agent scripts), max out protection:
chromium.launch({ channel: 'chrome', chromiumSandbox: true })
๐ Always keep Chrome / Edge updated. Some bugs can escape a sandbox.
Happy testing!
Introducing Expand Search ๐ Pareto frontier search for your agent.
Two weeks ago we launched Expand Fetch. But which pages should your agent fetch?
We need search. And existing providers are either too expensive or low quality.
Expand Search costs $1.50 per 1,000 searches, with the highest average answer accuracy across the five public benchmarks in our evaluation.
Sign up in the next 24 hours and get 50,000 free credits.
Never trust a verbal job offer.
I recently had one from a frontier AI lab.
โ Reference checks came back positive
โ Visa work started and was moving forward
Two weeks later I got an SMS: "We are not able to move forward" while waiting for the written offer.
The reason given was that theyโre no longer hiring seniors and are focusing on juniors and new grads instead. ๐คฏ
Is that the real reason? Who knows. I liked their product. I was hyped.
Moving on and talking to more companies. Especially curious about computer use, browser use, RL environments, and coding agents right now.
Introducing Expand Fetch, a new way to scrape and crawl the web.
Your agent has never seen the web. No wonder it gets basic questions wrong.
Traditional Markdown APIs lose critical details. So we trained two System one models to change that:
Iris, a vision model that sees pages like you do, preserving tables, icons, and layouts.
X-Ray, a JSON model that uncovers the hidden data behind every page.
Every fetch also comes with a Wayback Machine. Every line links back to its source, so you can verify exactly what your agent saw.
Three products. One API.
On our benchmark of 1,094 questions across 326 challenging web pages, agents using Expand got 74% right. The next best API got 55%.
Available today at $1 per 1,000 fetches.
Try it at https://t.co/x4SDYsUX25
@TimSuchanek Very nice! ๐
I just recently had a case where my agent didnโt receive the siteโs content correctly.
Big fan of the Wayback machine too - great for research and citations.