Tags: firecrawl/cli
Tags
Fix CI: remove stray package-lock.json, reformat setup.ts with pinned… … prettier package-lock.json was accidentally committed in #206 (an npm install artifact — this repo is pnpm-managed). bun prefers it over pnpm-lock.yaml in release-binaries, and its migration fails under --frozen-lockfile. Remove it and gitignore it. setup.ts was formatted by prettier 3.9.6 from that same npm node_modules; CI pins 3.7.4 via pnpm-lock.yaml. Reformatted with 3.7.4. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
release: 1.22.0 (#202) Developer search is a lean agent surface: query and --limit only. All filter flags removed (breaking): --passages, --types, --repos, --sources, --language, --topic, --license, --min-stars, --max-stars, --archived, --fork, --skills-only. Scoping intent belongs in the query text.
release: 1.21.0 (#197) Developer search passages are now shaped server-side (search#843 policy): the CLI trusts passage_budget_applied responses and keeps a legacy local cut only for older servers. Removes the short-lived --passage-budget flag before it ever shipped in a release.
fix: describe the research paper index accurately across CLI surfaces (… …#186) * fix(research): describe the real paper corpus in CLI help Why: over 40 agent traces, 8/8 biomedical CLI runs read the root-help research line ("Research arXiv papers and GitHub history"), concluded the index was arXiv-only, and hand-scraped PubMed instead of ever running `firecrawl research`. The index is ~43M abstracts, ~90% biomedical. The group description is the single highest-leverage string: it renders both in `firecrawl --help` and as the `firecrawl research --help` header. Summary: - research group description now names the corpus (PubMed/bioRxiv/medRxiv plus arXiv), its scale, and routes agents away from hand-scraping. - search-papers description drops the three "arXiv" claims and names the multi-source id forms it actually returns; keeps the load-bearing "run several distinct framings" guidance verbatim. - search-papers --categories only claims what is true: arXiv-style taxonomy labels, not applicable to biomedical records. - search --categories disambiguates `research` (a ~web-domain filter) from the paper index, pointing at `research search-papers`. The wire value 'research' is unchanged. - related-papers accepts pmid:/pmcid:/doi:/arxiv: forms in its docs, in line with inspect-paper and read-paper. - research examples now include biomedical ids, not arXiv only. - cli-argv tests gain the research pair that mirrored `developer`, plus a regression guard that root help names the biomedical corpus. * docs(readme): route paper search to `research`, add its command section Why: the README taught the wrong tool. "# Find research papers" was followed by `firecrawl search --categories research`, which is only a website filter over ordinary web results, not the paper index. README also had a `###` section for every command except `research`, so the index had no documentation surface at all, and the tagline omitted both `research` and `developer`. Summary: - the "Find research papers" example now leads with `research search-papers`; the `--categories research` example stays but is labelled as the website filter it is. - same disambiguation added to the category example block and the search options table. - new `### research` section beside `developer`: corpus and scale, the explicit "not the same as --categories research" note, all five subcommands, search-papers options, and workflow tips. - line-3 tagline now mentions research papers and developer sources. * chore: add research vocabulary to package metadata, bump to 1.20.0 Why: npm search and package listings carried no research, paper, or biomedical vocabulary, so the paper index was undiscoverable from outside the CLI too. Behavioural metadata change across help text, docs, and skills -> minor bump. Summary: - package.json description names the paper index and its sources. - keywords gain research, paper/literature search, biomedical, pubmed, biorxiv, medrxiv, arxiv, life sciences. - 1.19.31 -> 1.20.0. - nfpm.yaml and homebrew/firecrawl-cli.rb carry the same one-line description; both updated. The brew `desc` is kept under the 80-char audit limit. Note: homebrew/firecrawl-cli.rb `version` is 1.10.0 and is not written by any release tooling in this repo; left as found rather than guessed at. * docs(skills): give paper search a routing surface in the CLI skills Why: agents load skills before they load `--help`. firecrawl-search had a full "Developer search" section and nothing for research; its options table listed `research` with no elaboration, so the naming collision with the paper index was invisible. firecrawl-cli's routing table and "When to Load References" omitted research entirely, so nothing ever pointed an agent at `firecrawl research`. Summary: - firecrawl-search: new "## Paper search" section parallel to "## Developer search" — states plainly that `--categories research` is not the paper index, routes to `research search-papers`, and shows the find/expand/verify loop with real id forms. - firecrawl-search: `--categories` options row and "When to use" now disambiguate the two; frontmatter description gains literature triggers so the skill actually loads on a biomedical task. - firecrawl-cli: research rows added to the routing table and to "When to Load References", both stating the anti-pattern (hand-scraping PubMed). * docs: stop pinning stale CLI versions in install commands Why: cubic flagged the README install example pinning firecrawl-cli@1.19.6 while this PR ships 1.20.0. The pin was already 25 patches behind npm's published 1.19.31, and the same stale pin appeared in five more places in the bundled skills rules. Summary: install and run commands now use @latest, matching the convention the public docs already use in all 30 of their occurrences. That removes the drift permanently rather than trading one stale pin for another — and avoids pinning 1.20.0, which is not published yet and would break the documented one-shot install until release. The illustrative `--status` sample output now shows the version this PR ships. Test Plan: pnpm test 422/422, prettier clean, no hard-pinned versions remain in any markdown file.
chore(developer): call /v2/search/developer and correct the result de… …fault The developer command called /v2/developer/search. That mount rejects a keyless caller, so keyless developer search never reached the index. It is also the path that may be withdrawn. Call /v2/search/developer, the public path, which accepts a keyless caller. The API returns 10 results by default, not 20. Correct the help text and the README.
PreviousNext
