Skip to content

Add structured field selection to scrape output #265

Description

@developersdigest

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions