Add structured field selection to scrape output
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
Read production CLI PR #262 first; this issue explicitly directs the implementation there rather than into a competing PR. Use the current beta.22 scrape help as the baseline, and keep beta-skill guidance separate. Done means predictable selectors cover multi-row and missing fields, invalid selectors are rejected locally, JSON and provider errors remain valid, pagination metadata survives, and the size-versus-billing limitation is documented.
Written by the indexing model from the issue text.
Description
Add an explicit field-selection option for structured scrape responses so agents can retain useful fields without printing every provider attribute.
Target the existing production CLI PR #262; do not open a competing production implementation PR. Keep released beta-skill guidance in a separate PR and document a flag there only when that beta supports it.
Define selection relative to provider result data, including array rows and missing fields. Preserve request IDs, receipts, errors and pagination metadata; reject invalid selectors locally. Start with predictable paths rather than arbitrary code evaluation. Clarify that local projection reduces printed/context size but does not reduce upstream transfer, execution or billing. For remote reduction, retained-result Bash already exists where supported.
Acceptance: a projected multi-row response stays valid JSON, reports provider errors unchanged, and retains enough metadata to continue pagination. Current beta.22 scrape help exposes neither --fields nor --select.
- Dominant language
- TypeScript
- Stars
- 635
- Forks
- 106
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firecrawl/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
firecrawl-monitor skill: description exceeds Claude Code's 1024-char limit, skill fails to load Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·