Firecrawl launches /interact for natural-language browser actions

• Firecrawl launched /interact as a follow-on to /scrape, letting agents take browser actions in natural language so they can "click, fill, scroll" and pull deeper web data from the same page flow, according to the launch thread.
• Firecrawl's docs teaser positions /interact as the fast path for post-scrape automation, while also drawing a clear boundary: if you need "full browser control," the company says to use Playwright code instead.
• The new flow keeps state alive across sessions: Firecrawl says each /interact run gets a live shareable browser URL, and "persistent profiles" mean agents can log in once and resume without re-authenticating, per the feature thread.
• Firecrawl is also pitching the release as part of a broader agent onboarding path, with a supporting repost saying agents can choose between replacing fetch/search-style retrieval and moving into interactive browser work.

The new endpoint shortens the jump from extraction to automation. Firecrawl's launch thread describes the sequence as: first /scrape a page, then call /interact to perform actions with natural language. The practical change is that browsing and extraction no longer look like separate toolchains when an agent needs to go beyond static HTML.

Firecrawl says agents can "click, fill, scroll" to reach "deep web data" that would normally require a browser session launch thread. A supporting repost from Nick Scamara's demo adds that the same step can also be driven with code, not just natural-language instructions, which matters for teams that want an easier path first and more explicit control later.

Firecrawl is unusually direct about the tradeoff. In the product thread, it says teams needing "full browser control" should use Playwright code instead, even though it runs in the "same page, same session." The screenshot in that post shows a code-based app.interact call that clicks #next-page, waits for networkidle, then extracts the new page's title and article body interact docs.

That makes /interact look less like a Playwright replacement than a higher-level entry point: start with natural-language actions when the task is simple, then drop to code when determinism and exact page handling matter. Firecrawl also says every browser session has a live URL you can embed or share, and that persistent profiles preserve login state between runs feature thread.