Firecrawl Interact
- 60.3k installs
- 561 repo stars
- Updated August 4, 2026
- firecrawl/cli
firecrawl-interact is a Firecrawl CLI agent skill that controls live browser sessions on scraped pages for developers who need clicks, form fills, navigation, and extraction beyond static scraping.
About
firecrawl-interact is a firecrawl/cli skill for controlling live browser sessions on any scraped page by clicking buttons, filling forms, navigating multi-step flows, and extracting data with natural language prompts or code. Developers invoke it when static scrapes fail on JavaScript-rendered content, login walls, pagination, infinite scroll, checkout wizards, or authenticated pages via profiles. The skill extends Firecrawl from read-only scraping to interactive automation for agents and CLI workflows. It supports profiles to persist browser state across scrapes and handles authenticated scraping before data extraction.
- Control live browser sessions after scraping
- Perform natural-language clicks, form fills, pagination, and infinite scroll
- Handle authenticated flows and multi-step wizards
Firecrawl Interact by the numbers
- 60,303 all-time installs (skills.sh)
- +815 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #21 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/firecrawl/cli --skill firecrawl-interactAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 60.3k |
|---|---|
| repo stars | ★ 561 |
| Security audit | 1 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | firecrawl/cli ↗ |
How do you interact with pages using Firecrawl?
Control a live browser session on any scraped page, enabling clicks, form fills, navigation, and data extraction when static scraping is insufficient.
Who is it for?
Developers automating JavaScript-heavy sites, authenticated scrapes, paginated listings, and multi-step forms with Firecrawl browser sessions.
Skip if: Simple static HTML pages that full Firecrawl scrape already returns completely without clicks, logins, or scroll interaction.
When should I use this skill?
User needs Firecrawl browser clicks, form fills, login flows, pagination, infinite scroll, or interaction after a scrape failed.
What you get
Live browser session actions, extracted interactive page data, and completed multi-step navigation flows
- Interactive session extraction results
- Completed navigation flow logs
- Authenticated page data exports
Files
firecrawl interact
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.
When to use
- Content requires interaction: clicks, form fills, pagination, login
scrapefailed because content is behind JavaScript interaction- You need to navigate a multi-step flow
- Last resort in the workflow escalation pattern: search → scrape → map → crawl → interact
- Never use interact for web searches — use
searchinstead
Quick start
# 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 stopOptions
| Option | Description |
|---|---|
--prompt <text> | Natural language instruction (use this OR --code) |
--code <code> | Code to execute in the browser session |
--language <lang> | Language for code: bash, python, node |
--timeout <seconds> | Execution timeout (default: 30, max: 300) |
--scrape-id <id> | Target a specific scrape (default: last scrape) |
-o, --output <path> | Output file path |
Profiles
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-changesTips
- Always scrape first —
interactrequires a scrape ID from a previousfirecrawl scrapecall - The scrape ID is saved automatically, so you don't need
--scrape-idfor subsequent interact calls - Use
firecrawl interact stopto free resources when done - For parallel work, scrape multiple pages and interact with each using
--scrape-id
See also
- firecrawl-scrape — try scrape first, escalate to interact only when needed
- firecrawl-search — for web searches (never use interact for searching)
- firecrawl-agent — AI-powered extraction (less manual control)
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669Forks & variants (1)
Firecrawl Interact has 1 known copy in the catalog totaling 22 installs. They canonicalize to this original listing.
- firecrawl - 22 installs
How it compares
Use firecrawl-interact when pages need clicks or logins; use plain Firecrawl scrape for static HTML extraction.
FAQ
What does firecrawl-interact add over static Firecrawl scraping?
firecrawl-interact controls a live browser session to click, fill forms, navigate flows, and extract data when static scraping fails on JavaScript-rendered, paginated, or login-protected pages.
When should developers use firecrawl-interact?
Developers use firecrawl-interact for logging into sites, submitting forms, clicking pagination or infinite scroll, navigating checkout wizards, or extracting content that requires interaction beyond a simple scrape.
Can firecrawl-interact handle authenticated pages?
firecrawl-interact supports authenticated scraping via Firecrawl profiles and live session control, enabling sign-in flows before data extraction on protected or session-dependent pages.
Is Firecrawl Interact safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.