feat(cli): add the developer category to search - #175
Merged
Conversation
`firecrawl search <query> --categories developer` searches an index built for coding agents: GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. The API already served the category. The CLI rejected the value, and `executeSearch` copied only `web`, `images`, and `news` out of the payload. A developer group therefore never reached the caller. The category is an extra arm, not a filter on the web results, so the API returns its hits in `data.developer`. The command copies that group through, prints it under its own heading, and labels the web group when both are present. A matched passage runs to several KB. The readable output clips it at 500 characters and names `--json`, which keeps the full text. Without the clip, three hits flood a terminal.
The developer index now has two surfaces, the same as research: the `developer` category on `firecrawl search`, and a dedicated command. The command mirrors the research commands. It calls GET /v2/developer/search, keeps the keyless free-tier path, and renders the ranked hits as markdown blocks with the passages clipped at 1200 characters; `--json` keeps the full envelope. It takes a query and `--limit` only; the endpoint accepts no filters, and that narrow surface is deliberate. New tests cover the request URL, the readable and JSON output, and the error path. Two argv tests prove the command appears in the root help and parses, so a wrapper cannot drop it the way `executeSearch` once dropped the category group. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C4vZ6XH65bUJDkLthyfmvC
Member
Author
|
@cubic-dev-ai review this PR |
@PhantomInTheWire I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
All reported issues were addressed across 10 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
firecrawl search <query> --categories developerand the newfirecrawl developer <query>command search an index built for coding agents: GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Research search has two surfaces in this client — a category and a dedicated command — and developer search now matches.Category: the API returns its hits in
data.developer. The CLI rejected the value, andexecuteSearchcopied onlyweb,images, andnewsout of the payload, so the group never reached the caller. The command now copies it through, prints it under its own heading, and clips each passage at 500 characters in readable output;--jsonkeeps the full text.Dedicated command:
firecrawl developermirrors the research commands (query positional,--limit,--json,-o, keyless free tier). It calls GET /v2/developer/search with the query and limit only; the endpoint accepts no filters, and that narrow surface is deliberate. Hits render as markdown blocks with the passages clipped at 1200 characters. Two argv tests prove the command appears in the root help and parses.Tests: 406 pass (was 391). Type-check, format, and build clean. Both surfaces verified against the live API.
🤖 Generated with Claude Code
https://claude.ai/code/session_01C4vZ6XH65bUJDkLthyfmvC
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Adds a developer-focused search across GitHub issues, merged PRs, READMEs, and docs. Available via
firecrawl search --categories developerand the newfirecrawl developercommand, with labeled output and smart passage truncation.New Features
firecrawl search "<query>" --categories developer; return hits indata.developerbesidedata.web/images/news, label groups in readable output, and truncate passages to 500 chars;--jsonkeeps full.firecrawl developer "<query>"for developer-only search (GET/v2/developer/search); outputs id/type/url/title/passages, clips readable passages to 1200 chars;--json/--prettykeep the full envelope.Bug Fixes
developeras a valid category and pass it to the API.developerresults inexecuteSearchresponse and CLI output.developer), README/SKILL docs, and add tests for args, output, and errors.Written for commit c5eaa68. Summary will update on new commits.