@mastra/browser-firecrawl

Headlines · 1

1. Oct 21
   Mastra explains Firecrawl browser provider, flags password exposure in traces

   Mastra published a walkthrough of @mastra/browser-firecrawl, a browser provider built by Firecrawl's team that it says gives an agent a hosted browser for pages behind a login without running Chromium locally, with a demo that logs into Sauce Labs' test store and checks out a backpack. Mastra says FirecrawlBrowser extends its AgentBrowser and exposes the same 16 browser tools by default, with the difference being that AgentBrowser launches Chromium locally with Playwright while FirecrawlBrowser connects to a Firecrawl session over CDP; sessions are tied to an agent thread, but the thread-to-session map lives in the server process, so restarts or another instance get a fresh browser with no cookies, and Firecrawl ends sessions after five minutes idle or ten minutes total by default. Mastra also warns that a password typed through the browser_type tool is recorded in memory and traces as plain text because the browser tool's field is called text rather than password; named profiles with saveChanges set to false let an agent start signed in without the model seeing the password.

   Mastra Blog · 🔥 0

Experience and discussion from the community

Share my @mastra/browser-firecrawl experienceAsk about @mastra/browser-firecrawl