Skip to content

feat(cli): add the developer category to search - #175

Merged
KrisOei merged 2 commits into
mainfrom
feat/developer-search
Jul 31, 2026
Merged

feat(cli): add the developer category to search#175
KrisOei merged 2 commits into
mainfrom
feat/developer-search

Conversation

@PhantomInTheWire

@PhantomInTheWire PhantomInTheWire commented Jul 31, 2026

Copy link
Copy Markdown
Member

firecrawl search <query> --categories developer and the new firecrawl 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, and executeSearch copied only web, images, and news out 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; --json keeps the full text.

Dedicated command: firecrawl developer mirrors 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


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with 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 developer and the new firecrawl developer command, with labeled output and smart passage truncation.

  • New Features

    • Support firecrawl search "<query>" --categories developer; return hits in data.developer beside data.web/images/news, label groups in readable output, and truncate passages to 500 chars; --json keeps full.
    • Add firecrawl developer "<query>" for developer-only search (GET /v2/developer/search); outputs id/type/url/title/passages, clips readable passages to 1200 chars; --json/--pretty keep the full envelope.
  • Bug Fixes

    • Accept developer as a valid category and pass it to the API.
    • Include developer results in executeSearch response and CLI output.
    • Update types, CLI help (root lists developer), README/SKILL docs, and add tests for args, output, and errors.

Written for commit c5eaa68. Summary will update on new commits.

Review in cubic

`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.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 6 files

Re-trigger cubic

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
@PhantomInTheWire

Copy link
Copy Markdown
Member Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Jul 31, 2026

Copy link
Copy Markdown

@cubic-dev-ai review this PR

@PhantomInTheWire I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 10 files

Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic

Comment thread src/commands/developer.ts
@KrisOei
KrisOei merged commit a151277 into main Jul 31, 2026
9 checks passed
@KrisOei
KrisOei deleted the feat/developer-search branch July 31, 2026 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants