Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data.
scrape failed because content is behind JavaScript interactionsearch instead# 1. Scrape a page (scrape ID is saved automatically)
firecrawl scrape "<url>"
# 2. Interact with the page using natural language
firecrawl interact --prompt "Click the login button"
firecrawl interact --prompt "Fill in the email field with test@example.com"
firecrawl interact --prompt "Extract the pricing table"
# 3. Or use code for precise control
firecrawl interact --code "agent-browser click @e5" --language bash
firecrawl interact --code "agent-browser snapshot -i" --language bash
# 4. Stop the session when done
firecrawl interact stop
| Option | Description |
|---|---|
| --------------------- | ------------------------------------------------- |
--prompt | Natural language instruction (use this OR --code) |
--code | Code to execute in the browser session |
--language | Language for code: bash, python, node |
--timeout | Execution timeout (default: 30, max: 300) |
--scrape-id | Target a specific scrape (default: last scrape) |
-o, --output | Output file path |
Use --profile on the scrape to persist browser state (cookies, localStorage) across scrapes:
# Session 1: Login and save state
firecrawl scrape "https://app.example.com/login" --profile my-app
firecrawl interact --prompt "Fill in email with user@example.com and click login"
# Session 2: Come back authenticated
firecrawl scrape "https://app.example.com/dashboard" --profile my-app
firecrawl interact --prompt "Extract the dashboard data"
Read-only reconnect (no writes to profile state):
firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes
interact requires a scrape ID from a previous firecrawl scrape call--scrape-id for subsequent interact callsfirecrawl interact stop to free resources when done--scrape-id共 1 个版本
暂无安全检测报告