- monitor create --help: a 'Target modes' section distinguishing single page,
URL batch, whole-site crawl, and web-search targets.
- On create, print the Cloud dashboard link + a run-now hint (interactive only,
so pipes/--output stay clean).
- SKILL.md: a target-mode table so agents pick the right flags.
- Bump version to 1.19.21.
Bump CLI version and add YAML dependency; implement native MCP installers for Hermes and OpenClaw and a hosted Firecrawl MCP URL. Normalize agent aliases and extend setup/installMcp to handle special launchers (hermes, openclaw, and --agent all) and to invoke add-mcp with the hosted MCP URL and transport option. Add functions to write Hermes config and configure OpenClaw via its CLI, and add installSkillsForAgent helper. Extend launch command to recognize hermes/openclaw targets, run their MCP installers, optionally install skills (new --skip-skills flag), and launch with correct args. Update command help text and expand tests to cover these new behaviors.
Introduce an interactive picker for the `launch` command when no agent argument is provided, and require an explicit target in non-interactive mode. Adds helper functions (promptInput, pickLaunchTarget, supportedTargets), makes targetName optional in handleLaunchCommand, and validates that extraArgs cannot be provided without an explicit target. Also adds a `launcher` alias for the command and updates error messages. Tests updated to cover the non-interactive error case.
* feat(cli): add generic feedback command
* chore: bump version to 1.19.7
* chore: bump version to 1.19.8
* feat(cli): add endpoint feedback opt-out
* chore: bump version to 1.19.9
* chore: bump version to 1.19.10
* Add firecrawl doctor command (ENG-4883)
* Fix doctor support diagnostics
* Refine doctor credit label
* Polish doctor option handling
* Respect terminal color support in doctor
* Bump CLI version to 1.18.7
* Refactor package dependencies to replace '@mendable/firecrawl-js' with 'firecrawl' in package.json and update related imports across the codebase. This change ensures consistency and aligns with the new package naming convention.
* Update import statement for Firecrawl in client.ts to use named import for consistency with new package structure.
Export and update monitor creation helpers to accept a --goal and single --page shorthand (constructs urls from page when provided) and include goal in the request body. Add CLI options and help text for --goal and --page, support goal on monitor update, and adjust example usage. Add unit tests for buildCreateBody covering goal and page behavior. Update README and SKILL docs to document monitor usage and guidance. Bump package version to 1.18.1.
During install, show "Installing core firecrawl skills..." and
"Installing skills to build with firecrawl..." instead of the raw repo
names firecrawl/cli and firecrawl/skills. SKILL_REPO_LABELS map drives
the friendly text.
In the next-steps summary, split into two distinct groupings:
1. "Connect & interact with the web (direct or in your AI agent)"
with scrape/search/interact examples showing the natural language
prompt next to the equivalent CLI command.
2. "Building with firecrawl?" at the bottom, pointing at the build
skills with a concrete business example.
MCP + --help entries sit between the two sections as general utilities.
Bumped to 1.14.7.
Parse '(Found|Installed) N skills' from captured npx skills output and
sum across both repos so the post-install summary shows
"✓ Installed 14 skills across your AI coding agents" instead of vague
text.
Collapse the next-steps block from 18 lines to 7: drop the 4 example
prompts in favor of one of each (AI prompt + direct CLI), plus the
MCP install hint and the --help pointer. Each entry uses padded labels
("Ask your AI:", "Run direct: ", "Add MCP: ", "All commands:") so
the commands align in a column.
stepIntegrations and runNonInteractive both thread the count through
to printNextSteps. Tests still mock execSync as undefined, so
parseSkillCount handles the empty case. Bumped to 1.14.3.
Replace the noisy 'npx skills add' inherited stdout (banner, +/symlink
table, security report, ~80 lines per repo) with a single line per repo:
" ✓ firecrawl/cli" / " ✓ firecrawl/skills". TTY runs get a transient
"↓ <repo>" indicator while the install is in flight; non-TTY runs (CI,
piped) get only the final line.
Replace the trailing "Setup complete!" line with a printNextSteps()
block that surfaces:
- what just happened (skills installed globally)
- what firecrawl is for (search, scrape, crawl, interact)
- 4 example prompts (2 build-skill triggers, 2 direct CLI calls)
- pointer to firecrawl --help
Both interactive and non-interactive init paths use the same helpers,
so output is consistent regardless of how users enter the flow.
Bumped to 1.14.2.
when this cli is launched via 'npx -y firecrawl-cli@VERSION', npm injects
npm_command/npm_lifecycle_event/npm_execpath/INIT_CWD into the process
env. those vars leak into nested execSync('npx -y skills add ...') calls
and cause the loop's second iteration to silently exit after the first
install completes — published 1.14.0 only installs from firecrawl/cli
even though SKILL_REPOS contains both repos.
cleanNpmEnv() in skills-install.ts strips those vars; init.ts and
setup.ts pass it as the env to every nested execSync. added a
regression test that primes process.env with the leaking vars and
asserts every install call sees a clean env. bumped to 1.14.1.
Developers Digest