Conversation
Contributor
Author
|
Closing as superseded by #264, which merged the search contents command and its typed flags. |
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.
Summary
kernel search contents <id>with a JSON request body for selected result contentTesting
go test ./cmd -run TestSearchNote
Medium Risk
New CLI surface can trigger billable search content and browser retrieval; validation is limited to the result selector, with remaining fields passed through to the API.
Overview
Adds
kernel search contents <id>, a subcommand that POSTs tosearch/<id>/contentswith a required--requestJSON body so users can pull page or provider content for a retained search after the initial query.Client-side validation rejects missing or malformed
--requestpayloads and enforces exactly one ofresult_idsorlimitbefore the API call. Help text notes that browser-backed retrieval can use concurrency and incur charges. Responses still flow through the existingexecuteSearchRequestpath (indented JSON on stdout, no retries on POST).Tests cover a happy-path POST/body assertion, extra invalid-input cases for the new command, and command wiring alongside
getandproviders.Reviewed by Cursor Bugbot for commit 8a61f40. Configure here.